How to solve the problem of starting an error report again after an abnormal shutdown of Mongodb

How to solve Mongodb abnormal shutdown after starting error again, for this problem, this article details the corresponding analysis and solution, hoping to help more small partners who want to solve this problem find a simpler and easier way.

Mongodb exits abnormally and will report an error the next time it starts. Some people say that you can delete the mongod.lock file. If deleting the mongod.lock file does not solve the problem, you can try to delete the lock file and execute the

./ bin/mongod --repair --dbpath /…/data/--repairpath /home/test/bakdata

/home/test/bakdata is the directory you created to store backup data, /…/data/is the directory mongodb stores data files. After this command is successfully executed, start mongodb normally, and you can succeed.

About how to solve the Mongodb abnormal shutdown after starting the error problem again to share the answer here, I hope the above content can be of some help to everyone, if you still have a lot of doubts not solved, you can pay attention to the industry information channel to learn more related knowledge.