Cause
Watchdog is shutting down the system down because an application failed to start correctly. The application failed to start because of the following:
The file did not exist, similar to Event ID #7.
Required application parameters were missing or invalid in watchd.conf.
Proposed Solution
Procedure
- To verify the alarm, locate the message, Application num <#> (<application path>) not started. Watchdog exiting NOW:
- From the Web interface, select .
- From the Linux command line, enter logv -w or directly examine the /var/log/ecs/wdlog log file.
- Check if the file named in the log exists and is executable.
- Check if the string in watchd.conf is correct.
- If Step 2 and Step 3 are okay, investigate the trace log to see why the application fails, either from the:
- From the Web interface:
Select the View System Logs diagnostic and Logmanager Debug trace.
Specify the Event Range for the appropriate time frame.
Match the application number as the pattern.
- On the Linux command line, type logv -t ts
- Once resolved, manually clear the alarm:
- From the Web interface, select Current Alarms and the appropriate alarm, and click Clear.
- From the Linux command line, enter almclear -n #id.