Hi, I’m not sure when it started happening but I’m finding that the high and low warning values I’m popping into the “Wireless Sensors” tab are being erased after a few hours. Can anyone assist?
librenms@librenms:~$ ./validate.php
===========================================
Component | Version
--------- | -------
LibreNMS | 25.2.0-33-g7bd7f38eb (2025-03-05T20:37:14+13:00)
DB Schema | 2025_01_30_214311_create_ipv6_nd_table (320)
PHP | 8.3.13
Python | 3.10.12
Database | MariaDB 10.6.18-MariaDB-0ubuntu0.22.04.1
RRDTool | 1.7.2
SNMP | 5.9.1
===========================================
[OK] Composer Version: 2.8.6
[OK] Dependencies up-to-date.
[OK] Database connection successful
[OK] Database connection successful
[OK] Database Schema is current
[OK] SQL Server meets minimum requirements
[OK] lower_case_table_names is enabled
[OK] MySQL engine is optimal
[OK] Database and column collations are correct
[OK] Database schema correct
[OK] MySQL and PHP time match
[OK] Active pollers found
[OK] Dispatcher Service not detected
[OK] Locks are functional
[OK] Python poller wrapper is polling
[OK] Redis is unavailable
[OK] rrdtool version ok
[OK] Connected to rrdcached
1 Like
Hi, I have the same problem here, I haven’t been able to find a solution yet but I think the problem was introduced in the last update to 25.2.0 and maybe it could be associated with #17086 but my poor understanding of the modified code doesn’t allow me to understand what it was, maybe Tony @murrant can help us, what I have been able to verify is that the values are deleted when performing a new discovery cycle.
Any way to help in how to diagnose or correct this? since it has broken part of the alarm logic that I used with this sensor limits
Hi, I’m experiencing the same issue. Every time a discovery runs, all the Wireless sensors limits are erased. Has anyone found a solution for this?
also have this issue. for NEC vr4 we have custom OIDS so they are fine. (be nice to have native support for this).
anything with a ‘wireless sensor’ has been erased. sigh. @murrant
I have the same issue on memory,storage limits. after new discovery reset to 60.
@murrant can you please confirm if this is a one time issue where we need to repopulate the wireless sensor thresholds? as you can appreciate for WISPs , we have alot of backhaul link that we monitor and having these thresholds is important. there are dozens of links to repopulate and do not want to do this without knowing they will not be erased again. many thanks
Yeah, sorry about that. The wireless sensors code is now using modern code so it shouldn’t need to be refactored any time soon.
If I were you, I would try to pull the old thresholds from a backup. You can dump the wireless_sensors table and import them into the current database.
Good luck.
