MongoDB Failing to Start - ***aborting after fassert() failure

Question

I am new to Ubuntu (Linux tbh). I encountered problem with starting MongoDB service. I want to created web app using Ruby on Rails and MongoDB but mongo seems to fail to start.

I followed this MongoDB installation on Ubuntu all of installation went without problems until I got to sudo service mongod start

mongod.log

2016-01-01T10:58:15.545+0000 I CONTROL  ***** SERVER RESTARTED *****
2016-01-01T10:58:15.548+0000 I CONTROL  [initandlisten] MongoDB starting : pid=3868 port=27017 dbpath=/var/lib/mongodb 64-bit host=damian-CX61-0NC-CX61-0ND-CX61-0NF-CX61-0NE
2016-01-01T10:58:15.548+0000 I CONTROL  [initandlisten] db version v3.0.8
2016-01-01T10:58:15.548+0000 I CONTROL  [initandlisten] git version: 83d8cc25e00e42856924d84e220fbe4a839e605d
2016-01-01T10:58:15.548+0000 I CONTROL  [initandlisten] build info: Linux ip-10-187-89-126 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49
2016-01-01T10:58:15.548+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2016-01-01T10:58:15.548+0000 I CONTROL  [initandlisten] options: { config: "/etc/mongod.conf", net: { bindIp: "127.0.0.1", port: 27017 }, storage: { dbPath: "/var/lib/mongodb", journal: { enabled: true } }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongod.log" } }
2016-01-01T10:58:15.567+0000 E NETWORK  [initandlisten] Failed to unlink socket file /tmp/mongodb-27017.sock errno:1 Operation not permitted
2016-01-01T10:58:15.567+0000 I -        [initandlisten] Fatal Assertion 28578
2016-01-01T10:58:15.567+0000 I -        [initandlisten] 

***aborting after fassert() failure

So what I am doing wrong or its different issue?

Does the file /tmp/mongodb-27017.sock exist? If so try to delete it, ie. 'sudo rm /tmp/mongodb-27017.sock'. — kometen, Jan 01 '16 at 11:14
@kometen I think that worked - how to check that mongo is actually running? Like in windows I had cmd window with all these things going on - here I cant see any of it. Is mongod.log the only way to know what is going on? — Fresz, Jan 01 '16 at 11:25
2520 ? Sl 0:09 /usr/bin/gnome-terminal -x /bin/sh -c cd '/home/damian/Downloads/mongodb-linux-x86_64-ubuntu1404-3.2.0/bin' && exec $SHELL 3751 ? Sl 0:06 gedit /var/log/mongodb/mongod.log 4020 ? Ssl 0:23 /usr/bin/mongod --config /etc/mongod.conf 4206 pts/0 S+ 0:00 grep --color=auto mongo What does this mean? Am I running 4 different mongodb's at the same time? — Fresz, Jan 01 '16 at 12:21
I'm not shure where the output came from. But there are probably more than one process to handle the requests. — kometen, Jan 01 '16 at 19:19

score 70 · Accepted Answer · edited May 23 '17 at 12:10

70

SOLUTION by kometen

Does the file /tmp/mongodb-27017.sock exist? If so try to delete it, ie. 'sudo rm /tmp/mongodb-27017.sock'.

edited May 23 '17 at 12:10

Community

1
1

answered Jan 22 '16 at 11:48

Fresz

1,804
2
16
29

2

You saved my day. Thank you – Nimatullah Razmjo Apr 16 '16 at 09:58
4

What does this do exactly? – Jeremy Jackson Mar 01 '17 at 20:40
3

I'm using Mac (Sierra OS), but I can't find this file... thanks @fresz – chemitaxis Apr 24 '17 at 14:41
Hey guys, this solution is for linux. What this do its removing temporary file which didnt delete itself and its blocking normal operation. – Fresz Mar 04 '18 at 08:21
Hey guys this solution doesn't work for me. When I delete mongod-27017.sock and try to start mongod, the file pops back up in /tmp. Suggestions? – ByteTheBits Mar 10 '20 at 18:09
@larry are u on Linux? Does your service for mongodb start at all? – Fresz Mar 10 '20 at 19:03
Yes I'm on Ubuntu 18.04 LTS. I was able to resolve my issue by installing version 4.0.10. Turns out version 4.0.9 and 4.0.11 have compatibility issues with Ubuntu. – ByteTheBits Mar 11 '20 at 05:29
I also had an issue with this file reappearing in /tmp. I think for me it was because I had a running mongodb-runner process. I killed it, and `sudo service mongod start` behaved as expected. – userManyNumbers May 18 '22 at 07:58

minion · Answer 2 · 2020-08-07T09:06:24.987

8

The problem can also be due to mongodb using up all the disk space. That was the case for me. You can install ncdu with this command: sudo apt install ncdu

This will help you in looking at the disk usage. Use the command: ncdu -x /

Remove the unwanted dbs from /var/lib/mongodb/

edited Aug 07 '20 at 09:06

answered Aug 04 '17 at 12:55

minion

81
1
3

Thanks. That memory thing issue reminded me and saved my day – sns Jul 10 '18 at 19:25
1

`ncdu` is not for memory, it's for disk space, huge difference. – Moshe Feb 10 '19 at 08:55
@Moshe Thanks for pointing it out, updated the solution – minion Aug 07 '20 at 09:07

score 7 · Answer 3 · answered Jun 22 '20 at 15:09

7

sudo mongod

(suggested by @João Bortolosso)

after (suggested by @fresz):

sudo rm /tmp/mongodb-27017.sock

worked on mac!

answered Jun 22 '20 at 15:09

Maya

75
1
3

score 6 · Answer 4 · edited Aug 05 '19 at 15:14

6

If you use Ubuntu, try:

sudo mongod

edited Aug 05 '19 at 15:14

Paul Roub

36,322
27
84
93

answered Aug 05 '19 at 15:12

João Bortolosso

71
1
3

score 2 · Answer 5 · answered Oct 14 '20 at 11:51

2

For me, it was because of the bad data inside the folder: ‘/data/db’

Solution that worked for me: Remove all the files inside '/data/db'

answered Oct 14 '20 at 11:51

Saravanan V

79
4

score 2 · Answer 6 · answered Aug 18 '21 at 17:02

We was getting the same message in Production and service was not restarted

{"t":{"$date":"2021-08-18T15:18:27.834+00:00"},"s":"F",  "c":"-",        "id":23092,   "ctx":"initandlisten","msg":"\n\n***aborting after fassert() failure\n\n"}

So I ran this command (Giving the permission to mongodb user)

sudo chown mongodb:mongodb mongodb-27017.sock

And started the service

sudo systemctl start mongod

Now mongo is up and running. ;)

Credit Goes to our StackOverflow Contributor Rajith K

He gave the answer on 'Failed to unlink socket file" error in MongoDB 3.0

score 1 · Answer 7 · answered Aug 09 '20 at 05:50

1

mongo --shell

It worked for me on ubuntu

answered Aug 09 '20 at 05:50

Prince Agrawal

380
4
14

score 0 · Answer 8 · answered Jul 10 '22 at 06:50

You need to delete MongoDB temp file

sudo rm /tmp/mongodb-27017.sock

for any one getting this error after every restart, u need to stop mongod.service on startup

sudo systemctl disable mongod.service

the name mongod.service may change later, so just write mongo and press tab for autocompletion

score 0 · Answer 9 · answered Aug 08 '23 at 12:16

0

clear the files inside c:\data\db folder and then start mongodb database using mongod command.

answered Aug 08 '23 at 12:16

Viswanath Balisetty

1

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Aug 14 '23 at 03:23

MongoDB Failing to Start - ***aborting after fassert() failure

9 Answers9

Linked

Related