3.5.1 Matrix Server Administration Guide

Appendix B: Error and Log File Messages 337

Reboot <server> ASAP as it stopped matrix network

communication at date/time but attempts to exclude it

from the SAN were unsuccessful!

Rebooting it will allow normal matrix operation to continue.

Alternatively, if the server cannot be rebooted, but can be

confirmed to have no access to the SAN, run ‘mx server markdown

<server>' to restore normal matrix operation.

Matrix Server cannot fence a server that is no longer communicating with

the matrix. Either reboot the server or run the mx server markdown

command to restore normal operations.

Before using mx server markdown, be sure that the server is physically

down. If the command is run on a server that is not down, filesystem

corruption can occur. See “Server Cannot Be Fenced” on page 301 for

more information about the mx server markdown command.

Server closed connection

connection to the server was lost

Either the server has closed the communication connection to the

Management Console or the ClusterPulse daemon has died on the server

you were logged onto.

Log on to the server if you are remote. Verify that the ClusterPulse

daemon is still executing and restart Matrix Server if necessary.

Server protocol version received from <host> is incompatible

with this console version.

Verify that you are using the version of the Management Console

provided with Matrix Server.

Singleton matrix unable to take control of SAN, because the

matrix that includes NN.NN.NN.NN currently controls the SAN.

Possibly this server has not been added to the matrix or has

been deleted from the matrix, or possibly a networking

failure or misconfiguration has partitioned this server from

the servers that control the SAN.

Check the matrix configuration and add the server if it is not currently a

member. Also check the network to ensure that the server can

communicate with the rest of the matrix.