3.1.2 Matrix Server Administration Guide

Chapter 19: Other Matrix Maintenance 259

“Activity Unknown” Status

For a brief period while the monitor_agent daemon checks the monitor

script configuration and creates a thread to serve the monitor, the activity

may be displayed as “activity unknown.”

“Transitioning” Activity

The “Transitioning” activity indicates that the monitor state is on its way

to becoming

ACTIVE or INACTIVE (or starting or stopping, if a Start or

Stop script is present).

“Starting” Activity

This activity is reported only when a Start script has been specified for the

monitor. It indicates that the monitor_agent thread is running the Start

script and the monitor is in the

STARTING state.

“Stopping” Activity

This activity is reported only when a Stop script has been specified for the

monitor. It indicates that the monitor_agent thread is running the Stop

script and the monitor is in the

STOPPING state.

Service Monitor Always Down

A network service monitor such as a generic TCP port monitor will

always appear as “Down” if the network application is configured to

bind to the host address and not to the virtual host address. One solution

is to modify the application so that it binds with the address of the virtual

host or the value of

INADDR_ANY. Remember, service monitors probe

the virtual host address and not the server’s host address. You can use the

netstat command to display the listening server sockets. If the Local

Address appears as host:port instead of virtual-host:port or *:port, the server

software should be reconfigured as described above.

Monitor Recovery

If a Recovery script is configured, a probe failure will not immediately

cause the monitor to become “Down.” The Recovery script is attempted

only once after the probe fails. However, when the monitor again reaches

the “Up” status, the Recovery script is again enabled to run if the probe

fails again later. A Recovery script is a valuable tool if you expect the