Mongod keeps aborting

Every time i try to run mongod it aborts with message

{“t”:{"$date":“2021-06-01T21:52:21.630+03:00”},“s”:“E”, “c”:“NETWORK”, “id”:23024, “ctx”:“initandlisten”,“msg”:“Failed to unlink socket file”,“attr”:{“path”:"/tmp/mongodb-27017.sock",“error”:“Operation not permitted”}}
{“t”:{"$date":“2021-06-01T21:52:21.630+03:00”},“s”:“F”, “c”:"-", “id”:23091, “ctx”:“initandlisten”,“msg”:“Fatal assertion”,“attr”:{“msgid”:40486,“file”:“src/mongo/transport/transport_layer_asio.cpp”,“line”:919}}
{“t”:{"$date":“2021-06-01T21:52:21.630+03:00”},“s”:“F”, “c”:"-", “id”:23092, “ctx”:“initandlisten”,“msg”:"\n\n***aborting after fassert() failure\n\n"}

mongo works fine.
I have tried sudo mongod and mongod --repair with no posetive result

Hi @jakob_smith and welcome in the MongoDB community :muscle: !

Looks like there is something wrong with your socket file /tmp/mongodb-27017.sock.
Are you sure that your port 27017 is free? No other mongod service running somewhere & using this port?

Cheers,
Maxime.

The simplest way to fix that with the M103 IDE that you are supposed to use is to reset the workspace.

1 Like

yes i have tested if the port is free and it is.

i am not using the IDE, working from local terminal

Hi @jakob_smith,

We recommend you to use the IDE, as then only you will be able to pass the labs within the courses.

All the Best,
Kushagra

1 Like

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.