Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Data Service for MySQL Cluster Guide Oracle Solaris Cluster 4.1

Search Scope:

- This Document
- Entire Library

## Debugging HA for MySQL Cluster

Each HA for MySQL Cluster component has a file named `config` that enables you to activate debugging for MySQL Cluster resources. This file is in the `/opt/SUNWscmys/component/etc` directory.

## How to Activate Debugging for HA for MySQL Cluster

1. Determine whether debugging for HA for MySQL Cluster is active.

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

2. Determine whether debugging is active.
   - If `daemon.debug` appears in the `/etc/syslog.conf` file of the global zone or the zone cluster's zone, debugging is active.

     You do not need to continue with this procedure.

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

     Continue with the rest of this procedure.

3. In the `/etc/syslog.conf` file in the appropriate zone, change `daemon.notice` to `daemon.debug`.
4. Restart the `syslogd` daemon in the appropriate zone.

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

5. Edit the appropriate `/opt/SUNWscmys/component-name/etc/config` file to add a value to the `DEBUG=` parameter:

   The value of the component-name can be `ndb_mgmd`, `ndbd`, or `ndbd_shutdown`.

   - To debug all resources, use `DEBUG=ALL`

   - To debug specific resources, use `DEBUG=resource-name, resource-name`

Example 1-1 Editing the Debug Configuration File

    # cat /opt/SUNWscmys/ndb_mgmd/etc/config
    #
    # Copyright 2012 Oracle and/or its affiliates. All rights reserved.
    # Use is subject to license terms.
    #
    # Usage:
    #    DEBUG=RESOURCE-NAME or ALL
    #
    DEBUG=ALL
    #

Copyright © 2000, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |