JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Data Service for MySQL Guide     Oracle Solaris Cluster 4.1
search filter icon
search icon

Document Information

Preface

1.  Installing and Configuring HA for MySQL

Installing and Configuring HA for MySQL

HA for MySQL Overview

Planning the HA for MySQL Installation and Configuration

MySQL and Solaris Containers

Configuration Restrictions

Restriction for the HA for MySQL Data Service Configuration

Restrictions on the MySQL Configuration File

Restrictions for the MySQL Configurations

Restrictions on the MySQL Database Directory

Restriction for the MySQL smf Service Name in an HA Zone

Examples for the File Systems Layout

Configuration Requirements

Components and Their Dependencies for HA for MySQL

Registration and Configuration File for HA for MySQL

Explanation of the my.cnf File

Installing and Configuring MySQL

Enabling MySQL to Run in a Global Zone Configuration

How to Enable MySQL for a Failover Resource

How to Enable MySQL to Run in a Scalable Configuration

How to Enable MySQL to Run in a Multiple-Master Configuration

How to Install and Configure MySQL in a Global Zone

Enabling MySQL to Run in a Zone Configuration

How to Enable MySQL for a Failover Resource

How to Enable MySQL to Run in a Scalable Configuration

How to Enable MySQL to Run in a Multiple-Master Configuration

How to Install and Configure MySQL in a Zone

How to Enable MySQL to run in an HA Zone Configuration

How to Install and Configure MySQL in an HA Zone

Verifying the Installation and Configuration of MySQL

How to Verify the Installation and Configuration of MySQL

Installing the HA for MySQL Package

How to Install the HA for MySQL Package

Registering and Configuring HA for MySQL

How to Register and Configure HA for MySQL as a Failover Service in a Global Zone Configuration

How to Register and Configure HA for MySQL as a Failover Service in a Zone Configuration

How to Register and Configure HA for MySQL as a Failover Service in an HA Zone Configuration

How to Modify Parameters in the HA for MySQL Manifest

How to Remove an HA for MySQL Resource From an HA Zone

How to Add an HA for MySQL Resource in a Scalable or Multiple-Master Configuration

Verifying the HA for MySQL Installation and Configuration

How to Verify the HA for MySQL Installation and Configuration

Understanding the HA for MySQL Fault Monitor

Resource Properties

Probing Algorithm and Functionality

Debugging the HA for MySQL

How to Activate Debugging for HA for MySQL

A.  Deployment Example: Installing MySQL in the Global Zone

B.  Deployment Example: Installing MySQL in the Non-Global HA Zone

C.  Deployment Example: Installing MySQL in a Scalable or Multiple-Master Configuration

Index

Debugging the HA for MySQL

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

How to Activate Debugging for HA for MySQL

  1. Determine whether you are in a global zone or in an HA Zone configuration.
  2. 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 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 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
    #
  5. Restart the syslogd daemon in the appropriate zone.
    # svcadm restart system-log
  6. Edit the appropriate /opt/SUNWscmys/etc/config file to change the DEBUG= parameter.

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

    • To debug all resources, use DEBUG=ALL.

    • To debug specific resources, use DEBUG=resource name,resource name[, …].


    Note - To deactivate debugging, repeat this procedure after you change daemon.debug to daemon.notice and the DEBUG variable to DEBUG=.


Example 1-5 Editing the Debug Config File

# cat /opt/SUNWscmys/etc/config
#
# Copyright 2012 OracleCorporation.  All rights reserved.
# Use is subject to license terms.
#
# Usage:
#       DEBUG=<RESOURCE_NAME> or ALL
#
DEBUG=ALL
#