Cause
Application failed the maximum allowed number of times. This alarm usually occurs with Event ID #4.
Proposed Solution
Procedure
- To verify the alarm, locate the application name or process ID (PID):
- From the Web interface, select .
- From the Linux command line, enter logv -w or directly examine the
/var/log/ecs/wdlog log file.
- Check if the application is running:
From the Web interface, select View Process Status.
From the Linux command line, enter statapp.
- If the application is not running down, type start -s application to start the application.
- If the application starts, continue with Step 7.
If the application does not start, check the trace log to determine why the application failed to start:
- From the Web interface:
Select the View System Logs diagnostic and Logmanager Debug trace.
Specify the Event Range for the appropriate time frame.
Match the application’s PID as the pattern.
- From the Linux command line, enter logv -t ts
- To locate the executable file of the application, enter the command:
ls -l /opt/ecs/sbin/appl
If the executable is present, Linux returns a symbolic link to its location.
- If the file is present:
- Enter ls -l on the symbolic link’s address.
- Verify that the file has execute permissions. If not, enter chmod +x to enable execution of the application.
If the file is not present, Linux has returned a null link:
- Acquire the executable from the CD.
- Enter start -s application to start the application.
- Manually clear the alarm:
- From the Web interface, select Current Alarms and the appropriate alarm, and click Clear.
- From the Linux command line, enter almclear -n #id.
- If the problem persists, go to the Avaya Support website at http://support.avaya.com to open a service request.