3.4.0 Matrix Server Administration Guide

Appendix B: Error and Event Log Messages 234

ClusterPulse Messages

Bad command -- Could not find device monitor instance for XXX

on server YYY

The monitor_agent process is reporting status on a device monitor with

device name XXX on server YYY but the ClusterPulse process does not

recognize this device. Probably the Management Console has removed

the device monitor and monitor_agent has already sent the status to

ClusterPulse. Therefore, no corrective action is required.

Bad command -- Matrix Server process received an

unknown action or context reply from the agent monitor_agent:

[STATUS, EVENT,UNDEF] [SERVICE, DEVICE, UNKNOWN]

The message from the agent was not interpreted. This may indicate that

the versions of the monitor_agent and ClusterPulse processes are not the

same.

Configuration error -- could not write to configuration file

The ClusterPulse process was unable to write to the specified

configuration file. The text following the error message provides more

information about the problem. For example, it may state that a

filesystem is full.

Connection error -- send failed: N

Connection error -- transmit failed, no connection to

destination

Connection error -- total send failure

The ClusterPulse process experienced communication errors while trying

to send status to the PolyServe Management Console or an mx command.

The connection to the UI process needs to be re-established.

Internal system error -- Internal error at server X.X.X.X:

select returned with an unknown read socket N

Internal system error -- Internal error at server X.X.X.X:

select returned with an unknown write socket N