[SERVER-48999] mongod command is exiting with ***aborting after fassert() failure message Created: 22/Jun/20  Updated: 06/Dec/22  Resolved: 22/Jun/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.2.8
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: MIKHIL MOHAN C Assignee: Backlog - Triage Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Triage
Operating System: ALL
Participants:

 Description   

Whenever I run the command mongod, this output is showing.

 

2020-06-22T09:51:19.613+0530 I CONTROL [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
2020-06-22T09:51:19.678+0530 W ASIO [main] No TransportLayer configured during NetworkInterface startup
2020-06-22T09:51:19.679+0530 I CONTROL [initandlisten] MongoDB starting : pid=11097 port=27017 dbpath=/data/db 64-bit host=mikhil-HP-Laptop-15-bs0xx
2020-06-22T09:51:19.679+0530 I CONTROL [initandlisten] db version v4.2.8
2020-06-22T09:51:19.679+0530 I CONTROL [initandlisten] git version: 43d25964249164d76d5e04dd6cf38f6111e21f5f
2020-06-22T09:51:19.679+0530 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.1.1 11 Sep 2018
2020-06-22T09:51:19.679+0530 I CONTROL [initandlisten] allocator: tcmalloc
2020-06-22T09:51:19.679+0530 I CONTROL [initandlisten] modules: none
2020-06-22T09:51:19.679+0530 I CONTROL [initandlisten] build environment:
2020-06-22T09:51:19.679+0530 I CONTROL [initandlisten] distmod: ubuntu1804
2020-06-22T09:51:19.679+0530 I CONTROL [initandlisten] distarch: x86_64
2020-06-22T09:51:19.679+0530 I CONTROL [initandlisten] target_arch: x86_64
2020-06-22T09:51:19.679+0530 I CONTROL [initandlisten] options: {}
2020-06-22T09:51:19.679+0530 E NETWORK [initandlisten] Failed to unlink socket file /tmp/mongodb-27017.sock Operation not permitted
2020-06-22T09:51:19.679+0530 F - [initandlisten] Fatal Assertion 40486 at src/mongo/transport/transport_layer_asio.cpp 684
2020-06-22T09:51:19.680+0530 F - [initandlisten]

***aborting after fassert() failure

 

I tried deleting the file /tmp/mongodb-27017.sock. But whenever I starts the mongod using sudo systemctl start mongod, that file is creating again and again. What should I do now?



 Comments   
Comment by Carl Champain (Inactive) [ 22/Jun/20 ]

Hi mikhilmohan13@gmail.com,

The "Operation not permitted" indicates an issue with the file permissions for /tmp/mongodb-27017.sock. You can try running:

sudo chown `whoami` /tmp/mongodb-27017.sock

but if you are using root you can try:

sudo chown mongodb:mongodb /tmp/mongodb-27017.sock

That said, the SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to be a bug, I will now close it. If you need further assistance troubleshooting, I encourage you to ask our community by posting on the MongoDB Community Forums or on Stack Overflow with the mongodb tag.

Kind regards,
Carl

Generated at Thu Feb 08 05:18:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.