error message [localhost:27017: [WinError 10061] No connection could be made because the target machine actively refused it, Timeout: 30s, - mongodb

MongoDb atlas connetion issue.
Can anyone know how to resolve it?
error message [localhost:27017: [WinError 10061] No connection could
be made because the target machine actively refused it, Timeout: 30s,
Topology Description:
I checked MongoDB atlas connection, connection working fine, cluster running.

Related

kafka installation failed with Connection failed: [Errno 111] Connection refused to 6667

I am installing kafka using ambari.
While installation i got an error:
Connection failed: [Errno 111] Connection refused to localhost:6667.
Can someone help in this.
The error message seems to be related to the Kafka listener port, which is by default 6667. There might be another port configured, the port is blocked within the network or the service is not running.

Bluemix WebsocketListener.Start: Error connecting to a doppler server

Has anyone faced this issue with Bluemix? One of my Bluemix instances crashes repeatedly and the log file shows the following error. Seems to be an internal error within Bluemix environment, and I could not understand the reason for it.
......
2016-08-04T12:02:07.617+0530[DEA/75]OUTStopped app instance (index 0) with guid 9b4ebc26-e5f9-4c61-a54e-f8c7437185a7
2016-08-04T12:02:17.783+0530[LGR/null]ERRWebsocketListener.Start: Error connecting to a doppler server
2016-08-04T12:02:17.799+0530[LGR/null]ERRproxy: error connecting to 158.85.134.172:8081: dial tcp 158.85.134.172:8081: getsockopt: connection refused
2016-08-04T12:02:17.899+0530[LGR/null]ERRproxy: error connecting to 158.85.134.172:8081: dial tcp 158.85.134.172:8081: getsockopt: connection refused

MongoDB unable to run in Windows7

we have installed MongoDB 3.2.1. When i try to run it shows the following error.
C:\Program Files\MongoDB\Server\3.0\bin>mongo.exe
2016-01-13T12:48:14.974+0530 I CONTROL Hotfix KB2731284 or later update is installed, no need to zero-out data files
MongoDB shell version: 3.0.4
connecting to: test
2016-01-13T12:48:15.996+0530 W NETWORK Failed to connect to 127.0.0.1:27017, reason: errno:10061 No connection could be
made because the target machine actively refused it.
2016-01-13T12:48:16.002+0530 E QUERY Error: couldn't connect to server 127.0.0.1:27017 (127.0.0.1), connection attemp
t failed
at connect (src/mongo/shell/mongo.js:179:14)
at (connect):1:6 at src/mongo/shell/mongo.js:179
exception: connect failed
Please any one help us to solve this issue.

hack for "mongo db connection refused due to blocked port errno 10061"

I m trying connect to my db in Mongolab:
>> mongo ds123456.mongolab.com
MongoDB shell version: 2.6.1
connecting to: ds123456.mongolab.com/test
2014-12-16T14:13:41.738+0100 warning: Failed to connect to 54.74.247.101:27017, reason: errno:10061 No connection could be made because the target machine actively refused it.
2014-12-16T14:13:41.741+0100 Error: couldn't connect to server ds123456.mongolab.com:27017 (54.74.247.101), connection attempt failed at src/mongo/shell/mongo.js:148
exception: connect failed
I assume this question answers the first problem of access being blocked on this port.
The obvious solution is to contact the network admin. But I wonder if there is an alternative?
Thanks in advance.

Trying to run play application in console on heroku

I'm trying to start a play application in a console on heroku using this line of code:
new play.core.StaticApplication(new java.io.File("."))
Unfortunately it seems to be having a problem connecting to my database. I'm using postgres. Here's my configuration from application.conf
db.default.driver=org.postgresql.Driver
db.default.url=${?DATABASE_URL}
db.default.user=myusername
db.default.password=mypassword
My app is able to access the database through regular use. Here's the error i'm getting:
c.j.b.h.AbstractConnectionHook - Failed to obtain initial connection Sleeping for 0ms and trying again. Attempts left: 0. Exception: java.net.ConnectException: Connection refused.Message:Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
Configuration error: Configuration error[Cannot connect to database [default]]