Debugging Sun Cluster HA for SAP J2EE Engine

Sun Cluster HA for SAP J2EE Engine can be used by multiple Sun Cluster instances. However, it is possible to activate debugging for all Sun Cluster instances or for a particular Sun Cluster instance.

Each Sun Cluster component has a DEBUG file in /opt/SUNWscswa/etc.

This file allows you to activate debugging for all Sun Cluster resources or for a specific Sun Cluster resource on a particular node with Sun Cluster. If you require debugging to be turned on for Sun Cluster HA for SAP J2EE Engine across the entire Sun Cluster, repeat these steps on all nodes within Sun Cluster.

How to Activate Debugging for Sun Cluster HA for SAP J2EE Engine

Edit the file /etc/syslog.conf.

In the file /etc/syslog.conf, change daemon.notice to daemon.debug.

# grep daemon /etc/syslog.conf
*.err;kern.debug;daemon.notice;mail.crit        /var/adm/messages
*.alert;kern.err;daemon.err                     operator

Change daemon.notice to daemon.debug and restart syslogd. The command grep daemon /etc/syslog.conf issues the following output, which shows that daemon.debug has now been set.

# grep daemon /etc/syslog.conf
*.err;kern.debug;daemon.debug;mail.crit        /var/adm/messages
*.alert;kern.err;daemon.err                    operator
#
# pkill -1 syslogd

Edit the file /opt/SUNWscswa/etc/config.

In the file /opt/SUNWscswa/etc/config, change DEBUG= to DEBUG=ALL or DEBUG=resource.

# cat /opt/SUNWscswa/etc/config
#
# Copyright 2003 Sun Microsystems, Inc.  All rights reserved.
# Use is subject to license terms.
#
# Usage:
#       DEBUG=<RESOURCE_NAME> or ALL
#
DEBUG=ALL
#

Note –

To deactivate debugging, perform the steps in this procedure in the reverse order.