Avaya 03-300430 User Manual

Back to:              

             

24

MAJ

“Watchd’s high-monitor thread is stopping tickling of hw” — Event ID #23’s 
call to reboot the server was unsuccessfully invoked. (A Linux kernel’s 
semaphore is possibly stuck.) After this happens, Watchd stops tickling 
the HW sanity timer so that the HW sanity watchdog executes a hard 
reboot of the processor.

1. To verify that the alarm occurred, look for messages about:

Stopping the tickling of the HW sanity timer
CPU occupancy profiling

using either the:

- Web interface, by selecting Diagnostics > View System Logs 

and Watchdog Logs

- Linux command line, by entering logv -w or, directly, by 

examining /var/log/ecs/wdlog.

- If the HW sanity watchdog successfully executed a hard reboot, 

the alarm was cleared. (This reboot normally fixes problems due 
to unresponsive software.)

If not, power cycle the server to release it from this condition and to 
clear the alarm.

2. Watch to see if the alarm recurs. If so, escalate the problem.

 15 of 15