Server Alarms - Avaya Support

Table 41: _WD Alarms 4 of 16
Event
ID
5
(cont’d)
6
S8300
Alarm
Level
Alarm Text, Cause/Description, Recommendation
_WD (Watchdog)
MIN 6. If rebooting the server does not help or if the problem recurs, escalate
the problem to the next higher tier.
MAJ “Application (pid) not started, config parm errors” — Watchdog
cannot read its configuration file, /etc/opt/ecs/watchd.conf.
1. To verify the alarm, look for the application’s name or process ID
(PID), 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. Get a fresh copy of watchd.conf from the CD.
3. Verify that every executable file listed in watchd.conf exists and is
executable.
4. Enter start -s application to start the application.
5. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
4 of 16
Communication Manager Release 5.0 Issue 4 January 2008 129