AWS Thinkbox Discussion Forums

MongoDB Error - DeadlineDatabase8\mongo\data\mongod.lock. probably means unclean shutdown

when I was trying to lunch dead line i got error massage

I did check for the services and i found the deadline database service dose not running and not respond to the run command
I did check for the log and I find the massage:
2017-08-13T17:48:30.696+0200 I CONTROL Trying to start Windows service ‘MongoDB’
2017-08-13T17:48:30.698+0200 I STORAGE Service running
2017-08-13T17:48:30.701+0200 W - [initandlisten] Detected unclean shutdown - E:\DeadlineDatabase8\mongo\data\mongod.lock is not empty.
2017-08-13T17:48:30.727+0200 I STORAGE [initandlisten] **************
old lock file: E:\DeadlineDatabase8\mongo\data\mongod.lock. probably means unclean shutdown,
but there are no journal files to recover.
this is likely human error or filesystem corruption.
please make sure that your journal directory is mounted.
found 2 dbs.
see: dochub.mongodb.org/core/repair for more information


2017-08-13T17:48:30.736+0200 I STORAGE [initandlisten] exception in initAndListen: 12596 old lock file, terminating
2017-08-13T17:48:30.736+0200 I CONTROL [serviceStopWorker] dbexit: rc: 49

so how to solve this error ??

Try deleting that lock file and re-start the service. That should get you through.

unfortunately this dos not solve the problem
still getting the same error
any other suggestion

Is there a different error in the log when you delete the lock file? There may be a crash that would cause the lock file to remain.

I would also check the last few logs in case they do have other information.

If this is urgent, please call use at +1-866-419-0283 ext 2 and we can help out faster than via the forums.

Privacy | Site terms | Cookie preferences