3.6.1 HP PolyServe Matrix Server Administration Guide (T5392-96018, August 2008)

Chapter 21: Other Matrix Maintenance 295
The status of the monitor may be “Up” even though an event has been
reported. This is the case if the error was not serious enough to stop the
execution of the script.
The events are:
CONFIG_ERROR. A script must exist and be executable by root. This
condition is checked for probe, Start, Stop, and Recovery scripts each time
an attempt is made to execute the script.
SCRIPT_SYSERR. The monitor_agent tried to fork a process to execute the
script but the fork system call failed. This condition can occur when
Matrix Server is trying to execute probe, Start, Stop, or Recovery scripts.
START_TIMEOUT. A Start script was executed but it did not complete
within the specified timeout period.
STOP_TIMEOUT. A Stop script was executed but it did not complete
within the specified timeout period.
RECOV_TIMEOUT. A Recovery script was executed but it did not
complete within the specified timeout period.
START_FAILURE. A Start script was executed but it returned a non-zero
exit status.
STOP_FAILURE. A Stop script was executed but returned a non-zero exit
status.
RECOV_FAILURE. A Recovery script was executed but returned a non-
zero exit status.
ILLEGAL TRANSITION. The ClusterPulse process gave instruction to the
monitor_agent process, which is considered to be an illegal state
transition for a monitor. This indicates an internal error and should be
reported to HP Support.
The event is written into the event log. To view the error, select the
monitor on the Management Console, right-click, and select View Last
Error.