Avamar: ATO or ADMe fails to start a job policy

ADMe job policy when initiated does not go active.

This occurs after the Utility node has been rebooted as this daemon by default is not configured to start automatically.

Avamar Tape Out (ATO) and ADMe job policies fail to run:
 

atd daemon is not started

ATO or ADMe job policies are initiated using the at command which relies on the atd daemon being started.

1. Verify whether an atd daemon is started:

ps -ef | grep atd


root     25738 18289  0 10:52 pts/0    00:00:00 grep atd
at       30681     1  0  2013 ?        00:00:00 /usr/sbin/atd  <--- this line indicates it is started correctly

2. If an appropriate atd line is returned ensure that its path includes /usr/sbin as shown above. If not, then kill its associated process identifier (pid).

kill -15 pid-number

Otherwise, the atd daemon is already started and is probably not the cause of the issue.

3. If no appropriate atd line was returned from Step-1 or if you killed the pid in Step-2, start the daemon by using the following syntax:

/usr/sbin/atd

ATO or ADMe checks for the atd daemon being started using its complete path /usr/sbin any time. The ATO or ADMe menu is opened using either ATO or ADMe commands. When it fails to detect being started with its complete path name the following message displays:

[CMD=/usr/sbin/atd]