Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The fix as stated in Bug 683680 did not fix this issue, sadly:
[nagios@bigbrother ~]$ snmpwalk -c public -v 1 leeuwarden 1.3.6.1.2.1.25.1.2
HOST-RESOURCES-MIB::hrSystemDate.0 = STRING: 2011-12-14,11:43:22.0,+1:0
[nagios@bigbrother ~]$ snmpwalk -c public -v 2c lipwig 1.3.6.1.2.1.25.1.2
HOST-RESOURCES-MIB::hrSystemDate.0 = STRING: 2011-12-14,11:43:27.0,-1:0
'Leeuwarden' is still a rhel 5.7 box.
I am not sure I understand. Which one of the two snmpwalk above is wrong?
leeuwarden or lipwig? What OS is on lipwig? What net-snmp version and release
is running on both of them?
BTW, the bug #683680 you are referring to was fixed in snmpd daemon, not
snmpwalk.
excuse me, you are right.
the snmpd-daemon reports the timezone wrong in rhel 6.2. There was a report, which is closed now.
lipwig is rhel 6. snmpwalk only shows the difference between what it is (lipwig) and what is should be (leeuwarden).
Yes, there is a bug. snmpd reports the tomezone wrong. It reports -1 instead of +1. /etc/localtime is correct symlink to Europe/Amsterdam on both machines, date reports correct timezone.
[arjenh@lipwig ~]$ rpm -qa |grep snmp
net-snmp-libs-5.5-31.el6.x86_64
net-snmp-5.5-31.el6.x86_64
[arjenh@lipwig ~]$ date
Wed Dec 14 14:00:55 CET 2011
[arjenh@leeuwarden ~]$ rpm -qa |grep snmp
net-snmp-libs-5.3.2.2-14.el5_7.1
net-snmp-5.3.2.2-14.el5_7.1
[arjenh@leeuwarden ~]$ date
Wed Dec 14 14:00:52 CET 2011
(In reply to comment #5)
> Yes, there is a bug. snmpd reports the tomezone wrong. It reports -1 instead of
> +1. /etc/localtime is correct symlink to Europe/Amsterdam on both machines,
> date reports correct timezone.
>
> [arjenh@lipwig ~]$ rpm -qa |grep snmp
> net-snmp-libs-5.5-31.el6.x86_64
> net-snmp-5.5-31.el6.x86_64
Please update to net-snmp-5.5-37, released in RHEL 6.2. This bug should be fixed there.