User`s guide

Logging Events
007-4403-003 61
The following is an example of a message that has a severity code of 2 (Debug2 severity
level). The message was written on day 14 of the month at the time that is shown in the
message, and the ID of the process that wrote the message is 8254:
2 14-22:23:50.316766 8254 mvcp/ninety9 <-- 100 VTR Ready
The following example shows a Notice-level message:
N 29-09:26:11.490919 3064 U1 Unit ERROR (err=22): Clip timecode type
not known
The following example shows an Info-level message:
I 29-09:26:12.758644 3065 (littlered_1) Timecode input acquired
tc=09:27:35.02 (offset=* -27000000)
The following example shows a Warning-level message:
W 08-12:12:25.910495 1364 No media devices detected by "dq" module
Configuring Logging
Logging is configured by setting the value of the following control in the system defaults
file /usr/vtr/config/system-defaults/main:
vtr.main.log_level.file
For example, to enable increased logging by including the first level of debug events in
the events that are logged to the server log, /usr/vtr/adm/logs/vtrlog, include the
following control setting in the main system defaults file:
vtr.main.log_level.file 1
The value of the control is relative to the Info log event severity. As shown in Table 4-1,
positive values enable more verbose logging (1 = Debug1, 2 = Debug2, ...); negative
values disable all but the more severe events (–2 = Warning, –3 = Error, and so on).
Caution: Level 2 and above create very large files that can adversely affect system
performance and should only be used for troubleshooting. Using the MVCP SET
command to set the log verbosity allows you to effect the change without a VST restart.
!