3.4.0 Matrix Server Administration Guide

Appendix B: Error and Event Log Messages 232

psdNpN on NN.NN.NN.NN is stalled on locks from NN.NN.NN.NN

A DLM lock request has been outstanding for a long period of time on the

specified server. Probably the server is severely overloaded or is

experiencing a resource shortage. As a last resort, reboot the server to

clear the problem.

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 200 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 process has died on the server

you were logged onto.

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

process 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 PolyServe Management

Console provided with Matrix Server.