![](https://secure.gravatar.com/avatar/f8439d15d0ba9653e1d430326958b8d2.jpg?s=120&d=mm&r=g)
Hi,
we are using 0.16.5.7901 (Stable) and have got some wrong alert of rebooting devices after 1 year, 132 days, 2h, 23m Actually they didn't reboot but uptime graphs restarted. Can be a kind of counter overflow ?
Affected devices are some brocade san switches and juniper isg1000
Regards, imedve
![](https://secure.gravatar.com/avatar/f8439d15d0ba9653e1d430326958b8d2.jpg?s=120&d=mm&r=g)
Hi,
forget it, 2^32 timeticks are about 497.1 days. SNMP counter overflow.
Regards, imedve
On h, 2016-06-20 at 09:31 +0000, Medve István wrote: Hi,
we are using 0.16.5.7901 (Stable) and have got some wrong alert of rebooting devices after 1 year, 132 days, 2h, 23m Actually they didn't reboot but uptime graphs restarted. Can be a kind of counter overflow ?
Affected devices are some brocade san switches and juniper isg1000
Regards, imedve
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
![](https://secure.gravatar.com/avatar/0896e673efe2e0118c2617b5af6c817b.jpg?s=120&d=mm&r=g)
Actually they didn't reboot but uptime graphs restarted. Can be a kind of counter overflow ?
Uptime is presented from the returned value in sysUptime.
observium~$ snmpwalk -v2c -c public device sysUptime DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (106822559) 12 days, 8:43:45.59
That would be the first place I would look. It may just be that the SNMP daemon on the device has restarted (which is what that value is actually reporting the uptime of).
Cheers,
Michael
![](https://secure.gravatar.com/avatar/0fa97865a0e1ab36152b6b2299eedb49.jpg?s=120&d=mm&r=g)
Hi,
Yeah, this is likely to be caused by an SNMP counter overflowing. It's difficult to work around... :)
Adam.
Sent from BlueMail
On 20 Jun 2016, 10:32, at 10:32, "Medve István" medve.istvan@pillerkft.hu wrote:
Hi,
we are using 0.16.5.7901 (Stable) and have got some wrong alert of rebooting devices after 1 year, 132 days, 2h, 23m Actually they didn't reboot but uptime graphs restarted. Can be a kind of counter overflow ?
Affected devices are some brocade san switches and juniper isg1000
Regards, imedve
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (3)
-
Adam Armstrong
-
Medve István
-
Michael