Oracle^® Solaris Cluster Data Service for PostgreSQL Guide

Debugging HA for PostgreSQL

HA for PostgreSQL has a file named config that enables you to activate debugging for PostgreSQL resources. This file is in the /opt/SUNWscPostgreSQL/etc directory.

How to Activate Debugging for HA for PostgreSQL

1. Determine whether you are in the global zone or in an HA for Solaris Zones configuration.

   If your PostgreSQL resource is dependent on an Oracle Solaris Zones boot component resource, you are in an HA for Solaris Zones configuration. In any other case, you are in a global zone configuration.

2. Determine whether debugging for 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 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.

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

6. Edit the /opt/SUNWscPostgreSQL/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 (c) 2006,2012, Oracle and/or its affiliates.  All rights reserved.
   #
   # Usage:
   #       DEBUG=<RESOURCE_NAME> or ALL
   #
   DEBUG=ALL
   #

   ---

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

   ---