High Availability Installation |
For overview information about Aspera Cluster Manager (ACM), see Aspera Cluster Manager (Overview).
$ chkconfig aspera_mysqld off $ chkconfig aspera_httpd off $ chkconfig AsperaOrchestrator off
The acmctl command has an option to check that the necessary configurations have been made that allow the acm4orchestrator script to run appropriately. You should make sure that each server passes the sanity test.
Configure ACM services in crontab on both nodes so that the acm4orchestrator script is launched every minute.
$ crontab –e * * * * * /opt/aspera/acm/bin/acm4orchestrator ip_address > /dev/null 2>&1One parameter must be entered in crontab: the IP address of the host where the script is running. This parameter is passed to the acm4orchestrator script.
$ crontab –e * * * * * /opt/aspera/acm/bin/acm4orchestrator 10.0.71.21 > /dev/null 2>&1
Once configured in crontab, the acm4orchestrator script runs regularly to determine the active node and start the required Orchestrator services on both the active and passive nodes, depending on their current status (active or passive).
Obtaining the crontab Parameter Values
To list the IP addresses available on a system, run the following command:$ ip addr | grep "inet" inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host inet 10.0.75.21/16 brd 10.255.255 scope global eth0
$ stat -c "%d" /mnt/shared/orchestrator/acm_files/ 20/mnt/shared/orchestrator/acm_files/ is a placeholder for your shared storage mount point that contains ACM files.
/opt/aspera/acm/bin/acmctl -i
For
more information about using this command, see Disabling and Re-enabling ACM on One NodeIf the services are running properly, you can now connect to the Orchestrator application using the virtual IP address (VIP) assigned to the ACM cluster.
If the load balancer is correctly configured, you should now be able to connect to the Orchestrator web application using the URL pointing to the VIP