[SERVER-7240] pidfile appears to be overwritten even when lock can not be obtained Created: 02/Oct/12 Updated: 21/Jun/22 Resolved: 10/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.2.0, 2.4.3, 2.6.4 |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Benno Leslie | Assignee: | Gregory Noma |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Execution Team 2022-06-13 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||
| Description |
|
The pidfile appears to be written even in the case where the database can't be started due to lockfile being locked. E.g: I think it would be better if in the case where the lockfile can't be obtained the PID file isn't updated. (i.e: the PID file should be protected by the lockfile). |
| Comments |
| Comment by Githook User [ 10/Jun/22 ] | |||||||||||||||||||||||||||||||
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: | |||||||||||||||||||||||||||||||
| Comment by Githook User [ 10/Jun/22 ] | |||||||||||||||||||||||||||||||
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: | |||||||||||||||||||||||||||||||
| Comment by Christopher Henderson [ 20/Jul/16 ] | |||||||||||||||||||||||||||||||
|
Confirmed for 2.6.8 and 3.2.8. | |||||||||||||||||||||||||||||||
| Comment by Thomas Rueckstiess [ 09/Sep/14 ] | |||||||||||||||||||||||||||||||
|
And confirmed for 2.6.4. | |||||||||||||||||||||||||||||||
| Comment by Gianfranco Palumbo [ 22/May/13 ] | |||||||||||||||||||||||||||||||
|
This occurs as well on Ubuntu Linux on mongod 2.4.3
|