[SERVER-14338] mongod/s should refuse to overwrite pidfiles belonging to a running process Created: 23/Jun/14 Updated: 09/Sep/14 Resolved: 09/Sep/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.6.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pat Gunn | Assignee: | Matt Kangas |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Steps To Reproduce: | 1) Manually start a mongos/d with a named pidfile |
||||||||||||
| Participants: | |||||||||||||
| Description |
|
When mongod/s starts up, if it is told to use a pidfile, it will overwrite that pidfile, even if that pidfile belongs to another mongod/s process that is currently running. It should check to see if the pid in the pidfile is active and refuse to start if it is given a pidfile that corresponds to a running process. (This was found on MongoDB 2.6.1 on Linux and is believed to be present on 2.6.3 ; found as part of an investigation of an issue on the MMS cloud servers) |