Manually Failing-Over to the Passive Node

To force a passive node to assume the active role, disable ACM on the active node and stop all Faspex services on that node.

1. Determine the active node with the acmctl command.

   # /opt/aspera/acm/bin/acmctl -i
   Checking current ACM status...
   
   Aspera Cluster Manager status
   -----------------------------
   Local hostname:         hashares2 
   Active node:            hashares2  (me)
   Status of this node:    active
   ...

2. Disable ACM locally.

   # /opt/aspera/acm/bin/acmctl -d
   ACM is disabled locally

3. Check to confirm that no ACM instances are running.

   # ps aux | grep acm
   root 1248	0.0 	0.0 	103252	824	pts/0 	S+	17:18 0:00 grep acm4shares

4. Stop the Shares services.

   # service aspera-shares stop

5. Run the acmctl -i command to verify that all Faspex services have been stopped.

   # /opt/aspera/acm/bin/acmctl -i
   Checking current ACM status...
   
   ...
   
   Shares active/active services status
   ------------------------------------
   nginx:      not running
   crond:      not running
   
   Shares active/passive services status
   -------------------------------------
   mysqld:                      not running
   shares-background-default-0: not running
   shares-background-nodes-0:   not running
   shares-background-users-0:   not running
   shares-background-users-1:   not running
   shares-background-users-2:   not running
   

6. Check that the active node is no longer active.

   # /opt/aspera/acm/bin/acmctl -i
   Checking current ACM status...
   
   
   Aspera Cluster Manager status
   -----------------------------
   Local hostname:         hashares1
   Active node:            hashares2
   Status of this node:    passive
   Status file:            current
   Disabled globally:      no
   Disabled on this node:  yes
   ...

   And check that the other node is now the active one:

   # /opt/aspera/acm/bin/acmctl -i
   Checking current ACM status...
   
   Aspera Cluster Manager status
   -----------------------------
   Local hostname:         hashares1
   Active node:            hashares1 (me)
   Status of this node:    active
   Status file:            current
   Disabled globally:      no
   Disabled on this node:  no
   Database host:          10.0.143.6
   
   Console active/passive services status
   --------------------------------------
   Apache:	 running
   MySQL:	  running
   Console:	running
   
   ...
7. Re-enable ACM on the node that recently became passive to let it start the active/active Faspex services.

   # /opt/aspera/acm/bin/acmctl -e
   ACM is enabled locally

8. After a several minutes, you can verify that the active/active services have started on the passive node:

   # /opt/aspera/acm/bin/acmctl -i
   Checking current ACM status...
   
   Aspera Cluster Manager status
   -----------------------------
   Local hostname:         hashares2 
   Active node:            hashares1 
   Status of this node:    passive
   Status file:            current
   Disabled globally:      no
   Disabled on this node:  no
   
   Database configuration file
   ---------------------------
   Database host:        10.0.115.101
   
   Shares active/active services status
   ------------------------------------
   nginx:      running
   crond:      running
   
   
   ...