Restarting Applications Manager v8.0 After a UNIX System Failure

Document ID : KB000089774
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Restarting Applications Manager v8.0 After a UNIX System Failure
Resolution:

Symptoms

After a UNIX/Linux system failure the Applications Manager processes can not be restarted.


Troubleshooting Steps:

Logged into your Unix/Linux system as the Applications Manager (AM) user from the $AW_HOME subdirectory follow these steps.

1) Stop all the AM processes using the following commands:
    . site/sosite
    stopso all
    stopso awcomm
    apachectl stop

2) Check to ensure all processes have been stopped using:
    ps -af|grep <AM username>
   If there are any AM processes still running, kill them.
3) Remove the files in the $AW_HOME/status subdirectory.
4) Restart AM using the following commands:
    startso all
    apachectl start

5) Check to ensure that all processes have started.
    ps -af|grep <AM username>
   or issue
    awexe node
   This call should return the following columns: agent, status, elapsed time, automation engine/agent/group, max threads, tasks in the backlog, running tasks, tasks on hold, aborted tasks, running scheduled tasks and should look similar to this:

V80                          Running 00:00:41     M   99     0   0   0   0   0
V80                          Running 00:00:55     A   99     1   0   0   0   0

  
If for some reason AM does not start successfully
5) Continue to troubleshoot the issue by looking at the most recent logs in the $AW_HOME/log subdirectory for errors.
6) Ensure that the Oracle database is available.
    a) Can you log into SQL Plus as the AM Oracle userid?
    b) Is the Oracle listener is up.
    c) Contact your Oracle DBA to ensure Oracle is functioning correctly.
    
Once the errors found are resolved follow steps 1 through 4 to stop and restart all AM processes.

If you are still not able to restart Applications Manager, contact Automic Support for additional assistance.