3.1.2 Matrix Server RHEL4 Release Notes

PolyServe Matrix Server Release Notes 13

Open Issues and Workarounds

The following open issues affect Matrix Server operations.

Matrix Server

Defect

Description

982 Service monitor attempts to start before filesystem is mounted

PSFS filesystems can be configured to be mounted automatically

when the system is booted. This configuration is called a

persistent mount. When a server is booted, Matrix Server does

not wait for the persistent mounts to complete before it begins

other matrix operations.

This behavior can cause a virtual host to move among servers

under the following circumstance: A service monitor is

configured for an application that depends on a persistently

mounted filesystem, and the application is running on all

servers. If all of the servers are booted at once, the service

monitor may attempt to run on the primary server before the

filesystem is mounted. When the service monitor fails, the

virtual host associated with the monitor may move to another

server.

This behavior is repeated until the filesystem is mounted

somewhere in the matrix. The actual behavior of the monitor

and virtual host are dependent on the application and on the

activities specified in the scripts associated with the monitor.

To prevent this situation, create a

SHARED_FILESYSTEM device

monitor on the filesystem mount. This device monitor will

prevent the virtual host from being established on any server

that has not completed the filesystem mount.

1615 Resized log does not display properly

When you use the Set Log Length option to set the number of

lines to appear on the Server Log window, the Management

Console does not refresh the display. You will need to close the

Server Log window and then reopen it to see the resized log.