![](https://secure.gravatar.com/avatar/c4af5e29ad2bf1ea52b555562b4b59f4.jpg?s=120&d=mm&r=g)
16 Nov
2023
16 Nov
'23
12:17 p.m.
On 11/13/23 5:14 AM, Mike Stupalov wrote:
Heh,
it's funny. Seems as this is an openbsd snmpd issue.
It's report 3 different Uptimes:
- SNMPv2-MIB::sysUpTime.0 = 1:0:58:32.85 (Timeticks converted
1:0:58:32.85 -> 89912) 2. HOST-RESOURCES-MIB::hrSystemUptime.0 = 7:10:54:04.27 (Timeticks converted 7:10:54:04.27 -> 644044) 3. SNMP-FRAMEWORK-MIB::snmpEngineTime.0 = 1699608841
We always take 3 values and choose the maximum of them.
But seems as OpenBSD report just current unixtime in snmpEngineTime. This is incorrect.
I suppose I should try reporting that to the maintainer. It's not Theo, so perhaps he'll listen :-)
I added workaround for this case in r13160.
Thanks Mike,
I switched to rolling to test it and can confirm the uptime is being reported correctly now.
--
Bryan Fields
727-409-1194 - Voice
http://bryanfields.net