3.5.1 Matrix Server Administration Guide

Chapter 8: Configure MxFS-Linux 151

This behavior is necessary because the Start and Stop scripts are run to

establish the desired start/stop activity, even though the service may

actually have been started by something other than MxFS-Linux.

The Start and Stop scripts must also handle recovery from events that

may cause them to run unsuccessfully. For example, if the system

encounters a problem, the script will fail and exit non-zero. The service

could then become active on another node, causing the Stop script to run

on the original node even though the Start script did not complete

successfully.

To configure scripts from the command line, use these options:

--recoveryScript <script>

--recoveryTimeout <seconds>

--startScript <script>

--startTimeout <seconds>

--stopScript <script>

--stopTimeout <seconds>

Event Severity

By default, MxFS-Linux treats the failure or timeout of a Start or Stop

script as a failure of the associated service and may initiate failover of the

associated Virtual NFS Services. Configuration errors can also cause this

behavior.

Such a failure or timeout creates an event associated with the monitor on

the node where the failure or timeout occurred. You can view these

events on the Management Console and clear them after you have fixed

the problems that caused them.

You can configure the failover behavior with the Event Severity attribute.

There are two settings:

CONSIDER. This is the default value. Events are considered during

failover decisions.

IGNORE. Events are ignored and Start or Stop script failures will not

cause failover. This is useful when the action performed by the Start and

Stop scripts is not critical, but is important enough that you want to keep

a record of it.