You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the device is inactive, the map does not update the links leaving that device and it shows the last value when it was UP.
Follow image
Output of ./validate.php
librenms@librenms:~$ ./validate.php
===========================================
Component | Version
--------- | -------
LibreNMS | 24.2.0 (2024-02-27T15:54:10-03:00)
DB Schema | 2024_02_07_151845_custom_map_additions (290)
PHP | 8.1.16
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.1
[OK] Dependencies up-to-date.
[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] rrd_dir is writable
[OK] rrdtool version ok
librenms@librenms:~$
What was the last working version of LibreNMS?
No response
Anything in the logs that might be useful for us?
No response
The text was updated successfully, but these errors were encountered:
santiag0z
changed the title
Custom Maps Style - The links between nodes are not reset when they are down
Custom Maps: The links between nodes are not reset when they are down
Mar 10, 2024
The problem
When the device is inactive, the map does not update the links leaving that device and it shows the last value when it was UP.
Follow image
Output of ./validate.php
What was the last working version of LibreNMS?
No response
Anything in the logs that might be useful for us?
No response
The text was updated successfully, but these errors were encountered: