Hi,
My LibreNMS was also affected by that bug and the new release solved the problem however that new version bring another problem on my LibreNMS VM :
2024-09-10 14:01:24,082 :: CRITICAL :: DB Connection exception (1062, “Duplicate entry ‘librenms’ for key ‘pollers_poller_name_unique’”)
I checked on within the LibreNMS DB and I don’t see something suspicious
The output of./validate looks correct :
librenms@librenms:~$ ./validate.php
Component | Version |
---|---|
LibreNMS | 24.8.0-62-g77fa7573c (2024-09-10T07:59:20+00:00) |
DB Schema | 2024_08_27_182000_ports_statistics_table_rev_length (299) |
PHP | 8.1.23 |
Python | 3.8.10 |
Database | MariaDB 10.3.39-MariaDB-0ubuntu0.20.04.2 |
RRDTool | 1.7.2 |
SNMP | 5.8 |
=========================================== |
[OK] Composer Version: 2.7.9
[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 has been used, but not recently
[OK] Locks are functional
[OK] Python poller wrapper is polling
[OK] Redis is unavailable
[OK] rrd_dir is writable
[OK] rrdtool version ok
And from the DB :
MariaDB [librenms]> explain pollers;
±------------±-----------------±-----±----±--------±---------------+
| Field | Type | Null | Key | Default | Extra |
±------------±-----------------±-----±----±--------±---------------+
| id | int(10) unsigned | NO | PRI | NULL | auto_increment |
| poller_name | varchar(255) | NO | UNI | NULL | |
| last_polled | datetime | NO | | NULL | |
| devices | int(10) unsigned | NO | | NULL | |
| time_taken | double | NO | | NULL | |
±------------±-----------------±-----±----±--------±---------------+
5 rows in set (0.001 sec)
MariaDB [librenms]> select * from pollers;
±—±------------±--------------------±--------±-----------+
| id | poller_name | last_polled | devices | time_taken |
±—±------------±--------------------±--------±-----------+
| 1 | librenms | 2024-09-10 14:01:24 | 65 | 81 |
±—±------------±--------------------±--------±-----------+
1 row in set (0.000 sec)
I looked at the past logs but this error started to popup with this new release, if someone have an idea…
Thanks,