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!
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.
First systemctl stop mongodb-mms-automation-agent then pkill -x mongod
Closed 1 day ago
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.
| Topic | Replies | Views | Activity |
|---|---|---|---|
| Error while installing MongoDB Compass Isolated Edtion on Windows Server | 0 | 424 | Jul 2024 |
| Unable to establish remote cursors | 0 | 324 | Jul 2024 |
| Mongodump / Mongorestore on two different versions of MongoDB (4.2 and 7.0) | 0 | 69 | Aug 2024 |
| Microk8s Kubernetes and connecting by Service Name | 0 | 55 | Nov 2024 |
| AWS Private endpoints and MongoDB projects and clusters | 0 | 6 | 23d |
