Avaya 03-300430 User Manual

Page of 2574
Alarms in Linux Media Servers
Issue 1 June 2005
107
 
15
S8300
MAJ
“Detected a rolling reboot” — Watchdog has detected “x” number of Linux 
reboots within “y” minutes (where x and y are configurable in /etc/opt/
ecs/watchd.conf). Rolling reboots have a wide variety of possible 
causes.
1. To verify the alarm, look for the message, “WARNING: Rolling reboot 
detected!!,“either using 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.
2. Escalate this problem for explicit guidance with the following steps.
3. Paying special attention to Communication Manager errors, continue 
examining the Watchdog log (from Step 
), and try to determine which 
application failed.
4. Verify that every executable file listed in watchd.conf exists and is 
executable.   Rolling reboots are often caused by executables in 
unexpected locations.
5. If the files and their locations are OK, investigate the trace log to 
isolate the cause, either from the:
- Web interface by:
a. Selecting the View System Logs diagnostic and Logmanager 
Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the “rolling reboot” pattern
- Linux command line, by entering logv -t ts
Table 31: _WD Alarms in Media Server  (continued)
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
 8 of 15