How to Activate Debugging for Sun Cluster HA for PostgreSQL

1. Determine whether you are in a global zone or in a failover zone configuration.

   If your operating system is Solaris 10 and your PostgreSQL resource is dependent on a Solaris Container boot component resource, you are in a failover zone configuration. In any other case, especially on a Solaris 9 system , you are in a global zone configuration.

2. Determine whether debugging for Sun Cluster HA for PostgreSQL is active.

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

   If debugging is inactive, daemon.notice is set in the file /etc/syslog.conf of the appropriate zone.

3. If debugging is inactive, edit the /etc/syslog.conf file in the appropriate zone to change daemon.notice to daemon.debug.

4. Confirm that debugging for Sun Cluster HA for PostgreSQL is active.

   If debugging is active, daemon.debug is set in the file /etc/syslog.conf.

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

5. Restart the syslogd daemon in the appropriate zone.

   • If your operating system is Solaris 9, type:

     # pkill -1 syslogd

   • If your operating system is Solaris 10, type:

     # svcadm refresh svc:/system/system-log:default

6. Edit the /opt/SUNWsczone/sczbt/etc/config file to change the DEBUG= variable according to one of the examples:

   • DEBUG=ALL

   • DEBUG=resource name

   • DEBUG=resource name,resource name, ...

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

   ---

   Note –

   To deactivate debugging, repeat step 1 to 6, changing daemon.debug to daemon.notice and changing the DEBUG variable to DEBUG=.

   ---