Using the Console Debug Trace Log

By default, the console does not log debug messages. You can turn on debug logging to help troubleshoot console service problems.

Use the debug.trace.level property to turn on debug logging by setting the property to a value other than 0.

Available choices include the following:

• 1 - Use this setting to record potentially severe errors.

• 2 - Use this setting to record important messages, as well as error messages of the 1 level.

• 3 - Use this setting to record all possible messages with full details.

By default, the debug trace log is created in the /var/log/webconsole directory for the Oracle Solaris 10, Solaris 10 1/06, and the Solaris 10 6/06 releases. Starting with the Solaris 10 11/06 release, the log is created in the /var/log/webconsole/console directory. The log file is named console_debug_log. Historical logs, such as console_debug_log.1 and console_debug_log.2 might also exist in this directory. There can be up to five (default setting) historical logs stored in this directory before the earliest log is deleted and a new log is created.

Example 3–6 Setting the Console Debug Trace Log Level

Use the following command to set the debug trace log level to 3.

For the Solaris 10 11/06 release, use this command:

# wcadmin add -p -a console debug.trace.level=3

For the Oracle Solaris 10, Solaris 10 1/06, and the Solaris 10 6/06 releases, use this command:

# smreg add -p -c debug.trace.level=3

Example 3–7 Checking the Status of the debug.trace.level Property

To check the status of the debug.trace.level property, use the wcadmin list or smreg list command.

Solaris 10 11/06:

# wcadmin list -p | grep "debug.trace.level"

For the Oracle Solaris 10, Solaris 10 1/06, and Solaris 10 6/06 releases, use this command:

# smreg list -p | grep "debug.trace.level"