Understanding the fields in the daemon.raw file

If you have installed NetWorker version 7.4.X and upwards you may have noticed that the daemon log file has been modified to report as daemon.raw format rather than the daemon.log format.

You are still able to view the daemon.raw file but it is harder to decipher than the daemon.log file. This post provides a brief explanation of some of the fields in the unrendered NetWorker daemon.raw file.

To force the header to be displayed, use the -l switch with nsr_render_log.

# nsr_render_log -l daemon.raw | head
MsgID TimeStamp        Severity Category ErrorNo ThreadID     ProcessID ActivityID   HostName ProgramName RenderedMessage
42506 03/21/09 09:24:39 2           0      0      1           11700      0           smurf    nsrd        server notice: started
10100 03/21/09 09:24:44 2           0      0      1           11704      0           smurf    nsrmmdbd    media db is checking btrees

The first line in the output about will list the name of each field.

message ID, timestamp, severity, category, error no, thread id, process id, activity id, hostname, program name, message

The fields mean the following:

nsr_render_log header details
message ID code mapping to the logged message (the last field), things like waiting for job to complete etc
timestamp time error logged
severity this returns fields EQUAL OR MORE to the specified value, the higher the level the more severe the problems returned (and less info returned)(0-5 for notification, information, alert, warning, critical, emergency)
category there appears to be two valid values, 0 is regular server logging, 3 is alerts relating to permissions
error note here the -e switch excludes the error code, but the -E switch specifies the end time; it appears you cannot specify an error code in query
thread ID specific thread ID
process ID process ID
activity ID seems to always be 0
hostname this seems to always be the hostname the log file is on
program name savegrp, nsrmmdbd, nsrjobsd etc
message the message corresponding to the message ID which may have specific things relating the message such as client name, saveset name and so on.