[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #NJE-906346]: LDM Log Time Zone Issue

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #NJE-906346]: LDM Log Time Zone Issue
  • Date: Thu, 27 Dec 2012 14:41:11 -0700
Becky & Justin,

Mike Schmidt, our system administrator, has discovered that the rsyslogd(8) 
program changed how it handles timestamps from version 4 to version 5.  how it 
handles timestamps. Version 4 uses the timestamp in the messages as received; 
version 5, by default, rewrites the timestamp according to an internal template.

You can determine the version of rsyslogd(8) via the command "rsyslogd -v".

The solution to your problem (local timestamps instead of UTC timestamps) is to 
tell the rsyslogd(8) process -- via the system-logging configuration-file -- to 
use a different template for the LDM (one that doesn't rewrite the timestamp). 
This is done by adding the following line to the file "/etc/syslog.conf" (or 
whatever configuration-file is used):

    $template ldm, "%rawmsg:6:20% %hostname% %rawmsg:22:255%\n"

This line must appear *before* the LDM entry, which must have " ; ldm" appended 
to it in order to reference the above template. For example:

    local0.debug  /usr/local/ldm/logs/ldmd.log ; ldm

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: NJE-906346
Department: Support LDM
Priority: Normal
Status: Closed