test

Sun Cluster Data Service for N1 Grid Service Provisioning System for Solaris OS

How to debug Sun Cluster HA for N1 Service Provisioning System

Sun Cluster HA for N1 Service Provisioning System can be used by multiple N1 Grid Service Provisioning System instances. However, it is possible to turn debug on for all N1 Grid Service Provisioning System instances or a particular N1 Grid Service Provisioning System instance. This has to be done for each component (Master Server, Remote Agent, or Local Distributor) on its own.

The Sun Cluster HA for N1 Service Provisioning System component has a DEBUG file under /opt/SUNWscsps/component-dir/etc. The directories of these components are master for the Master Server, remoteagent for the Remote Agent, and localdist for the Local Distributor.

This file allows you to switch debug on for all instances of a N1 Grid Service Provisioning System component, or for a specific instance of a N1 Grid Service Provisioning System component on a particular node in a Sun Cluster. If you require debug to be switched on for Sun Cluster HA for N1 Service Provisioning System across the whole Sun Cluster, you will need to repeat this step on all nodes within Sun Cluster.

ProcedureHow to turn debug on for a Sun Cluster HA for N1 Service Provisioning System component

Perform these steps for the Sun Cluster HA for N1 Service Provisioning System component that requires debug output, on each node of Sun Cluster as required.

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

    If your operating system is Solaris 10 and your N1 Grid Service Provisioning System 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 N1 Service Provisioning System 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 N1 Service Provisioning System 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, ...

    Edit /opt/SUNWscsps/component-dir/etc/config and change DEBUG= to DEBUG=ALL or DEBUG=resource 


    # cat /opt/SUNWscsps/component-dir/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, repeat step 1 to 6, changing daemon.debug to daemon.notice and changing the DEBUG variable to DEBUG=.