====================================
| Component | Version |
|---|---|
| LibreNMS | 1.62-27-g29748fe30 |
| DB Schema | 2020_03_25_165300_add_column_to_ports (161) |
| PHP | 7.2.24-0ubuntu0.18.04.2 |
| MySQL | 10.4.8-MariaDB-1:10.4.8+maria~xenial |
| RRDTool | 1.7.0 |
| SNMP | NET-SNMP 5.7.3 |
====================================
Hi,
I’m wondering if I’ve found a bug. We have an alert rule that triggers when a device is down. This particular one posts a form on a different site that will handle the devices in alarm state. It has worked as a charm until today when a network switch went down at 10:01:39 this morning. At 10:04:54 it was rebooted and LibreNMS received information that the device was up again. But at 10:05:03, 9 seconds after the switch clearly was up again, the alarm triggered according to the event log. The alarm log correctly shows that the device was no longer in alarm state but no recovery message was sent, making the other system believe that the device was still down, and still is.
Could it be that the alarm rule was preparing the message to be sent during those 9 seconds and sent the alarm message without knowing the device was back up? And since no “Up” event was logged after the alert, no recovery message was sent?