Filter
Top Products
Alarms in Linux Media Servers
Issue 1 June 2005 109
19
S8300
MIN “Application failed unintentionally” — Watchdog is bringing the system
down because an application failed to start correctly. The application may
have failed to start either because:
● The file did not exist (coincident with Event ID #7).
● Required application parameters were missing or invalid in
watchd.conf.
1. To verify the alarm, look for the message, “Application num <#>
(<application path>) not started. Watchdog exiting NOW,” 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. Verify that the file named in the log exists and is executable.
3. Verify that the string in watchd.conf is correct.
4. If Steps 2
and 3 are OK, investigate the trace log to see why the
application fails, 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 number as the pattern
- Linux command line, by entering logv -t ts
5. Once resolved, 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
Table 31: _WD Alarms in Media Server (continued)
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
10 of 15