3.1.2 Matrix Server Administration Guide

Appendix B: Error and Log File Messages 273

ClusterPulse Messages

Bad command -- Could not find device monitor instance for

XXX on server YYY

The monitor_agent daemon is reporting status on a device monitor with

device name XXX on server YYY but the ClusterPulse daemon 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 daemon 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 daemons are not the

same.

Configuration error -- could not write to configuration file

The ClusterPulse daemon 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.

Configuration file error -- could not open configuration

file

The ClusterPulse daemon was unable to open the configuration file

/etc/opt/polyserve/cp_conf. Verify that root has write access to the file.

Connection error -- send failed: N

Connection error -- transmit failed, no connection to

destination

Connection error -- total send failure

The ClusterPulse daemon experienced communication errors while

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

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