HP Enterprise Cluster Master Toolkit User Guide (5900-2131, December 2011)

the Tomcat does not start for some other reason the action by the Tomcat toolkit script is to halt the
package on that node and try it on another node. In order to troubleshoot why Tomcat has not
been started correctly, one has to look at the Tomcat error log files. The Tomcat log files can be
available at $CATALINA_BASE/logs directory.
Tomcat Server Maintenance
There might be situations, when the Tomcat Server has to be taken down for maintenance. For
example, when a user wants to change configuration of Tomcat but does not want to migrate to
another node. See the example that follows:
NOTE: The example assumes that the package name is tomcat_pkg1, package directory is /etc/
cmcluster/pkg/tomcat_pkg1 and the Tomcat CATALINA_BASE is configured as
/shared/tomcat_1
1. Disable the failover of the package through the cmmodpkg command cmmodpkg -d
tomcat_pkg1.
2. Pause the monitor script .
• Create an empty file, /etc/cmcluster/pkg/tomcat_pkg1/tomcat.debug as,
shown below:
touch/etc/cmcluster/pkg/tomcat_pkg1/tomcat.debug
The toolkit monitor script, which continuously monitored the Tomcat daemons, would now
stop monitoring these daemons. A message "Tomcat toolkit pausing monitoring and
entering maintenance mode" is logged in the package control script log.
3. If required stop the tomcat application as shown below:-
cd /etc/cmcluster/pkg/tomcat_pkg1/
$PWD/toolkit.sh stop
4. Perform maintenance actions (for example, changing the configuration of the Tomcat instance,
or making changes to the toolkit configuration file, hatomcat.conf. If this file is changed,
remember to distribute the new file to all cluster nodes).
5. Start the tomcat instance again if it is stopped using cd /etc/cmcluster/pkg/
tomcat_pkg1/ $PWD/toolkit.sh start.
6. Allow monitoring scripts to continue normally as shown below:
rm -f /etc/cmcluster/pkg/tomcat_pkg1/tomcat.debug
A message "Starting Tomcat toolkit monitoring again after maintenance" appears in the
Serviceguard Package Control script log.
7. Enable the package failover:
cmmodpkg -e tomcat_pkg1
NOTE: If the package fails during maintenance (for example, the node crashes), the package
will not automatically fail over to an adoptive node. It is the responsibility of the user to start the
package up on an adoptive node. See Managing ServiceGuard manual available at http://
www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard " for more details.
NOTE: This feature is enabled only when the configuration variable MAINTENANCE_FLAG is set
to "yes" in the tomcat toolkit configuration file /etc/cmcluster/pkg/tomcat_pkg1/
hatomcat.conf.
Tomcat Server Maintenance 121