Mongodb startup error report
MongoDB-problem occurred during startup
Repair method
MongoDB- problem occurred during startup mongod is not executed in the background, after the terminal connection is abnormally disconnected, execute mongod again to report an error
Repair method
This is a common error in Mongod startup. The lock file was not killed when it was shut down illegally. When the lock file was checked for the second startup, this error was reported.
Solution: Enter the data directory specified when mongod was started last time –dbpath=/data/mongodb and
delete the file:
1
|
rm /data/db/mongo.lock |
Then execute:
1
|
./mongod --repair |
OK, the problem is solved.
The correct way to close mongod: enter the mongo shell
1
2
|
use admin db.shutdownServer() |
Please don’t kill -9, it will cause confusion and loss of file data. Repair will also be unable to recover.
ctrl+c can exit the mongo interface or ext
Similar Posts:
- [Solved] MongoDB Start ERROR: child process failed, exited with error number
- Mongodb Cannot Start: child process failed, exited with error number 100
- [Solved] Mongodb Error: NETWORK [thread1] Failed to connect to 127.0.0.1:27017
- MongoDB Startup Error: Failed to connect to 127.0.0.1:27017, reason: errno:111 Connection refused
- MongoDB:Unclean shutdown detected
- Unable to start mongod after installing mongodb in Ubuntu
- Raspberry pie: How to Solve Mongodb installation error
- No package mongodb-org available. [How to Solve]
- How to Solve MongoDB Error: Authentication failed.
- mongodb:E QUERY [thread1] SyntaxError: missing ; before statement @(shell):1:4