Types of unified logging messages
The following message types can appear in unified logging files:
Application log messages
Application log messages include informational, warning, and error messages. They are always logged and cannot be disabled. These messages are localized.
An example of an application message follows:
05/02/10 11:02:01.717 [Warning] V-116-18
failed to connect to nbjm, will retry
Diagnostic log messages
Diagnostic log messages are the unified logging equivalent of the legacy debug log messages. They can be issued at various levels of detail (similar to verbose levels in legacy logging). These messages are localized.
Diagnostic messages can be disabled with the vxlogcfg command.
An example of a diagnostic message follows:
05/05/09 14:14:30.347 V-116-71
[JobScheduler::doCatIncr] no configured
session based incremental catalog schedules
Debug log messages
Debug log messages are intended primarily for Symantec engineering. Like diagnostic messages, they can be issued at various levels of detail. These messages are not localized.
Debug messages can be disabled with the vxlogcfg command.
An example of a debug message follows:
10/29/09 13:11:28.065 [taolog] TAO (12066|1) -
Transport_Cache_Manager::bind_i, 0xffbfc194 ->
See Gathering unified logs for NetBackup
See Server processes that use unified logging