Mon May 1 21:25:21.620 [initandlisten] MongoDB starting : 256KB (512 sectors) or less
Mon May 1 21:25:21.621 [initandlisten] ** http://dochub.mongodb.org/core/readahead
Mon May 1 21:25:21.630 [initandlisten] exception in ilose listening sockets...
Mon May 1 21:25:21.630 [initandlisten] shutdown: going to flush diaglog...
Mon May 1 21:25:21.630 [initandlisten] shutdown: going to close sockets...
Mon May 1 21:25:21.630 [initandlisten] shutdown: waiting for fs preallocator...
Mon May 1 21:25:21.630 [initandlisten] shutdown: lock for final commit...
Mon May 1 21:25:21.630 [initandlisten] shutdown: final commit...
Mon May 1 21:25:21.630 [initandlisten] shutdown: closing all files...
Mon May 1 21:25:21.630 [initandlisten] closeAllFiles() finished
Mon May 1 21:25:21.630 dbexit: really exiting now
There are possible reasons, for reference:
1. MongoDB may be running, so you cannot start a new MongoDB database and use the same listening port;
But judging from the performance of your application, this possibility is relatively small.
2. File system permissions have changed;
Because it is 10310 Unable to lock file, please check whether the current operating system user has permissions to the lock file
3. MongoDB was not shut down correctly;
MongoDB was not shut down correctly. You can consider making a backup copy of the original lock file, then deleting it, and then restarting MongoDB. The steps are:
1) Make relevant backups;
2) Delete the lock file;
3) Restart, you may need to repair the database.
P.S. I found that version 2.4 is in use. It is recommended to upgrade to version 3.2+.
For reference.
Love MongoDB! Have fun!
Fortunately, I am in the hang-up state now, otherwise it would have turned black easily. Really, I am not trying to scare you