Troubleshooting the Geographic Edition Framework

Language:

This appendix describes procedures for troubleshooting your application of the Geographic Edition framework.

This appendix contains the following sections:

Troubleshooting Monitoring and Logging

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

For information about logging, see Viewing the Geographic Edition Log Messages.

Configuring the Logger File to Avoid Too Many Traces

Configure the logger file, /etc/cacao/instances/default/private/logger.properties, as follows 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 Logger 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 /etc/cacao/instances/default/private/logger.properties logger file:

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 Logger 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

Oracle® Solaris Cluster 4.3 Geographic Edition System Administration Guide