[SERVER-9822] db.shutdownServer() does not empty mongod.lock Created: 30/May/13  Updated: 30/May/13  Resolved: 30/May/13

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 2.2.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Jack Zhang Assignee: Scott Hernandez (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

2.2.2 linux


Operating System: ALL
Participants:

 Description   

on version 2.2.2:
db.shutdownServer() does NOT empty mongod.lock.
but on 2.4.3, it does empty the lock file.

The problem I experienced is:
If mongod.lock not clean, "numactl --interleave=all mongod -f xx" failed to start, but "mongod -f xx" works fine.

Thu May 30 13:10:49 [initandlisten] exception in initAndListen: 10310 Unable to lock file: /u10/mongodata/27017/mongod.lock. Is a mongod instance already running?, terminating
Thu May 30 13:10:49 dbexit:

My question is:
Is this a bug and fixed in 2.4.x?
Is there a workaround for this problem?

Thanks
Jack



 Comments   
Comment by Jack Zhang [ 30/May/13 ]

After another close look/testing.
We can not reproduce the error anymore.
Sorry for the trouble, you can close the ticket now.
Thanks
Jack

Comment by Scott Hernandez (Inactive) [ 30/May/13 ]

Please attach the log files from the shutdown so we can see if there are any errors during the process to account for this discrepancy.

Generated at Thu Feb 08 03:21:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.