Are you looking for a solution to the error ‘MongoDb error aborting after fassert() failure’? We can help you fix it.

Here at Bobcares, we have seen several such MongoDB errors as part of our Server Management Services for web hosts and online service providers.

Today we’ll take a look at the causes for this error and see how to fix it.

Why MongoDB error aborting after fassert() failure occurs

Before we get into the solution part of this error message. Let us first see what causes this error to occur in MongoDB.

Normally, this error occurs due to the existence of the temporary socket file /tmp/mongodb-27017.sock

Also, in some cases, the MongoDB consumes a lot of disk space. Thus, this disk usage issue also causes this error to occur.

For instance, the error appears as below.

How we fix the error ‘MongoDB error aborting after fassert() failure’

Now let us look into the solution part of this error message.

One of our customers installed MongoDB on Ubuntu. Then while starting the MongoDB service using the below command, he came across the ‘aborting after fassert() failure‘ error.

sudo service mongod start

So our Support Engineers suggested removing the socket file,

/tmp/mongodb-27017.sock

In case, if the file isn’t getting deleted, then set the file to appropriate permissions and then delete it.

Sometimes, the file will have a root permission set. So make sure that you have the root access to delete it or change the permissions of the file.

After deleting the file, restart the MongoDB service. Here is the command for restarting it.

sudo systemctl start mongod

This must fix the error.

[Need any further assistance in fixing MongoDB errors? – We are here to help you.]

Conclusion

In short, this MongoDB error occurs due to the existence of the temporary socket file /tmp/mongodb-27017.sock or if MongoDB eats a lot of disk space in the server. Today, we saw how our Support Engineers fix this error.