ACM Safety Check

After you can done the ACM setup, you will need to perform an ACM safety check.

Run an ACM sanity check with the following command.

$ /opt/aspera/acm/bin/acmctl –s
ACM sanity check
----------------
Checking if an entry for ACM seems to exist in the crontab                      
OK

Checking that the Orchestrator master service is disabled in chkconfig          
OK

Checking that SE Linux mode is not set to enforcing                            
OK

On one node, enable ACM.

$ /opt/aspera/acm/bin/acmctl –E
ACM is enabled globally

Check the cluster status on the active node.

$ /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: currentDisabled globally: no
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: 25123     
    -> Mongrel serving orchestrator on port 3000 is running with pid: 25219 
    -> Mongrel serving orchestrator on port 3001 is running with pid: 25222 
    -> Mongrel serving orchestrator on port 3002 is running with pid: 25225 
    -> Orchestrator Monitor running with pid: 25245 
    -> Asynchronous Worker Process 0 is running with pid: 25247 
    -> Asynchronous Worker Process 1 is running with pid: 25250     
    -> Synchronous Worker Process 2 is running with pid: 25252 
    -> Synchronous Worker Process 3 is running with pid: 25254 
    -> Synchronous Worker Process 4 is running with pid: 25259 
    -> Synchronous Worker Process 5 is running with pid: 25274

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

Check the status on the passive node.

$ /opt/aspera/acm/bin/acmctl –i
Checking current ACM status...
Aspera Cluster Manager for Orchestrator - status
------------------------------------------
Localhostname:          orchestrator2
Active node:            orchestrator1
Status of this node:    passive
Status file:            current
Disabled globally:      no
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: 2511  
-> Mongrel serving orchestrator on port 3000 is running with pid: 2642  
-> Mongrel serving orchestrator on port 3001 is running with pid: 2645  
-> Mongrel serving orchestrator on port 3002 is running with pid: 2648  
-> Orchestrator Monitor running with pid: 2654  
-> Asynchronous Worker Process 0 is running with pid: 2656  
-> Asynchronous Worker Process 1 is running with pid: 2658  
-> Synchronous Worker Process 2 is running with pid: 2660  
-> Synchronous Worker Process 3 is running with pid: 2662  
-> Synchronous Worker Process 4 is running with pid: 2664  
-> Synchronous Worker Process 5 is running with pid: 2666 

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

Check ACM log messages in the following file:
```
/var/log/aspera.log
```