Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Enterprise Edition
-
None
Description
Hello,
We updated our Observium instances last week to revision 13020 and after a couple of days found out that the Alert checkers for "Device rebooted" didn't work.
What we have found so far is that the state in the table "Alert_id" is "{"metrics":{"device_rebooted":null}}" while the expected value is either "{"metrics":{"device_rebooted":0}}" or "{"metrics":{"device_rebooted":1}}"
When manually discovering a random device, this is what the discover.php returns:
[root@mum-obs-2.vm: /opt/observium]# ./poller.php -d -h mmrda-rsb-h-s5735-acc | grep rebooted
[last_rebooted] => 1695423984
[last_rebooted] => 1695423984
[rebooted] => 0
But as a record in the Alert_id table we have: :{\"device_rebooted\":null}}.
Downgrading to revision 12912 which was our previous version fixed the issue.
Attachments
Activity
General questions and device support can be discussed in our Discord channel, click here to join.
Please make and attach additional information about the device:
- full snmp dump from device:
snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalksnmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalkIf device not support SNMP version 2c, replace -v2c with -v1.
- If you have problems with discovery or poller processes, please do and attach these debugs:
./discovery.php -d -h <device>./poller.php -d -h <device>
- additionally attach device and/or vendor specific MIB files
This comment is added automatically.
Tnx, fixed in r13040.
(wait for next stable).