3.5.1 Matrix Server Administration Guide

Appendix B: Error and Log File Messages 333

Error getting cluster status from server: <exception string>

The <exception string> describes the error. The connection to the server on

port 9050 was successful but the first response from the server

experienced an I/O error.

Error logging in: I/O error connecting to server

An I/O error occurred during the authentication of the Management

Console to the ClusterPulse daemon. View recent entries in the matrix.log

file for indications of what might have happened.

Error when connecting to the server: version not found - Using the

latest version in the cache

By default, the Management Console checks the current software version

on the server to which it is being connected and then downloads the

appropriate software only if that version is not already in the local cache.

This message indicates that the version check failed and the Management

Console is using the software in its local cache.

Fencing operation failed, reboot NN.NN.NN.NN ASAP.

NN.NN.NN.NN stopped matrix communication DATE HH:MM but

cannot be excluded from the matrix because of a networking

or fencing hardware failure or misconfiguration. To protect

filesystem integrity, some or all filesystem operations may

be paused until NN.NN.NN.NN is rebooted or until fencing

operations can be performed.

The server is unresponsive but Matrix Server is unable to exclude it from

the matrix because the fencing device is not responding to the fencing

request. Possibly the Ethernet connection to the FibreChannel switch has

failed. The server should be rebooted as soon as possible.

Internal error: unable to initialize security

Internal error: unable to initialize security. Java program

problem. Contact service.

If you receive one of these messages, report it to PolyServe Technical

Support at your earliest opportunity.