Joe Clarke Fri, 03/09/2007 - 13:10

We are evaluating the full effect on LMS, but one easy way of mitigating this somewhat is to make sure you are not using one of EST, MST, or HST timezones on your server. For example, on Solaris, check /etc/TIMEZONE to make sure TZ is not set to one of these values.

Joe Clarke Sat, 03/10/2007 - 10:39

Besides the server timezone, syslog messages that are tagged with either one of the timezones EST, MST, or HST will be affected. However, since DST is just beginning, messages should show up with EDT, MDT, or HDT. As a workaround, you can remove the timezone files, EST, MST, and HST under NMSROOT/lib/jre/lib/zi, then restart dmgtd.

We will be releasing an official patch for LMS 2.6 when it becomes available. LMS 3.0 will not be affected when it is released.

yjdabear Sun, 03/11/2007 - 00:25

Thanks for the timely info. I'm running LMS 2.2. The server's /etc/TIMEZONE has TZ=US/Eastern configured. I don't find a $NMSROOT/lib/jre/lib/ directory or a "zi" file under $NMSROOT/lib/jre2/lib/ so I'm not able to implement the workaround. Will there be an official patch for LMS 2.2 as well?

In RME 3.5, I'm seeing Syslog Analysis displaying timestamps one hour ahead of what's received by the syslog server (Solaris built-in). Is this manifestation of this particular Sun JRE bug?

Also, in Analyze ANI Server (Campus Manager 3.3), it shows

-- listing properties -- 2 Runtime Environment, Stand...






Does this need a DST patch?

Joe Clarke Sun, 03/11/2007 - 10:06

LMS 2.2 is not affected. Only JVM 1.4.2 is affected, and only LMS 2.5+ uses this version.

yjdabear Mon, 03/12/2007 - 10:23

Any idea why in RME 3.5's Syslog Analysis the timestamps jumped directly from 1:59AM EST to 4:00AM EDT, one hour ahead of what's received by the syslog server (Solaris built-in)? Does the JRE 1.4.2_12 on the client PC (prompted download from LMS 2.2 after applying DST patch) play a role?

Joe Clarke Mon, 03/12/2007 - 10:29

Do new messages arriving now still have a one hour discrepancy? If so, try restarting the SyslogAnalyzer daemon, and see if the time resyncs.

yjdabear Mon, 03/12/2007 - 11:18

I restarted dmgtd yesterday shortly after seeing the timestamps being one-hour ahead. I suppose that might have unintentionally made Syslog Analysis sync up the time, because indeed the timestamps are in sync with what the syslog server displays.


This Discussion