How do you stop a MongoD service that is managed by Ops Manager?

Justus_Niemeyer · 2025-04-04T07:50:43.926Z

Hello! I’m wondering how to manually, from the Linux OS, stop a mongod service on an instance that is managed by Ops Manager. Typically, I would do a systemctl stop mongod followed by a systemctl start mongod. However, since importing the cluster, “systemctl status mongod” shows the service as Failed despite the node being an active secondary when doing a rs.status().

TL;DR - If I wanted to manually stop the service from Linux, how would I do that if it isn’t systemctl stop mongod?

Thanks!

chris · 2025-04-04T17:11:46.578Z

Hi @Justus_Niemeyer

The first option is to use the Ops Manager UI or API to set the instance to shutdown.

To do that without Ops Manager being involved first the MongoDB Agent would have to be stopped then kill mongod. The MongoDB Agent is responsible for managing mongod once it is added to automation, if mongod were killed first the agent would restart mongod.

Justus_Niemeyer:

TL;DR - If I wanted to manually stop the service from Linux, how would I do that if it isn’t systemctl stop mongod?

First systemctl stop mongodb-mms-automation-agent then pkill -x mongod

system · 2025-04-09T17:11:47.315Z

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.