Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Geographic Edition System Administration Guide

Search Scope:

- This Document
- Entire Library

## Troubleshooting Monitoring and Logging

This section provides 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:

- To select only `WARNING` and `SEVERE` messages, the first line of the file should read as follows:

      com.sun.cluster.level=WARNING

- To enable all `geocontrol` messages, the second line of the file should read as follows:

      com.sun.cluster.agent.geocontrol.level=ALL

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

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