3.1.2 Matrix Server Administration Guide

Chapter 19: Other Matrix Maintenance 255

Matrix Server Exits Immediately

If the ClusterPulse daemon exits immediately on starting, check the last

lines of the following files for errors:

• /var/log/polyserve/matrix.log

• /var/log/polyserve/mxinit.log

This problem typically occurs because either the hostname is not set

properly on the server or the main Ethernet interface is not installed.

Refer to the ifconfig man page for ways to check this.

Browser Accesses Inactive Server

If you access a virtual host from a Web browser that is running on one of

the servers in a matrix, the browser accesses the service on the server it is

running on. Note that this allows you to monitor and test the inactive

server while the virtual host is fully operational.

Troubleshoot Monitor Problems

You may encounter the following problems with service and device

monitors.

Monitor Status

If the monitor status is not reported as Up, check the last error message

string and the last event message string that monitor_agent returned to

Matrix Server for any service or device monitor on any server in the

matrix. The error or event message provides more status information.

“Down” Status

The “Down” status indicates that the monitor finished its probe but it did

not complete successfully. Depending on the monitor type (such as HTTP

or SMTP), the service monitor probe may involve more than being able to

connect to the network service.

For many built-in service monitors, Matrix Server may conclude that the

monitor is down even if the TCP connection succeeds. For example, if a

Web server is available but the URL specified in the HTTP service