Search <book_title>...

InfoScale™ 9.0 Cluster Server Bundled Agents Reference Guide - Solaris

Last Published: 2025-09-09

Product(s): InfoScale & Storage Foundation (9.0)

Platform: Solaris

Attributes for Application agent

Table: Required attributes for Solaris

Required attribute	Description
StartProgram	The executable, which starts the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and have spaces separating them. This executable can be on local storage or shared storage. For example, if the attribute for StartProgram is /usr/sbin/vxnotify -g dg00 -m >> /var/log/vxnotify.log (and vxnotify is blocking command) set it like: /usr/sbin/vxnotify -g dg00 -m >> /var/log/vxnotify.log & For applications running in Solaris zones, use the path as seen from the non-global zone. Note: The agent logs the return value of the StartProgram executable. The agent does not treat a non-zero return value as failure of execution and brings the resource online. Note: Do not use the opening and closing ({ }) brace symbols in this string. Note: In the script, specify a return value that is between 0 and 255. Type and dimension: string-scalar Example: "/usr/sbin/sample_app start"
StopProgram	The executable, which stops the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and have spaces separating them. This executable can be on local storage or shared storage. For applications running in Solaris zones, use the path as seen from the non-global zone. Note: The agent logs the return value of the StopProgram executable. The agent does not treat a non-zero return value as failure of execution and takes the resource offline. Note: Do not use the opening and closing ({ }) brace symbols in this string. Note: In the script, specify a return value that is between 0 and 255. Type and dimension: string-scalar Example: "/usr/sbin/sample_app stop"
At least one of the following attributes: MonitorProcesses MonitorProgram PidFiles	See Table: Optional attributes for Solaris.

Required attribute

Description

StartProgram

The executable, which starts the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and have spaces separating them. This executable can be on local storage or shared storage.

For example, if the attribute for StartProgram is

/usr/sbin/vxnotify -g dg00 -m >> /var/log/vxnotify.log

(and vxnotify is blocking command) set it like:

/usr/sbin/vxnotify -g dg00 -m >> /var/log/vxnotify.log &

For applications running in Solaris zones, use the path as seen from the non-global zone.

Note:

The agent logs the return value of the StartProgram executable. The agent does not treat a non-zero return value as failure of execution and brings the resource online.

Note:

Do not use the opening and closing ({ }) brace symbols in this string.

Note:

In the script, specify a return value that is between 0 and 255.

Type and dimension: string-scalar

Example: "/usr/sbin/sample_app start"

StopProgram

The executable, which stops the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and have spaces separating them. This executable can be on local storage or shared storage.

For applications running in Solaris zones, use the path as seen from the non-global zone.

Note:

The agent logs the return value of the StopProgram executable. The agent does not treat a non-zero return value as failure of execution and takes the resource offline.

Note:

Do not use the opening and closing ({ }) brace symbols in this string.

Note:

In the script, specify a return value that is between 0 and 255.

Type and dimension: string-scalar

Example: "/usr/sbin/sample_app stop"

At least one of the following attributes:

MonitorProcesses
MonitorProgram
PidFiles

See Table: Optional attributes for Solaris.

Table: Optional attributes for Solaris

Optional attribute	Description
CleanProgram	The executable, which forcibly stops the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and have spaces separating them. This executable can be on local storage or shared storage. For applications running in Solaris zones, use the path as seen from the non-global zone. Note: Arctera recommends to have the CleanProgram on the local storage so that in case of loss of storage connectivity VCS can take appropriate action to stop the application. Note: If the CleanProgram executable returns a non-zero value, the agent treats it as a clean failure and the resource does not fault. Type and dimension: string-scalar Example: "/usr/sbin/sample_app force stop"
MonitorProcesses	A list of processes that you want to be monitored and cleaned. Each process name is the name of an executable. Provide the full path name of the executable if the agent uses that path to start the executable. The process name must be the full command line argument that the following command displays for the process: Solaris 11: /usr/bin/ps ww pid Type and dimension: string-vector Example: "/app/sample_bin" or "/usr/bin/bash /app/sample_process.sh"
MonitorProgram	The executable, which monitors the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and have spaces separating them. This executable can be on local storage or shared storage. For applications running in Solaris zones, use the path as seen from the non-global zone. MonitorProgram can return the following VCSAgResState values: OFFLINE value is 100 or 1; ONLINE values range from 101 to 110 or 0 (depending on the confidence level); 110 equals confidence level of 100%. Any other value = UNKNOWN. Note: Do not use the opening and closing ({ }) brace symbols in this string. If MonitorProgram is configured and not available, then resource state will be: OFFLINE if the resource was in OFFLINE state and not waiting for any action UNKNOWN if the resource was in any other state or waiting for some action. Type and dimension: string-scalar Example: "/usr/sbin/sample_app_monitor all"
PidFiles	A list of PID (process ID) files that contain the PID of the processes that you want monitored and cleaned. These are application generated files. Each PID file contains one monitored PID. Specify the complete path of each PID file in the list. For applications running in Solaris zones, use the path as seen from the non-global zone. The process ID can change when the process restarts. If the application takes time to update the PID file, the agent's monitor function may return an incorrect result. If incorrect results occur, increase the ToleranceLimit in the resource definition. Type and dimension: string-vector Example: "/var/lock/samba/smbd.pid"
User	The user name for running StartProgram, StopProgram, MonitorProgram, and CleanProgram. The processes that are specified in the MonitorProcesses list must run in the context of the specified user. Monitor checks the processes to make sure they run in this context. Note: If the configured user does not exist, the resource state will be UNKNOWN. Type and dimension: string-scalar Default: root Example: user1
EnvFile	The environment file that should get sourced before running any of the StartProgram, StopProgram, MonitorProgram or CleanProgram. Note: Please make sure that the EnvFile adheres the default shell syntax of the configured use. Type and dimension: string-scalar Default: "" Example: /home/username/envfile
UseSUDash	When the value of this attribute is 0, the agent performs an su user command before it executes the StartProgram, the StopProgram, the MonitorProgram, or the CleanProgram agent functions. When the value of this attribute is 1, the agent performs an su - user command before it executes the StartProgram, the StopProgram, the MonitorProgram or the CleanProgram agent functions. Type and dimension: boolean-scalar Default: 0 Example: 1
DelayAfterOnline	Specifies the number of seconds that elapse after the Online entry point is complete and before the next monitor cycle is invoked. Type and dimension: integer-scalar Default: 0
DelayAfterOffline	Specifies the number of seconds that elapse after the Offline entry point is complete and before the next monitor cycle is invoked. Type and dimension: integer-scalar Default: 0