Hi Mike,
please update to r3621 and check that UpTime is now displayed correctly. :)
On Wed, Feb 20, 2013 at 3:19 PM, Mike Richardson mike.richardson@manchester.ac.uk wrote:
Hiya,
We've noticed that Observium is reporting that devices have rebooted even though they haven't. It's happening at the 496 day mark and so we're assuming that this is related to the 32bit SysUptime counter limitation.
I noticed though that there is a section of code which says:
// Use snmpEngineTime (68 year rollover) to cross-reference for false // positives in device rebooting due to sysUpTime rollover issues
so I presume this ought not be happening. I can appreciate that this is a difficult one to test. Or rather, it's easy to test but has a *really* long debug cycle :-)
We're currently running 0.13.2.3559.
Here's the output from a device which observium recently reported as having rebooted:
SNMP-FRAMEWORK-MIB::snmpEngineTime.0 = INTEGER: 43016530 DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (6689166) 18:34:51.66
If you want any more information just ask. Given the number of devices we have with uptimes around 496 days we can probably do a test every few days.
Thanks,
Mike
-- Mike Richardson Networks (network@manchester.ac.uk) IT Services, University of Manchester *Plain text only please - attachments stripped on arrival* _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium