High Availability Installation / Maintenance of the High Availability Environment |
# /opt/aspera/acm/bin/acmctl -h Aspera Cluster Manager Control Command Version: 0.2 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
Checking current ACM status... Aspera Cluster Manager for Orchestrator - status ------------------------------------------ Local hostname: orchestrator2 Active node: orchestrator2 (me) Status of this node: active 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: 31524 -> Mongrel serving orchestrator on port 3000 is running with pid: 31636 -> Mongrel serving orchestrator on port 3001 is running with pid: 31681 -> Mongrel serving orchestrator on port 3002 is running with pid: 31685 -> Orchestrator Monitor running with pid: 31713 -> Asynchronous Worker Process 0 is running with pid: 31715 -> Asynchronous Worker Process 1 is running with pid: 31717 -> Synchronous Worker Process 2 is running with pid: 31719 -> Synchronous Worker Process 3 is running with pid: 31721 -> Synchronous Worker Process 4 is running with pid: 31723 -> Synchronous Worker Process 5 is running with pid: 31725 Orchestrator active/passive services status ------------------------------------------ MySQL: stopped
Aspera Cluster Manager for Orchestrator - status ------------------------------------------ Local hostname: orchestrator1 Active node: orchestrator2 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: 26932 -> Mongrel serving orchestrator on port 3000 is running with pid: 26967 -> Mongrel serving orchestrator on port 3001 is running with pid: 26970 -> Mongrel serving orchestrator on port 3002 is running with pid: 26973 -> Orchestrator Monitor running with pid: 26979 -> Asynchronous Worker Process 0 is running with pid: 26981 -> Asynchronous Worker Process 1 is running with pid: 26983 -> Synchronous Worker Process 2 is running with pid: 26985 -> Synchronous Worker Process 3 is running with pid: 26987 -> Synchronous Worker Process 4 is running with pid: 26989 -> Synchronous Worker Process 5 is running with pid: 26991 Orchestrator active/passive services status ------------------------------------------ MySQL: stopped
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 /opt/aspera/acm/run/acm4orchestrator.status file is current or has expired. A status of expired usually indicates a failover situation. The status file may not be available for a short period during failover, and the Status file may be stated as Unable to find. |
Disabled globally | Answers the question: Is ACM disabled for all Orchestrator 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. |
Orchestrator active/active service status | The apache service should have a status of running on both the active and passive servers. The mysqld, stats-collector, orchestrator-background-default-0, orchestrator-background-nodes-0, orchestrator-background-users-0, orchestrator-background-users-1, and orchestrator-background-users-2 services should all be running on the active server and not running on the passive server. |