[SERVER-13607] mongod 2.4.10 does not delete PID file on exit Created: 16/Apr/14 Updated: 19/Nov/16 Resolved: 14/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | 2.4.10, 2.6.3, 2.7.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Stefan Seide | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
x86_64 |
||
| Issue Links: |
|
||||||||
| Operating System: | Linux | ||||||||
| Steps To Reproduce: | add pidfilepath=/data/db/mongod.pid to config file |
||||||||
| Participants: | |||||||||
| Description |
|
my /etc/mongod.conf defines an pidfile. On server startup the pid file gets created with the correct process id in it. System ubuntu 12.04 / 64bit Best regards |
| Comments |
| Comment by Kelsey Schubert [ 14/Nov/16 ] |
|
Hi stefan@seide.st, This is the intended behavior. If the lock file is present, then the PID file is valid. If the lock file is not present, then the PID file is either stale (and can be overwritten) or can be used to check for error conditions (the lock file was removed but the process is still running). Kind regards, |
| Comment by Stefan Seide [ 04/Jul/14 ] |
|
Hi Thomas, sorry for being late. I modified the upstart script to start mongodb with "mongodb -vv --config /etc/mongodb.conf", using the same config file es before and executed the "service mongodb start" and "service mongodb stop" commands. The last lines of the logfile /var/log/mongodb/mongodb.log are: Fri Jul 4 14:44:45.183 [journal] journal REMAPPRIVATEVIEW done startedAt: 2 n:2 0ms Fri Jul 4 14:44:45.487 [conn5] run command admin.$cmd { replSetHeartbeat: "rs0", v: 32013, pv: 1, checkEmpty: false, from: "db02:27017" }Fri Jul 4 14:44:45.487 [conn5] command: { replSetHeartbeat: "rs0", v: 32013, pv: 1, checkEmpty: false, from: "db02:27017" }Fri Jul 4 14:44:45.487 [conn5] command admin.$cmd command: { replSetHeartbeat: "rs0", v: 32013, pv: 1, checkEmpty: false, from: "db02:27017 " } ntoreturn:1 keyUpdates:0 reslen:209 0ms |
| Comment by Thomas Rueckstiess [ 03/Jul/14 ] |
|
Hi Stefan, We still need the log file that covers the shutdown to continue on this issue. Can you attach it please? Thanks, |
| Comment by Thomas Rueckstiess [ 01/May/14 ] |
|
Hi Stefan, I meant just the part where it shows the shutdown of mongod. If you can repeat the process with a higher verbosity level (for example by adding -vv to the command line when starting mongod) and providing the higher verbosity log file, that would be even better. Thanks, |
| Comment by Stefan Seide [ 22/Apr/14 ] |
|
my current configuration "/etc/mongodb.conf" is quit short, it just contains the following 5 parameter: == the effective commandline ( taken from 'ps ax') is What kind of log snippet do you mean? started with some special debug/logging flags? |
| Comment by Thomas Rueckstiess [ 17/Apr/14 ] |
|
Hi Stefan, Can you provide a log snippet that contains the shutdown messages? Can you also provide your mongod.conf? Thanks, |