Cause
The Lo-monitor thread is missing heartbeats (cannot get CPU time). The Hi-monitor thread has tried 3 times to recover the system by killing any infinitely looping processes. If the lo-monitor thread does not heartbeat even after three CPU-occupancy profiles and recoveries, the Watchd reboots the server.
Proposed Solution
Procedure
- To verify the alarm, look for messages containing the CPU profiling results and attempted recoveries and messages stating that Watchd is rebooting the server:
- From the Web interface, select .
- From the Linux command line, enter logv -w or directly examine the /var/log/ecs/wdlog log file.
No corrective action is necessary. The server restarts by the time a technician analyzes the system. A reboot clears the alarm and fixes problems with unresponsive software.
- 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.
