[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: The problem I experienced is: 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 My question is: Thanks |
| Comments |
| Comment by Jack Zhang [ 30/May/13 ] |
|
After another close look/testing. |
| 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. |