Disabling ACM

When an upgrade is performed, ACM should be disabled.

Disable ACM on all nodes.

$ /opt/aspera/acm/bin/acmctl –D
ACM is disabled globally.

Once ACM is disabled, it will stop performing status file updates and it will transition to the expired state, per the example below. The services are allowed to continue running.

$ /opt/aspera/acm/bin/acmctl -i
Checking current ACM status...
Aspera Cluster Manager for Orchestrator - status
------------------------------------------
Local hostname:         orchestrator1
Active node:            orchestrator1 (me)
Status of this node:    active
Status file:            expired
Disabled globally:      yes
Disabled on this node:  no 
Database configuration file
---------------------------
Database host:        localhost

Orchestrator active/active services status
------------------------------------
Apache:               running 

Orchestrator Status:  
  -> Orchestrator Engine running with pid: 29500  
  -> Mongrel serving orchestrator on port 3000 is running with pid: 29590  
  -> Mongrel serving orchestrator on port 3001 is running with pid: 29593  
  -> Mongrel serving orchestrator on port 3002 is running with pid: 29596   
  -> Orchestrator Monitor running with pid: 29615  
  -> Asynchronous Worker Process 0 is running with pid: 29617  
  -> Asynchronous Worker Process 1 is running with pid: 29619  
  -> Synchronous Worker Process 2 is running with pid: 29621                                        
  -> Synchronous Worker Process 3 is running with pid: 29624  
  -> Synchronous Worker Process 4 is running with pid: 29626  
  -> Synchronous Worker Process 5 is running with pid: 29628 

Orchestrator active/passive services status
------------------------------------------
MySQL:                running

When you are ready to re-enable ACM, run the following command:
```
$ /opt/aspera/acm/bin/acmctl –E
ACM is enabled globally
```
If the active node calls acm4orchestrator before the passive node, it only updates the status file.

If the passive node calls acm4orchestrator before the active node, it does not perform an automatic failover, because the status file transitioned into current state upon re-enabling ACM.