I have a problem when I want to connect to my MongoDB database (MongoAtlas). I have used Studio3T, but now I am not able to connect to my database any more. When I insert the Connection URI to 3T, I get the following response:
Connection failed.
SERVER [xxx.mongodb.net:27017] (Type: UNKNOWN)
|_/ Mongo Server error (MongoCommandException): Command failed with error 8000: 'could not find config for xxx.mongodb.net' on server xxx.mongodb.net:27017.
|_...
|_... The full response is:
|_... {
|_... "ok" : NumberInt(0),
|_... "errmsg" : "could not find config for xxx.mongodb.net",
|_... "code" : NumberInt(8000),
|_... "codeName" : "AtlasError"
|_... }
I have also tried to connect via MongoCompass in case I copied a false URI, because it it detects the string from my clipboard. From Compass I get the following error:
Server at xxx.mongodb.net:27017 reports wire version 0,
but this version of Node.js Driver requires at least 2 (MongoDB2.6).
All of this happened after I have upgraded my cluster to M10.
Related
I am having an issue with getting a server connection using the rsDriver function using this code:
driver <- rsDriver(browser = "chrome", chromever = "111.0.5563.19", port=free_port(),check=F, verbose=T)
I get this error:
Warning: Could not determine server status.[1] "Connecting to remote server" Could not open chrome browser. Client error message: Undefined error in httr call. httr output: Failed to connect to localhost port 14415 after 2229 ms: Connection refused Check server log for further details.
As suggested by other posts, I have tried deleting the LICENSE.chromedriver files which has not worked, as well as updating all dependencies of wdman. I have also attempted to revert wdman back to 0.2.5 from the current version but the old version will not install. While attempting to roll wdman back to v0.2.5 using
remotes::install_version("wdman",version="0.2.5",repos="http://cran.us.r-project.org")
I get this error:
Downloading package from url: http://cran.us.r-project.org/src/contrib/Archive/wdman/wdman_0.2.5.tar.gz Installing package into ‘C:/Users/abc/AppData/Local/R/win-library/4.2’ (as ‘lib’ is unspecified) Warning message: In i.p(...) : installation of package ‘C:/Users/abc/AppData/Local/Temp/RtmpuCeY3j/remotes1aec32a03b15/wdman’ had non-zero exit status
I have also tried using firefox instead of chrome without success. This is on windows 10, with R 4.2.2, RSelenium 1.7.9.
I'm trying to connect to MongoDB in a IBMCloud instance and I'm using MongoID. I ever use some configurations and try very things. I'm getting the error:
MONGODB | Error running ismaster on address:port: system lib
Here is my mongoid.yml that I'm trying to connect to mongoDB:
development:
clients:
default:
database: databasename
hosts:
- address:port
- address:port
options:
user: 'admin'
password: 'some-password'
auth_mech: :scram
auth_source: admin
connect: :replica_set
replica_set: replset
ssl: true
ssl_ca_cert: ./some-certificate.pem
ssl_verify: true
options:
log_level: :debug
What do I need to add to connect with the mongo database in IBMCloud?
"system lib" is coming from OpenSSL and indicates a problem with the CA certificate, such as the path not referring to an existing file. Note that in the configuration you specified a relative path which could cause problems.
I created https://jira.mongodb.org/browse/RUBY-1946 to add the exception class to the reported message which would clarify where the error is originating in the future.
Upgrade to the current version of Ruby driver (2.10.2 as of this writing) which provides more extensive diagnostics. Set driver log level to debug (https://docs.mongodb.com/mongoid/master/tutorials/mongoid-configuration/#logging). If you are having trouble identifying the problem then, post the
updated error and log messages here.
I'm trying to use a "Deploy SSIS" task in VSTS. I get this error:
Task_InternalError Exception calling ".ctor" with "1" argument(s): "Failed to connect to server xyz
It is asking for the following information below. How do I go about finding the information below needed for this task? The path to the .ispac file is easy since it is uploaded. I also think the name of the server is correct.
-Display name
-Path to .ispac file
-Name of the SSIS project in the .ispac file
-Name of the SQL Server hosting the SSIS catalog database
-Name of the SSIS catalog
-Name of the SSIS catalog folder
-Description of the SSIS catalog folder
Edit:
(detailed error log)
2017-09-20T12:55:05.6438379Z ##[debug]Env:INPUT_PROJECTFILEPATH: 'd:\a\3\s\HR Data.ispac'
2017-09-20T12:55:05.6468345Z ##[debug]Env:INPUT_PROJECTNAME: 'xyz'
2017-09-20T12:55:05.6488487Z ##[debug]Env:INPUT_SERVERNAME: 'xyz'
2017-09-20T12:55:05.6538355Z ##[debug]Env:INPUT_CATALOGNAME: 'xyz'
2017-09-20T12:55:05.6558353Z ##[debug]Env:INPUT_FOLDERNAME: 'xyz'
2017-09-20T12:55:05.6568351Z ##[debug]Env:INPUT_FOLDERDESCRIPTION (empty)
2017-09-20T12:55:05.6618490Z ##[debug]Env:INPUT_PROJECTPARAMETERS (empty)
2017-09-20T12:55:05.6628342Z SQL Connection String: Data Source=xyz;Initial Catalog=master;Integrated Security=SSPI;
2017-09-20T12:55:05.6638360Z Project file path: d:\a\3\s\xyz.ispac
2017-09-20T12:55:22.8057049Z ##[debug]Leaving D:\a_tasks\DeploySsis_582498ad-81d6-48b7-b9bc-fd0e5dec2e2b\0.1.0\DeploySSISTask.ps1.
2017-09-20T12:55:22.8388650Z ##[debug]Caught exception from task script.
2017-09-20T12:55:22.8418679Z ##[debug]Error record:
2017-09-20T12:55:22.8948708Z ##[debug]D:\a_tasks\DeploySsis_582498ad-81d6-48b7-b9bc-fd0e5dec2e2b\0.1.0\DeploySSISTask.ps1 : Task_InternalError Exception calling ".ctor" with "1" argument(s): "Failed to connect to server xyz."
2017-09-20T12:55:22.8968708Z ##[debug]At line:1 char:1
2017-09-20T12:55:22.8978718Z ##[debug]+ . 'd:\a_tasks\DeploySsis_582498ad-81d6-48b7-b9bc-fd0e5dec2e2b\0.1.0\ ...
2017-09-20T12:55:22.8988697Z ##[debug]+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2017-09-20T12:55:22.8998697Z ##[debug] + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
2017-09-20T12:55:22.9008861Z ##[debug] + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,DeploySSISTask.ps1
2017-09-20T12:55:22.9018704Z ##[debug]
2017-09-20T12:55:22.9048688Z ##[debug]Script stack trace:
2017-09-20T12:55:22.9078699Z ##[debug]at ,
D:\a_tasks\DeploySsis_582498ad-81d6-48b7-b9bc-fd0e5dec2e2b\0.1.0\DeploySSISTask.ps1: line 97
2017-09-20T12:55:22.9098691Z ##[debug]at , : line 1
2017-09-20T12:55:22.9108747Z ##[debug]at , : line 22
2017-09-20T12:55:22.9118883Z ##[debug]at , : line 18
2017-09-20T12:55:22.9128882Z ##[debug]at , : line 1
2017-09-20T12:55:22.9148698Z ##[debug]Exception:
2017-09-20T12:55:22.9188799Z ##[debug]Microsoft.PowerShell.Commands.WriteErrorException: Task_InternalError Exception calling ".ctor" with "1" argument(s): "Failed to connect to server xyz."
2017-09-20T12:55:22.9478706Z ##[error]Task_InternalError Exception calling ".ctor" with "1" argument(s): "Failed to connect to server xyz."
2017-09-20T12:55:22.9478706Z ##[debug]Processed: ##vso[task.logissue type=error]Task_InternalError Exception calling ".ctor" with "1" argument(s): "Failed to connect to server xyz."
2017-09-20T12:55:22.9508700Z ##[debug]Processed: ##vso[task.complete result=Failed]
Regarding Deploy SSIS task, it connects to the server with windows authentication (Integrated Security=SSPI), but the Hosted agent uses service account that can’t connect to the server.
You can set up a private build agent (running as your account) and queue build with that build agent, or you can refer to the source code to build the PowerShell script to deploy SSIS project with SQL Server authentication (User ID=XXX; Password=XX)
A related thread: Build and Deploy SSIS packages using VSTS
I deployed a Cassandra cluster through their launcher: https://cloud.google.com/launcher/explore?q=cassandra
I can connect to the VM fine, through SSH/PuTTY.
Then when I try to connect with for example DBeaver I get:
com.datastax.driver.core.exceptions.NoHostAvailableExeption: All host(s) tried for query failed(tried: /x.x.x.x:9160)
com.datastax.driver.core.ConnectionExption:[/x.x.x.x:9160] Unexpected error during transport initialization. Connection has been closed
Or with cassandra-driver (nodejs), I get:
All host(s) tried for query failed. First host tried, x.x.x.x:9160: Error: read ECONNRESET. See innerErrors.
InnerErrors: { 'x.x.x.x:9160': { [Error: read ECONNRESET] code: 'ECONNRESET', errno: 'ECONNRESET', syscall: 'read' } }
Info: Represents an error when a query cannot be performed because no host is available or could be reached by the driver.
I've forwarded the 9160 port in the google developer console and it seems to work because when I stop the cassandra server on the VM it gives a different error, indicating connection is refused:
All host(s) tried for query failed. First host tried, x.x.x.x:9160: Error: connect ECONNREFUSED. See innerErrors.
InnerErrors: { 'x.x.x.x:9160':
{ [Error: connect ECONNREFUSED]
code: 'ECONNREFUSED',
errno: 'ECONNREFUSED',
syscall: 'connect' } }
Info: Represents an error when a query cannot be performed because no host is available or could be reached by the driver.
Now, I've tried editing the cassandra.yaml rcp_adress to the actual external address instead of 0.0.0.0.
I've also tried the internal serverfarm address.
I've not changed the default authentication (but also tried with auth):
authenticator: AllowAllAuthenticator
# authenticator: PasswordAuthenticator
authorizer: AllowAllAuthorizer
# authorizer: CassandraAuthorizer
I'm at a loss, the connection seems to work, but cassandra seems to not allow a login or reset the connection?
You are trying to connect on the thrift port (9160). You should be using the native protocol port (9042).
I am using Base ClearCase with ClearQuest using CMI according to the IBM document :
How to configure base ClearCase to use the Change Management integration with ClearQuest
http://www-01.ibm.com/support/docview.wss?uid=swg21633122
While checking out a file, I am getting the following error within cmi.log file:
May 21,2015 12:23:22.574::ERROR::zxw378::Some Change Management providers failed to initialize! "Status : "10005", Error : "The requested resource was not found.
Session initialize failed for server at "http://usbri-app06/cqweb".
", Warning : "", Information : ""."
ClearQuest Login with either Client or Browser works perfectly fine.
cmiregister list -cq command response looks correct.
cleartool lsprovider -long -vob . response looks correct.
Any idea what else to look for, because CHECKOUT fails to attach the TASK with the VERSION of the ELEMENT.