3.6.0 Matrix Server Command Reference (5697-7083, December 2007)

Chapter 3: mx Commands 107
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
CUSTOM monitor. The parameter is a probe script.
[--ordering SERIAL|PARALLEL]
Whether Matrix Server enforces a strict ordering sequence when it runs Start
or Stop scripts. The default is serial, the strict ordering sequence.
[--recoveryScript <script>]
Runs after a monitor probe failure is detected, in an attempt to restore the
service.
[--recoveryTimeout <seconds>]
The amount of time to wait for the script to complete.
[--startScript <script>]
When Matrix Server selects the active server for a monitored service, the Start
script runs on that server.
[--stopScript <script>]
A script that runs on all other servers configured for the service monitor to
ensure that the service is not active on those servers.
[--startTimeout <seconds>]
The amount of time to wait for the Start script to complete.
[--stopTimeout <seconds>]
The amount of time to wait for the Stop script to complete.
[--eventSeverity consider|ignore]
Whether Matrix Server takes service monitor events (such as a failure or
timeout of a Start or Stop script) into consideration when it makes failover
decisions. The default is consider.
[--priority <priority>]
The priority of the service monitor in relation to other service monitors.
priority is a natural number; 0 is the highest priority. Matrix Server uses the
priority when failing over the virtual host associated with the monitor. If
multiple failures have occurred, all of the services associated with the virtual
host may not be available on one server. In this case, Matrix Server will fail
over to a network interface on a server running the highest priority service.
The default priority is 0.
clear—Clear an error condition and the associated alert for a service monitor
mx service clear <vhost:port> <netif> ...