3.7.0 HP StorageWorks HP Scalable NAS File Serving Software administration guide - HP Scalable NAS 3.7 for Linux (AG513-96002, October 2009)

could occur if the Management Console is out of date and does not support the
version of HP Scalable NAS running on the server.
Event status
The Event status is displayed when monitor_agent encounters an error while
executing the probe, Start, Stop, or Recovery scripts.
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 HP Scalable NAS 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 daemon gave instruction to the
monitor_agent daemon, which is considered to be an illegal state transition for
a monitor. This indicates an internal error and should be reported to HP Technical
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. You can also view the
information in the cluster log file.
From the command line, use these commands to check the status of monitors:
mx service status
mx device status
Other cluster maintenance392