Woke up this morning and thought a bunch of stuff was down. However it appears that overnight a bunch of devices (not all) had their sensors in Health duplicated. This resulted in many that I had tweaked thresholds or disabled alerting on to fire alerts as they now had a duplicate entry.
Anyone else having this? This has happened before in interfaces and the fastest resolution was to delete and re-add the device. But this time its a lot of devices, around 20 that I’d have to delete.
I’m going to delete the devices with the issue. Its now created 4 sensors per sensor resulting in hundreds of entries in health per device and its not able to load the page.
Yep, we are seeing the same thing. Woke up to hundreds of email notifications that appear to be related to duplicate sensors with more being created as I write this.
Same here, no apparent commonality among devices that had duplicate sensors enabled. Occurred on a monitored Palo Alto box, a SuperMicro BMC, a Vertiv PDU, and a Fortigate.
Vesion: [25.6.0-141-gf30d292aa]
ETA, more popping up, now Synology units. Some health state sensors are duplicated twice (total of 3). It appears that the duplicates come in with default High/HWarn/LWarn/Low values so they are triggering a lot of alerts where I have non-default values for the original sensor.
Same situation. It happens on cisco, extreme, supermicro, delta ups on every discovery.
Some devices already have sensors x 3.
I have commented discovery jobs in librenms cron. Hope it will help as workaround.
I ran daily.sh hoping it will pull in reverted code. But, I think we are going to have to delete and re-add every affected device. Tried Zabbix just to kick the tires and its garbage compared to this.
Looks like running daily and rediscover DOES delete duplicate sensors. So, its fixed for now if you do that. You do not have to delete devices and re-add thankfully.
