[SERVER-43363] mongod --bind_ip_all zombie process and failing service start Created: 17/Sep/19  Updated: 17/Sep/19  Resolved: 17/Sep/19

Status: Closed
Project: Core Server
Component/s: Admin, Stability, Usability
Affects Version/s: 4.2.0
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Alex Giokas Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

No steps, seems to have happened randomly.

Participants:

 Description   

I've run into this issue today on Ubuntu 18.04 using 4.2.0 mongod CE:

  1. `sudo service mongod start` fails
  2. looking into the log `/var/log/mongodb/mongod.log` shows that it failed to start because another process is listening (Socket in use) error code 48
  3. doing a `ps wuax | grep mongo` I can see that a process of mongod is already running as `mongod --bind_ip_all` user 999
  4. killing it with `kill -9 $PID` doesn't do anything, the process respawns. using pkill or htop to send different kill commands also fail, the process stays there/respawns with new pid.
  5. terminating it with `sudo service mongod stop` doesn't do anything, it still stays running
  6. connecting to it via mongo cli simply hangs-up at the connecting part.

 

This happened without any abnormal termination or closure of the platform.

Short of uninstalling and re-installing, I have no other way to use mongod at this point?



 Comments   
Comment by Danny Hatcher (Inactive) [ 17/Sep/19 ]

Thanks for letting us know.

Comment by Alex Giokas [ 17/Sep/19 ]

Feel free to close, another user was running a dockerized instance of mongod on start-up and was prohibiting the service'd mongod from starting at boot-time. 

Generated at Thu Feb 08 05:02:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.