Differences

This shows you the differences between two versions of the page.

--- mongo_ops_operations_agent_management [2020/03/23 10:53] – created andonovj
+++ mongo_ops_operations_agent_management [2020/03/23 11:02] (current) – andonovj
@@ Line 1: / Line 1: @@
-====Overview====
+=====Overview=====
 As already discussed the OPS Manager is centralized based manager for Mongo. Ergo it has server and agent.
 Agent should be also running on the OPS Manager server, so let's check how stop start an agent:
+=====Server=====
+We can check the status of the manager as follows (on the manager machine of course)
+====Status====
+<Code:none|Check status of Ops Manager>
+[root@dbpafxjrl ~]# service mongodb-mms status
+Check Ops Manager status
+   Probing instance 0...[  OK  ]
+      The instance is running.
+Check Backup Daemon status[  OK  ]
+   Backup Daemon Process is running.
+[root@dbpafxjrl ~]#
+</Code>
+====Start====
+We can also start it as follows:
+<Code:none|Start Ops Manager>
+[root@dbpafxjrl ~]# service mongodb-mms start
+Starting pre-flight checks
+Successfully finished pre-flight checks
+Migrate Ops Manager data
+   Running migrations...[OK]
+Start Ops Manager server
+   Instance 0 starting............[OK]
+Starting pre-flight checks
+Successfully finished pre-flight checks
+Starting Backup Deamon....[OK]
+.........................
+[root@dbpafxjrl ~]#
+</Code>
+=====Agent=====
+Agent is installed on the server and the destination hosts and should be running everywhere.
+So let's see how to check it's status and how to stop start it:
 ====Status===
 <Code:none|Status of Agent process>
@@ Line 14: / Line 53: @@
 ====Start====
 <Code:none|Start Agent>
+[root@dbpafxjrl ~]# systemctl start mongodb-mms-automation-agent.service
 [root@dbpafxjrl ~]# systemctl status mongodb-mms-automation-agent.service
 ● mongodb-mms-automation-agent.service - MongoDB MMS Automation Agent