4.1.0 HP PolyServe Matrix Server administration guide (T5392-96073, October 2010)

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 cluster log. To view the error, select the monitor on the
Management Console, right-click, and select View Last Error.
From the command line, use these commands to check the status of monitors:
mx service status
mx device status
Clear an error
After you have determined the cause for a script event, be sure to correct the script
on all servers that reported the event and then clear the error. On the Management
Console, select the monitor, right-click, and select Clear Last Error. To clear an error
from the command line, use these commands:
mx service clear <vhost:port> <server> ...
mx device clear <devicename> <server> ...
Because the error is server-specific, you must clear it on each server in the cluster
(just as you had to correct the script on each server that reported a problem).
Other cluster maintenance270