Pymongo keeps refusing the connection at 27017

Question

I am trying to run a simple connection to pymongo but it keeps returning that the connection was refused

Here is what I tried:

>>>from pymongo import Connection
>>>connection = Connection('localhost',27017)

here is what I get

Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/lib/python2.7/dist-packages/pymongo-2.0.1_-py2.7-linux i686.egg/pymongo/connection.py", line 348, in __init__
 self.__find_node()
File "/usr/local/lib/python2.7/dist-packages/pymongo-2.0.1_-py2.7-linux- i686.egg/pymongo/connection.py", line 627, in __find_node
  raise AutoReconnect(', '.join(errors))
pymongo.errors.AutoReconnect: could not connect to localhost:27017: [Errno 111]     Connection refused

How do I fix this?

score 56 · Accepted Answer · edited Mar 18 '20 at 21:34

56

Removing mongod.lock inside /var/lib/mongodb

sudo rm /var/lib/mongodb/mongod.lock

And then restarting the service should do it. For example, in my Ubuntu installation, restarting the server is something like this:

sudo service mongodb start

edited Mar 18 '20 at 21:34

alper

2,919
9
53
102

answered Nov 07 '11 at 12:23

Guille Polito

882
7
3

1

It should be `sudo service mongodb start` not `sudo service mongod start` – jfleach Sep 20 '18 at 21:59
1

path should be `/var/lib/mongodb`. – Sashini Hettiarachchi Feb 11 '19 at 03:55
3

C:\Program Files\MongoDB\Server\4.0\data on Windows thanks! – fedeteka Feb 24 '19 at 12:18
1

@jfleach that actually depends upon whether you're using the default package on Ubuntu (mongodb) or the official mongodb package. In the latter case, mongod and not mongodb is the service (daemon) name. – Nikhil Silveira Jun 10 '19 at 10:21
6

For me `sudo service mongod start` worked, not `sudo service mongodb start` – mhatch Sep 11 '19 at 22:11
You need to issue the command **sudo service mongod start** to start the mongo server. – Ayesh Weerasinghe Feb 27 '20 at 06:48
Did not worked for me – arpit1714 Oct 16 '21 at 13:19
how do i run this inside a k8 pod? – Savannah Madison Jun 24 '22 at 15:28
On Macs with the Apple chip the file is probably located under `/opt/homebrew/var/log/mongodb`. – Jakob May 02 '23 at 16:14

score 16 · Answer 2 · answered Jan 11 '21 at 22:07

If you found this page because you use Docker and you face the connection problem, try to use in your client initialization the docker container name of the mongodb instead of the localhost:27017 or 0.0.0.0:27017

Steps to fix:

write docker ps in console
find the name of container (it's in the last column of the command output called NAMES
MongoClient('mongodb://CONTAINER_NAME')

PROFIT.

score 13 · Answer 3 · answered Jun 25 '14 at 13:37

Just try following commands in given order :

sudo rm /var/lib/mongodb/mongod.lock

sudo mongod --repair

sudo service mongodb start

sudo service mongodb status

That's it now you could see following as output of last command:

mongodb start/running, process 2796

score 10 · Answer 4 · answered Aug 12 '14 at 16:34

For anyone who's having this problem on a remote server rather than the localhost, try enabling external interfaces:

Go to the configuration file (ex. /etc/mongodb.conf)
Find bind_ip=127.0.0.1
Comment out that line with a # at the front
Restart mongod

score 7 · Answer 5 · answered Oct 12 '11 at 18:21

7

It looks like you might not be running the MongoDB server. One thing that frequently trips me up is that if the server was shut down uncleanly, it will refuse to start up again until you remove the mongod.lock file from the data directory.

answered Oct 12 '11 at 18:21

Rick Copeland

11,672
5
39
38

score 4 · Answer 6 · answered Jan 11 '19 at 05:52

4

Try following commands :

sudo service mongod start
sudo service mongod status

db.py

import pymongo
from pymongo import MongoClient
#mongo client is connected
client = MongoClient()
db     = client['db']

answered Jan 11 '19 at 05:52

Nija I Pillai

1,046
11
13

score 3 · Answer 7 · answered Dec 19 '12 at 22:01

3

Rather than deleting mongod.lock, I'd recommend running 'mongod --repair'. (I figure it's better to go in through the front door whenever possible. And there may be other things that this catches as well, AFAIK.)

answered Dec 19 '12 at 22:01

ryepdx

206
1
6

1

Fair enough. Though I don't recall size being a factor here. My answer's certainly valid for people working with smaller datasets. – ryepdx Nov 07 '13 at 17:56

score 2 · Answer 8 · answered Mar 10 '21 at 22:05

None of the above answers worked for me, as I am using docker-compose so this worked for me:

docker run --rm --volumes-from my-mongo-server mongo unlink "/data/db/mongod.lock"
docker run --rm --volumes-from my-mongo-server mongo --repair

Replace my-mongo-server with your container name/id.

score 1 · Answer 9 · answered Mar 19 '20 at 13:39

If you're trying to connect from a server (other than your localhost), try checking if your mongo installation is complete : you should have: * /var/lib/mongodb file * /var/log/mongodb file * mongodb.service as service ( check by starting the service sudo service mongodb start )

If any of those fails, try reinstalling mongo ( Failed to start mongod.service: Unit mongod.service not found )

This solved my problem. Cheers

score 1 · Answer 10 · answered Aug 15 '20 at 13:54

1

First make sure you have installed mongodb using sudo apt install mongodb

answered Aug 15 '20 at 13:54

Biplob Das

2,818
21
13

score 0 · Answer 11 · answered Jun 26 '20 at 08:34

0

For the newer versions(4.x) of MongoDb, you can try:

sudo rm /var/lib/mongodb/mongod.lock

sudo systemctl daemon-reload

sudo systemctl start mongod

answered Jun 26 '20 at 08:34

Abhinav Anand

573
3
5
19

score -1 · Answer 12 · answered May 20 '21 at 01:18

-1

Thanks, but for me i just had to stop mongod and then restart it and it worked fine without having to remove anything. PS : pymongo 2.7.2

answered May 20 '21 at 01:18

Ben msaad Wael

1

Pymongo keeps refusing the connection at 27017

12 Answers12

Linked

Related