WD Event ID 22 S8300

Last Updated : Aug 31, 2023 |
Alarm level

MIN

Alarm text

Application <name> (<pid>) terminated

Cause

Watchdog successfully shut down the named application, and if necessary, watchdog will restart the application.

Proposed Solution

Procedure

  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.
  2. On the standby server, look for occurrences of the stop command:
    1. From the Web interface:

      1. Select View System Logs.

      2. Select Platform command history log.

      3. Specify the Event Range for the appropriate time frame.

      4. Match the Stop pattern.

    2. From the Linux command line, enter listhistory.
  3. If a stop command was inappropriately executed, prevent any future misuse of the stop command.
    Note:

    From the system’s perspective, this is normal behavior. However, in terms of potential service outage due to human error, this is irregular. Shutting down a server effectively downgrades a duplex, high or critical-reliability system to an unsupported standard-reliability system.

  4. If listhistory shows no stop commands, Watchdog responded to abnormal internal processes by shutting down the application.

    Check the trace log for information about this application:

    1. From the Web interface:

      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 PID as the pattern.

    2. From the Linux command line, enter logv -t ts
  5. 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.
  6. Check if the alarm persists. If the alarm persists, go to the Avaya Support website at http://support.avaya.com to open a service request.