Managing HP Serviceguard A.12.00.00 for Linux, June 2014

3.4.3 During Run Script Execution
Once the package manager has determined that the package can start on a particular node, it
launches the script that starts the package (that is, a package’s control script or master control
script is executed with the start parameter). This script carries out the following steps:
1. Executes any external_pre_scripts. For more information, see “About External Scripts”
(page 135)).
2. Activates volume groups or disk groups.
3. Mounts file systems.
4. Assigns package IP addresses to the LAN card on the node (failover packages only).
5. Executes any external_script. For more information, see “About External Scripts”
(page 135)).
6. Starts each package service.
7. Exits with an exit code of zero (0).
Figure 20 Modular Package Time Line
At any step along the way, an error will result in the script exiting abnormally (with an exit code
of 1). For example, if a package service is unable to be started, the control script will exit with an
error.
If the run script execution is not complete before the time specified in the run_script_timeout
parameter (page 187), the package manager will kill the script. During run script execution, messages
are written to a log file. For modular packages, the pathname is determined by the
script_log_file parameter in the package configuration file (page 188)). Normal starts are
recorded in the log, together with error messages or warnings related to starting the package.
3.4 How Packages Run 55