Server Alarms - Avaya Support

Server Alarms
Table 41: _WD Alarms 13 of 16
Event
ID
22
S8300
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN “Application () terminated” — Watchdog successfully shut
down the named application, and (if appropriate) watchdog will try to
restart it.
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
2. On the standby server, look for occurrences of the stop command,
either from the:
- Web interface, by:
a. Selecting View System Logs
b. Selecting Platform command history log
c. Specifying the Event Range for the appropriate time frame
d. Matching the “Stop” pattern
- Linux command line, by entering listhistory
3. If a stop command was inappropriately executed, prevent any future
misuse of the stop command.
Note: From the system’s perspective, this is normal behavior.
However, in terms of potential service outage due to human error, this
is quite irregular. (Shutting down a server effectively downgrades a
duplex-, high- or critical-reliability system to an unsupported
standard-reliability system.)
4. If listhistory shows no stop commands, then Watchdog
responded to abnormal internal processes by shutting down the
application.
Check the trace log for information about this application, 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 application’s PID as the pattern
- Linux command line, by entering logv -t ts
138 Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers
13 of 16