Go to main content

Oracle® Solaris Cluster Data Service for MySQL Guide

Exit Print View

Updated: October 2019
 
 

How to Activate Debugging for HA for MySQL

  1. Determine whether debugging for HA for MySQL 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.

  2. If debugging is inactive, edit the /etc/syslog.conf file to change daemon.notice to daemon.debug.
  3. Confirm that debugging for HA for MySQL 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
    #
  4. Restart the syslogd daemon.
    # svcadm restart svc:/system/system-log:default
  5. Set the Debug_level property for the MySQL resource.
    # clresource set -p Debug_level=N MySQL-resource

    The following are the valid values for the Debug_level property:

    0

    No debug information

    1

    Issue start and stop messages for the executed functions

    2

    Include a Korn shell trace on the console for start and stop messages of the functions

Example 4  Setting Debugging

The following example enables debugging for the MySQL-resource resource using debug level 2.

# clresource set -p Debug_level=2 MySQL-resource