Red Hat Enterprise Linux 6 snmpd may return incorrect timezone in hrSystemDate
Issue
- The time zone portion of the value stored in
hrSystemDatereturned bysnmpwalkmay have an incorect sign. It's negative when it should be positive, or positive when it should be negative. - We monitor the time via
snmpdto make sure it's within a 60 second window. On the box in question:
# hwclock -D hwclock from util-linux-ng 2.17.2 Using /dev interface to clock. Last drift adjustment done at 1297717577 seconds after 1969 Last calibration done at 1297717577 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ...got clock tick Time read from Hardware Clock: 2011/02/14 21:49:00 Hw clock time : 2011/02/14 21:49:00 = 1297720140 seconds since 1969 Mon 14 Feb 2011 04:49:00 PM EST -0.896322 secondsWhich looks like its running correctly with -5. However, on an snmp check of
hrSystemDate.0, we get the following result:hrSystemDate.0 = STRING: 2011-2-14,16:49:29.0,+5:0Compared to a Red Hat Enterprise Linux 5.3 server, which responds with:
hrSystemDate.0 = STRING: 2011-2-14,16:50:15.0,-5:0So essentially, everything is reporting that it's off by 10 hours.
Environment
- Red Hat Enterprise Linux 6
- net-snmp-5.5-27.el6.x86_64
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
