3.5.1 Matrix Server Administration Guide

Appendix B: Error and Log File Messages 332

NN.NN.NN.NN should be rebooted ASAP as it stopped matrix

network communication DATE HH:MM:SS and was excluded from

the SAN to protect filesystem integrity

The server was excluded from the matrix because it could no longer

communicate over the network. The server should be rebooted at the first

opportunity. Also check the network and make sure that the server is not

experiencing a resource shortage.

NN.NN.NN.NN should be rebooted ASAP as it was excluded from

the SAN to protect filesystem integrity

The server was excluded from the matrix because it could no longer

communicate over the network. The server should be rebooted at the first

opportunity. Also check the network and make sure that the server is not

experiencing a resource shortage.

Error adding <entity>: I/O error sending to server

Error disabling <entity>: I/O error sending to server

Error enabling <entity>: I/O error sending to server

Error updating <entity>: I/O error sending to server

If you receive one of these errors, you can attempt to resolve it by

restarting Matrix Server. If this is unsuccessful, call PolyServe Technical

Support.

Error connecting to server <host>: unknown host

The server identified as <host> is not responding to the connection request

from the Management Console. Verify that you typed a valid hostname or

IP address in the connection window. This error may indicate that the

ClusterPulse daemon is not running; restart Matrix Server on the server.

Error connecting to server: I/O error

Error connecting to server

An error occurred when Matrix Server tried to connect to the specified

server through the connection window.