When you restart the RMM with the "rwadm restart" or "rwadm restart all" command, you may see a message similar to:



Checking if any operations are running on the RMM...


          Sync                                Active DR policy

------------------------               ----------------

linux-src -> linux-tgt                 testpol

Cannot stop RMM as operations are running. Use rwadm force-stop to stop the RMM.



As you can see above, there are two types of operations that may be active, Syncs, and DR Policies.  If there are syncs running, they are listed in  the 'Sync' column (note - the 'rw job query -t running' command can be used to see if any syncs are currently running)  If there are any DR Policies in a state of ACTIVE, those are listed in the 'Active DR policy'  column (note - the 'rw drpolicy show | grep ACTIVE' command can also be used to determine this).     


If either type of operation is active, the RMM will show the "Cannot stop RMM as operations are running. Use rwadm force-stop to stop the RMM" message when an 'rwadm restart' or 'rwadm restart all' command is issued. 


 There are several possible courses of action you could take if you wish to restart the RMM:


1)  If ‘rw job query -t running’ shows that there are no syncs in progress, and there are active policies, you can examine each of the policies to see what the schedule is for each policy.   If you are sure that none of them will be starting syncs any time soon (for example, the policy runs only once per day at 1 AM and it is now 2 PM), then it is safe to do “rwadm –force stop”, followed by “rwadm start”.  

 

2) If ‘rw job query -t running’ shows that there are no syncs in progress, you could pause all of the DR Policies (“rw drpolicy pause <drpolicy name>”).   The DR policies can also be paused from the GUI.   Once all the policies are paused, and there are no syncs in progress,  “rwadm restart” will restart the RMM.    Once the RMM is back up, resume all the policies you paused (“rw drpolicy resume <drpolicy name>”).


3) If 'rw job query -t running' shows that there are syncs in progress, you could pause all of the DR Policies, wait for the syncs to complete, and then issue 'rwadm restart'.    After the RMM is back up, resume the drpolicies


4) if 'rw job query -t running' shows that there are syncs in progress, you could cancel all of the syncs in progress, one wave at a time.   Use the 'rw wave stop <wave name>' command to stop all of the syncs in a given wave.    If any of the syncs are host syncs or stage2 syncs, then see 'Note for Stage 2 Syncs or Direct Syncs/Host Syncs' in https://rackware.freshdesk.com/a/solutions/articles/5000875147


5) if 'rw job query -t running' shows that there are syncs in progress, but the wave containing the syncs is in the Pausing state, then follow the steps in https://rackware.freshdesk.com/a/solutions/articles/5000875147