Open for Voting

False reboot alerts due to SNMP service restart & Proper uptime information

Reboot information is related to SNMP service/daemon. It should not be work like this. SNMP service/daemon can be crashed or restarted for some reason (most of the time). And for that it's not a reliable service for tracking reboots. We need other solution (maybe different OID) for this out of the box. There are plenty of threads about this issue. Some of them are below.

linux snmpd restart during logrotate triggers false reboot alert weekly

Better Method of Calculating Uptime

Re: Misleading SNMP Uptime information
Re: events with "...nodename REBOOTED AT...date time"
Uptime SNMP and reboot messages

is this normal? restart SNMP SERVICE and get a REBOOT event

False Uptime/Reboot readings

Parents
  • You can modify or disable the Alert called "Alert me when a node Lastboot changes" AND Disable EventType 14 (Node Rebooted) events by running the following SQL Query:

     

    UPDATE EventTypes SET Record=0 WHERE EventType = 14

    I tested this and the above query does indeed stop the pesky alerts which are confusing my end users because it says the node rebooted but the node did not reboot, it was just that the SNMP Agent was cycled.

Comment
  • You can modify or disable the Alert called "Alert me when a node Lastboot changes" AND Disable EventType 14 (Node Rebooted) events by running the following SQL Query:

     

    UPDATE EventTypes SET Record=0 WHERE EventType = 14

    I tested this and the above query does indeed stop the pesky alerts which are confusing my end users because it says the node rebooted but the node did not reboot, it was just that the SNMP Agent was cycled.

Children