The ACM Control Command (acmctl)

You can use acmctl to diagnose and configure ACM.

Overview of the ACM Control Command (acmctl)

The acmctl command controls the ACM. Running it with the –h (Help) option displays the available command options:
# /opt/aspera/acm/bin/acmctl -h
Aspera Cluster Manager Control Command
Version: 1.97
Usage: acmctl {option}
List of options:
-i: Display the current state of ACM
-s: Perform a sanity check of ACM
-D: Disable ACM globally
-E: Enable ACM globally
-d: Disable ACM locally
-e: Enable ACM locally
-b: Back up the MySQL database (active node only)
-A: Display information about the version

Check that ACM works correctly

You can use the ‐i option to display the current status of ACM on a node output shown from the active node:
Aspera Cluster Manager status
-----------------------------
Local hostname:         faspex-ha2 
Active node:            faspex-ha2 (me)
Status of this node:    active
Status file:            current
Disabled globally:      no
Disabled on this node:  no

Database configuration file
---------------------------
Database host:        10.0.115.102

Faspex active/active services status
------------------------------------
Apache:               running
Faspex Mongrels:      running

Faspex active/passive services status
-------------------------------------
MySQL:                running
Faspex Background:    running
Faspex NP Background: running
Faspex DS Background: running
Faspex DB Background: running

The following is an example of the acmctl –i output on the passive node:

Aspera Cluster Manager status
-----------------------------
Local hostname:         faspex-ha1 
Active node:            faspex-ha2
Status of this node:    passive
Status file:            current
Disabled globally:      no
Disabled on this node:  no

Database configuration file
---------------------------
Database host:        10.0.115.102

Faspex active/active services status
------------------------------------
Apache:               running
Faspex Mongrels:      running

Faspex active/passive services status
-------------------------------------
MySQL:                stopped
Faspex Background:    stopped
Faspex NP Background: stopped
Faspex DS Background: stopped
Faspex DB Background: stopped

Data Provided by acmctl -i

On both the active and passive systems, the output of the acmctl -i command provides useful information about the status of the Faspex servers:
Output Element Definition
Hostname The name of the local system.
Active node The name and IP address of the node that is currently the active node.
Status [of] file Whether the common status file is current or has expired. A status of expired usually indicates a fail-over situation. The status file may not be available for a short period during fail-over, and the Status file may report as Unable to find.
Disabled globally Answers the question: Is ACM disabled for all Faspex servers?
Disabled on this node Answers the question: Is ACM disabled on this node?
Database host The system that is currently managing the MySQL database files.
Faspex active/active service status The apache and crond services should have a status of running on both the active and passive servers. The MySQL, Faspex Background, Faspex NP Background, Faspex DS Background, Faspex DB Background services should all be running on the active server and stopped on the passive server.