HP Serviceguard Enterprise Cluster Master Toolkit User Guide (5900-2145, April 2013)
Table Of Contents
- HP Serviceguard Enterprise Cluster Master Toolkit User Guide
- Contents
- 1 Introduction
- 2 Using the Oracle Toolkit in an HP Serviceguard Cluster
- Overview
- Supported Versions
- Support for Oracle Database Without ASM
- Supporting Oracle ASM Instance and Oracle Database with ASM
- What is Automatic Storage Management (ASM)?
- Why ASM over LVM?
- Configuring LVM Volume Groups for ASM Disk Groups
- Sample command sequence for configuring LVM Volume Groups
- Serviceguard support for ASM on HP-UX 11i v3 onwards
- Framework for ASM support with Serviceguard
- Installing, Configuring, and Troubleshooting
- Setting up DB instance and ASM instance
- Setting up the Toolkit
- ASM Package Configuration Example
- Modifying a Legacy Database Package Using an Older Version of Oracle ECMT Scripts to use the Scripts Provided for ASM Support
- Adding the Package to the Cluster
- Node-specific Configuration
- Error Handling
- Network Configuration
- Database Maintenance
- Configuring and packaging Oracle single-instance database to co-exist with SGeRAC packages
- Configuring Oracle single-instance database that uses ASM in a Coexistence Environment
- Attributes newly added to ECMT Oracle toolkit
- Configuring a modular failover package for an Oracle database using ASM in a coexistence environment
- Configuring a legacy failover package for an Oracle database using ASM in a Coexistence Environment
- ECMT Oracle Toolkit Maintenance Mode
- Supporting EBS database Tier
- Oracle ASM Support for EBS DB Tier
- 3 Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX
- Overview
- Sybase Information
- Setting up the Application
- Setting up the Toolkit
- Sybase Package Configuration Example
- Creating the Serviceguard package using Modular method
- Adding the Package to the Cluster
- Node-specific Configuration
- Error-Handling
- Network configuration
- Database Maintenance
- Cluster Verification for Sybase ASE Toolkit
- 4 Using the DB2 Database Toolkit in a Serviceguard Cluster in HP-UX
- 5 Using MySQL Toolkit in a HP Serviceguard Cluster
- MySQL Package Configuration Overview
- Setting Up the Database Server Application
- Setting up MySQL with the Toolkit
- Package Configuration File and Control Script
- Creating Serviceguard Package Using Modular Method
- Applying the Configuration and Running the Package
- Database Maintenance
- Guidelines to Start Using MySQL Toolkit
- 6 Using an Apache Toolkit in a HP Serviceguard Cluster
- 7 Using Tomcat Toolkit in a HP Serviceguard Cluster
- Tomcat Package Configuration Overview
- Multiple Tomcat Instances Configuration
- Configuring the Tomcat Server with Serviceguard
- Setting up the Package
- Creating Serviceguard Package Using Modular Method
- Setting up the Toolkit
- Error Handling
- Tomcat Server Maintenance
- Configuring Apache Web Server with Tomcat in a Single Package
- 8 Using SAMBA Toolkit in a Serviceguard Cluster
- 9 Using HP Serviceguard Toolkit for EnterpriseDB PPAS in an HP Serviceguard Cluster
- 10 Support and Other resources
- 11 Acronyms and Abbreviations
- Index
you must check the Apache error log files. The Apache log files can be located by the value set
for the ErrorLog directive in the Apache instance configuration file httpd.conf. In general, the
value is <SERVER ROOT>/logs/error_log.
Maintaining the Apache Web Server
At regular intervals, the MySQL database needs maintenance like changing configuration, without
migrating the instance to migrate to standby node. Follow the procedure during database
maintenance:
NOTE: In the example the package name is http_pkg1, package directory is /etc/cmcluster/
pkg/http_pkg1, and the Apache SERVER ROOT is configured as /shared/apache1/httpd.
1. Disable the failover of the package through cmmodpkg command cmmodpkg -d http_pkg1
2. Pause the monitor script. Create an empty file, /etc/cmcluster/pkg/http_pkg1/
apache.debug
3. touch/etc/cmcluster/pkg/http_pkg1/apache.debug.
NOTE: The toolkit monitor script which continuously monitored the Apache daemons, would now
stop monitoring these daemons.
A message "Apache toolkit pausing monitoring and entering maintenance mode" is logged in the
package control script log.
• If required, stop the apache application
cd /etc/cmcluster/pkg/http_pkg1/ $PWD/toolkit.sh stop
• Perform maintenance actions (for example, changing the configuration of the Apache instance,
or making changes to the toolkit configuration file, hahttp.conf for starting up Apache
web server application in secured mode. If this file is changed, remember to distribute the
new file to all cluster nodes).
• Restart the apache instance if it is stopped, cd /etc/cmcluster/pkg/http_pkg1/
$PWD/toolkit.sh start
• Allow monitoring scripts to continue normally as shown below:
rm -f /etc/cmcluster/pkg/http_pkg1/apache.debug
A message "Starting Apache toolkit monitoring again after maintenance" appears in the
Serviceguard Package Control script log.
• Enable the package failover
cmmodpkg -e http_pkg1
NOTE:
• If the package fails during maintenance (for example, the node crashes), it does not
automatically fail over to an adoptive node. You must start the package up on an adoptive
node. For more information, see the latest Managing Serviceguard manual available at http://
www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard .
• This feature is enabled only when the configuration variable, MAINTENANCE_FLAG, is set to
"yes" in the apache toolkit configuration file: /etc/cmcluster/pkg/http_pkg1/
hahttp.conf.
• HP suggests you to have different toolkit directories for each package. If two or more packages
share the same toolkit directory and if one package enters the maintenance mode, it will affect
the other package too.
Maintaining the Apache Web Server 109