[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' ***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 ] | ||
|
The "Operation not permitted" indicates an issue with the file permissions for /tmp/mongodb-27017.sock. You can try running:
but if you are using root you can try:
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, |