WD Event ID 24 S8300

Last Updated : Aug 31, 2023 |
Prolog information
Metadata
Keywords:
Alarm level
MAJ
Alarm text
Watchd’s high-monitor thread is stopping tickling of hw

Cause

The call of Event ID #23 to reboot the server was unsuccessfully invoked. A semaphore of the Linux kernel is stuck. Once this alarm is raised, Watchd stops the HW sanity timer prompting HW sanity watchdog to execute a hard reboot of the processor.

Proposed Solution

  1. To check if the alarm occurred, look for messages that indicate stopping stopping the tickling of the HW sanity timer and CPU occupancy profiling:
    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.
      ADDITIONAL INFORMATION:
      • If the HW sanity watchdog successfully executes a hard reboot, the alarm clears. This reboot fixes problems caused by unresponsive software.
      If the HW sanity watchdog fails to execute a hard reboot, disengage and reengage the power source of the server to release it from this condition and to clear the alarm.
  2. If the alarm persists, go to the Avaya Support website at http://support.avaya.com to open a service request.