JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Geographic Edition System Administration Guide     Oracle Solaris Cluster 4.1
search filter icon
search icon

Document Information

Preface

1.  Introduction to Administering the Geographic Edition Software

2.  Before You Begin

3.  Administering the Geographic Edition Infrastructure

4.  Administering Access and Security

5.  Administering Cluster Partnerships

6.  Administering Heartbeats

7.  Administering Protection Groups

8.  Monitoring and Validating the Geographic Edition Software

9.  Customizing Switchover and Takeover Actions

10.  Script-Based Plug-Ins

A.  Standard Geographic Edition Properties

B.  Legal Names and Values of Geographic Edition Entities

C.  Disaster Recovery Administration Example

D.  Takeover Postconditions

E.  Troubleshooting Geographic Edition Software

Troubleshooting Monitoring and Logging

Configuring the Logger File to Avoid Too Many Traces

Configuring the Log File to Avoid Detailed Messages From the gcr Agent

Configuring the Log File to Avoid jmx Remote Traces

Troubleshooting Migration Problems

Resolving Problems With Application Resource Group Failover When Communication Lost With the Storage Device

Solution or Workaround

Troubleshooting Cluster Start and Restart

Validating Protection Groups in an Error State

Solution or Workaround

Restarting the Common Agent Container

Solution or Workaround

Matching the Nodelist Property of a Protection Group to Those of Its Device Group and Resource Group

Solution or Workaround

F.  Deployment Example: Replicating Data With MySQL

G.  Error Return Codes for Script-Based Plug-Ins

Index

Troubleshooting Monitoring and Logging

This section provides the following information about setting up logging and problems that you might encounter with monitoring the Geographic Edition software:

Configuring the Logger File to Avoid Too Many Traces

Configure the logger file, /etc/cacao/instances/default/private/logger.properties, as following depending on the cmass messages you want logged:

The enabled traces are copied to the /var/cacao/instances/default/logs/cacao.0 file.

Configuring the Log File to Avoid Detailed Messages From the gcr Agent

If you want to avoid too detailed messages in your log file from the gcr agent, use entries similar to the following in your logger file /etc/cacao/instances/default/private/logger.properties:

com.sun.cluster.level=WARNING
com.sun.cluster.agent.geocontrol.gcr.level=INFO
com.sun.cluster.agent.geocontrol.level=ALL

This property file is updated each time you reinstall the SUNWscmasa package.

Configuring the Log File to Avoid jmx Remote Traces

To avoid jmx remote traces add the following lines to the beginning of your logger.properties file:

javax.management.remote.level=OFF
com.sun.jmx.remote.level=OFF
java.io.level=OFF