Logging

To make it easier to determine the events leading up to an error condition, the debug and error logs have been combined into one file - generally called error.log. This file is located in the component's logs directory (for example: the agent log is located in /opt/SUNWuce/agent/logs/error.log).

In addition, the format of the log file itself has been standardized. Entries in the log file have the following format:

pid:YYYY-MM-dd_hh:mm:ss level [ module-or-logger-name: source-file: #line-no ] error-code message

YYYY-MM-dd_hh:mm:ss

Rrepresent the date and time at which the message was sent to the logger for reporting.

Level

The symbolic logging level, in decreasing level of severity. The levels are SEVERE, ERROR, WARNING, INFO, DEBUG, FINE, and DETAILED.

Error-code

The numeric code of the error message that is being reported. When debug information is being reported, the error-code might be zero.

Source-file

The name of the file from which the logger was called. When legacy code in the application calls the logging mechanism, the source-file name might be the string source_unavailable.

Line-no

The line number in the source file at which the logger was called to report the message. If the source-file name is not available, this might be zero.

You might see messages with the level set to ERROR, but which actually contain debugging information or messages which are not errors, such as:

10918:2007-01-16_09:49:18 ERROR [ default_logger: source_unavailable: #0 ] 118100736 Info: Enabling Authentication mechanism (User=<>, Pass<**>)

This is usually the result of legacy code in the applications. In the example above, other indications that the legacy code called the logging mechanism are the source-file name and line number. Instead of recording the name of the source file in which the logger was called, you see source_unavailable, and the line number is zero.