[SERVER-38589] service mongod stop may produce No /usr/bin/mongod found running; none killed. Created: 13/Dec/18  Updated: 27/Oct/23  Resolved: 13/Feb/19

Status: Closed
Project: Core Server
Component/s: Packaging
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Kelsey Schubert Assignee: Matt Lord (Inactive)
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Sprint: Build 2018-12-31, Build 2019-01-14, Build 2019-01-28
Participants:
Story Points: 2

 Description   

A fix should be applied to https://github.com/mongodb/mongo/blob/6c8dc5e004bf2c91df10975adef861bcf00af6cd/debian/init.d to prevent this error when stopping mongod.



 Comments   
Comment by Matt Lord (Inactive) [ 13/Feb/19 ]

Removing the --exec call doesn't seem like good behavior to me. Given that:

  1. Ubuntu and Debian both use the exact same `start-stop-daemon` call in their init.d scripts that we are (e.g. see the one from canonical)
  2. It's standard/good practice to use --exec to ensure that you're actually going to be stopping the specific daemon associated with the service – which is /usr/bin/mongod, the same binary we're starting with the service (e.g. see grep "start-stop-daemon" "exec" /etc/init.d/*)
  3. There's something odd/unexpected happening in the specific case noted, which I don't fully understand.

Changing our behavior here doesn't seem wise so closing the ticket with "Works as Designed". If anybody does find related information and thinks that this is a mistake, I'm happy to re-open it and discuss further.

Generated at Thu Feb 08 04:49:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.