High Availability Installation / Maintenance of the High Availability Environment |
By default, ACM creates logging information only in the Linux syslog file. However, you may modify this default behavior by editing the /opt/aspera/acm/bin/acm4orchestrator file and changing the LOG_TO_FILE variable value to “1”. This directs ACM to generate a separate log file – /opt/aspera/acm/log/acm4orchestrator.log, which only contains data about ACM functions from either orchestrator server (the /opt/aspera/acm directory is shared by both servers).
# cd /opt/aspera/acm/bin # vi acm4orchestrator #! /bin/bash LOG_TO_FILE=0 LOG_TO_SYSLOG=1In this example, the value of LOG_TO_FILE ahs been changed to “1”; ACM now generates a separate log file.
# cd /opt/aspera/acm/bin # vi acm4orchestrator #! /bin/bash LOG_TO_FILE=1 LOG_TO_SYSLOG=1