Proposed Solution

1. To verify the alarm, locate the application name or process ID (PID):
   1. From the Web interface, select Diagnostics View System Logs Watchdog Logs.
   2. From the Linux command line, enter logv -w or directly examine the /var/log/ecs/wdlog log file.
   3. Check if the application is running:
      ADDITIONAL INFORMATION:

      • From the Web interface, select View Process Status.
      • From the Linux command line, enter statapp.
2. If the application is not running down, type start -s application to start the application.
3. If the application starts, continue with Step 7.
   ADDITIONAL INFORMATION:

   If the application does not start, check the trace log to determine why the application failed to start:
   1. From the Web interface:
      ADDITIONAL INFORMATION:

      1. Select the View System Logs diagnostic and Logmanager Debug trace.
      2. Specify the Event Range for the appropriate time frame.
      3. Match the application’s PID as the pattern.
   2. From the Linux command line, enter logv -t ts
4. To locate the executable file of the application, enter the command:
   ADDITIONAL INFORMATION:

   ls -l /opt/ecs/sbin/appl

   If the executable is present, Linux returns a symbolic link to its location.
5. If the file is present:
   1. Enter ls -l on the symbolic link’s address.
   2. Verify that the file has execute permissions. If not, enter chmod +x to enable execution of the application.
      ADDITIONAL INFORMATION:

      If the file is not present, Linux has returned a null link:
   3. Acquire the executable from the CD.
6. Enter start -s application to start the application.
7. Manually clear the alarm:
   1. From the Web interface, select Current Alarms and the appropriate alarm, and click Clear.
   2. From the Linux command line, enter almclear -n #id.
8. If the problem persists, go to the Avaya Support website at http://support.avaya.com to open a service request.