Avamar: Confirming ASCD is started on a Multinode Avamar Grid

If the Avamar Services Control Daemon (ASCD) process is not started, it can cause maintenance failures.

1. Log in to the Avamar Utility Node as admin and load the admin keys. See Avamar: How to Log in to an Avamar Server and Load Various Keys for instructions on loading keys.

2. Confirm that the ASCD process is running:

ps -ef | grep ascd 

Example output

admin    14423     1  0 Sep11 ? 00:00:00 ascd.bin --hfsport=27000 --probe file=/usr/local/avamar/var/probe.xml --sysdir=/usr/local/avamar/etc --windir=/usr/local/avamar/etc/gsan-maint-scripts --keyfile=/usr/local/avamar/etc/license.xml --scanfile=/usr/local/avamar/etc/serverlogscanners.xml --sysconfigdbfile=/usr/local/avamar/var/sysconfigdb.xml --logfile=/usr/local/avamar/var/ascd.log
admin    14424 14423  0 Sep11 ? 00:00:26 ascd.bin --hfsport=27000 --probe file=/usr/local/avamar/var/probe.xml --sysdir=/usr/local/avamar/etc --windir=/usr/local/avamar/etc/gsan-maint-scripts --keyfile=/usr/local/avamar/etc/license.xml --scanfile=/usr/local/avamar/etc/serverlogscanners.xml --sysconfigdbfile=/usr/local/avamar/var/sysconfigdb.xml --logfile=/usr/local/avamar/var/ascd.log

3. If the ASCD process is not running, examine /usr/local/avamar/var/ascd.log to confirm why it may be down.

If the root cause cannot be determined, create a Swarm with the Avamar L2 team for assistance.

4. Once the root cause has been determined, restart the ASCD process (as admin):

ascd start 

5. Confirm that it is running:

ps -ef | grep ascd

6. If the ASCD process is started, it is possible that it may be in an unresponsive state. See Avamar - How to test if ASCD is working correctly.