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

Document Information

Preface

1.  Installing and Configuring HA for Samba

HA for Samba Overview

Overview of Installing and Configuring HA for Samba

Planning the HA for Samba Installation and Configuration

Configuration Restrictions

Restriction for the supported configurations of Samba

Restriction for the Location of Samba files

Restriction for the Samba smb.conf files

Restriction for multiple Samba instances that require winbind

Configuration Requirements

Determine which Solaris Zone Samba will run use

Dependencies Between HA for Samba Components

Required parameters for the Samba smb.conf file

Installing and Configuring Samba

How to Install and Configure Samba

How to Check Samba is installed with Solaris 9 or 10

How to Install and Configure Samba downloaded from http://www.samba.org

How to Prepare Samba for HA for Samba

Verifying the Installation and Configuration of Samba

How to Verify the Installation and Configuration of Samba

Installing the HA for Samba Packages

How to Install the HA for Samba Packages

Registering and Configuring HA for Samba

How to Register and Configure HA for Samba

How to Register and Configure HA for Samba in a failover resource group

How to Register and Configure HA for Samba in a failover resource group with winbind in a scalable resource group

How to Register and Configure HA for Samba in an HA Container

Verifying the HA for Samba Installation and Configuration

How to Verify the HA for Samba Installation and Configuration

Upgrading HA for Samba

How to Migrate Existing Resources to a New Version of HA for Samba

Understanding the HA for Samba Fault Monitor

Resource Properties

Probing Algorithm and Functionality

Operations of the winbind probe

Operations of the Samba probe

Debug HA for Samba

How to turn on debug for HA for Samba

A.  Deployment Example: Installing Samba packaged with Solaris 10

B.  Deployment Example: Installing Samba from http://www.samba.org

C.  Deployment Example: Installing Samba in an HA Container

Index

Debug HA for Samba

How to turn on debug for HA for Samba

HA for Samba can be used by multiple Samba or winbind instances. It is possible to turn debug on for all Samba or winbind instances or a particular Samba or winbind instance.

A config file exists under /opt/SUNWscsmb/xxx/etc, where xxx refers to samba or winbind.

These files allow you to turn on debug for all Samba or winbind instances or for a specific Samba or winbind instance on a particular node with Oracle Solaris Cluster. If you require debug to be turned on for HA for Samba across the whole Oracle Solaris Cluster, repeat this step on all nodes within Oracle Solaris Cluster.

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

    Change the daemon.notice to daemon.debug and restart syslogd. Note that the output below, from grep daemon /etc/syslog.conf, shows that daemon.debug has been set.

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

    Restart the syslog daemon.

    1. If running Solaris 9
      # pkill -1 syslogd
    2. If running Solaris 10
      # svcadm disable system-log
      # svcadm enable system-log
  2. Edit /opt/SUNWscsmb/xxx/config.

    Perform this step for the samba or winbind components that require debug output, on each node of Oracle Solaris Cluster as required.

    Edit /opt/SUNWscsmb/xxx/etc/config and change DEBUG= to DEBUG=ALL or DEBUG=resource.

    # cat /opt/SUNWscsmb/samba/etc/config
    #
    # Copyright 2006 Sun Microsystems, Inc.  All rights reserved.
    # Use is subject to license terms.
    #
    #ident   "@(#)config 1.1     06/03/21 SMI"
    #
    # Usage:
    #       DEBUG=<RESOURCE_NAME> or ALL
    #
    DEBUG=ALL

    Note - To turn off debug, reverse the steps above.