Disabling and Re-enabling ACM on One Node

Use the ACM Control Command (acmctl) to disable and re-enable ACM on a single node.

If you disable ACM locally on the active node, another node running ACM eventually takes over, possibly generating conflicting access to some common files on the shared storage. You should always use this option with extreme caution, and stop all the Faspex services (asctl all:stop) on the active node immediately after you disabled ACM locally.

  1. To disable ACM for one node only, run acmctl with the -d option on that node:
    # /opt/aspera/acm/bin/acmctl -d
    ACM is disabled locally
  2. To verify ACM’s status for a disabled node, run the acmctl –i command on that node:
    # /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
    ...
  3. To re-enable ACM on a node, run the acmctl command with the -e option on the node:
    # /opt/aspera/acm/bin/acmctl -e
    ACM is enabled locally