Red Hat Bugzilla – Bug 449919
General: Uptime SNMP
Last modified: 2009-09-10 14:48:35 EDT
Description of problem:
The General: Uptime SNMP probe is supposed to report the uptime of the queried
machine. However it just reports the uptime of snmpd stack, so gives misleading
reports if the snmp stack is cycled on the target.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Configure a General: Uptime SNMP probe
Returns the uptime of the SNMP stack on the target
Returns the uptime of the target host
The problem is that the probe queries DISMAN-EVENT-MIB::sysUpTimeInstance /
It should instead query HOST-RESOURCES-MIB::hrSystemUptime.0 / 172.18.204.11
Notes to myself:
we will need to edit
and HOST-RESOURCES-MIB::hrSystemUptime.0 returns string ("212 hours 35 minutes 19 seconds" ) whereas sysUpTimeInstance returns timeticks - is is compatimble or wee need to do converse? Investigate...
Probe changed to query hrSystemUptime according to Description.
Conversion not needed, because both queries return values in Timeticks.
Available in composes since Satellite-5.3.0-RHELx-re20090501.1
[root@rlx-2-20 .ssh]# uptime
16:11:49 up 8 days, 2:32, 1 user, load average: 0.00, 0.00, 0.00
Probe: General: Uptime SNMP
Monitoring Scout RHN Monitoring Satellite
Status: OK, Uptime 8 days, 02:30:55.37
Last update: 5/19/09 12:09:30 PM EDT
Stage validated with Satellite-5.3.0-RHEL5-re20090820.1:
[root@vmware139 ~]# uptime
10:43:01 up 17 days, 17:43, 2 users, load average: 0.08, 0.36, 0.43
General: Uptime SNMP Uptime 17 days, 17:42:35.02
even if I've just hour ago installed snmpd.
Moving to RELEASE_PENDING.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.