Cause
The application is present but cannot start. The application cannot start the maximum allowed number of times. This alarm occurs with Event ID #20.
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 by examining the /var/log/ecs/wdlog log file.
- If the application is not running, enter start -s application to start the application.
- If the application starts successfully, continue with Step 7.
If the application fails to start, check the trace log to determine the reason why the application fails to start:
- From the Web interface:
Select View System Logs diagnostic, and Logmanager Debug trace.
Specify the Event Range for the appropriate time frame.
Match the application PID as the pattern.
- From the Linux command line, enter logv -t ts.
Locate a related core-dump file in /var/crash directly, and go to the Avaya Support website at http://support.avaya.com to open a service request.
- Check if the file named in the log exists and is executable.
To locate the executable file of the application, enter the Linux command:
ls -l /opt/ecs/sbin/appl
If the file is present, Linux returns a symbolic link to its location.
- If the file is present:
- Enter ls -l on the address of the symbolic link.
- Check if the file has execute permissions. If the file does not have execute permission, enter chmod +x to enable execution permission for 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.