VCS INFO V-16-6-15004 hatrigger:Failed to send trigger for resfault; script doesn't exist ...

Article: 100023174
Last Published: 2011-01-12
Ratings: 0 0
Product(s): InfoScale & Storage Foundation

Problem

Following message displayed in /var/VRTSvcs/log/engine_A.log file:

VCS INFO V-16-6-15004 hatrigger:Failed to send trigger for resfault; script doesn't exist ...

Solution

The below engine_A.log message is NOT an error. It's an INFO message.

2009/05/26 14:12:57 VCS INFO V-16-6-15004 (oiovp001) hatrigger:Failed to send trigger for resfault; script doesn't exist

Whenever a service group is brought online/offline or if a resource faults, there are trigger scripts available to be executed.
 
WHAT ARE TRIGGERS -
Triggers let you invoke user-defined scripts for specified events in a cluster.

VCS determines if the event is enabled and invokes the hatrigger script. The script is located at $VCS_HOME/bin/hatrigger. VCS also passes the name of the event trigger and associated parameters. For example, when a service group comes online on a system, VCS invokes the following command:

hatrigger -postonline <system> <service_group>.

VCS does not wait for the trigger to complete execution. VCS calls the trigger and continues normal operation.
VCS invokes event triggers on the system where the event occurred, with the following exceptions:
  • VCS invokes the sysoffline and nofailover event triggers on the lowest numbered system in the RUNNING state.
  • VCS invokes the violation event trigger on all systems on which the service group was brought partially or fully online.

The above mentioned INFO message is displayed because of resfault trigger which was not configured. So what is a resfault trigger -

resfault event trigger
Description
Invoked on the system where a resource has faulted. Note that when a resource is faulted, resources within the upward path of the faulted resource are also brought down. This event trigger is configurable.

To configure this trigger, you must define the following:
TriggerResFault: Set the attribute to 1 to invoke the trigger when a resource faults.

Usage
- resfault triggertype system resource previous_state
  • triggertype - represents whether trigger is custom (triggertype=0) or internal (triggertype=1). For this trigger, triggertype=0.
  • system - represents the name of the system.
  • resource - represents the name of the faulted resource.
  • previous_state - represents the resource's previous state.

To enable the trigger
To invoke the trigger when a resource faults, set the TriggerResFault attribute to 1.

 
 

 

Was this content helpful?