Issues with polling

We are currently setup with distributed polling with a master LiberNMS and then a probe at each campus using rrdcached.

It has been working flawless until around this time (Oct 31’ish).

I didn’t realize we are on the dev (daily) fork and around the same time ALL of our devices showed down across 7 colleges.

Now all of our devices randomly show down/up through out the day.

Is there a way to force a cut over to stable?

~$ ./validate.php

Component Version
LibreNMS 25.11.0-dev.79+49844d8a2 (2025-11-03T15:07:32-05:00)
DB Schema 2025_10_17_112553_bgp_peers_cbgp_bigint (358)
PHP 8.2.26
Python 3.11.2
Database MariaDB 10.11.14-MariaDB-0+deb12u2
RRDTool 1.7.2
SNMP 5.9.3
===========================================

[OK] Composer Version: 2.8.12
[OK] Dependencies up-to-date.

[OK] Database Connected
[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] Distributed Polling setting is enabled globally
[OK] Connected to rrdcached
[FAIL] Both Dispatcher Service and Python Wrapper were active recently, this could cause double polling
[OK] Dispatcher Service is enabled
[OK] Locks are functional
[FAIL] Some poller nodes have not checked in recently
Inactive Nodes:
XX-XX-XX
[OK] Redis is functional
[OK] rrdtool version ok
[OK] Connected to rrdcached

In 30mins our dashboard showed all up and then 80% down.

1 Like

There are no bugs affecting polling in any recent versions of LibreNMS (monthly or daily releases).

You likely have a configuration issue. I see a couple of failures in validation output, you should fix those before troubleshooting further.

As for your question, you can set your release target to monthly (covered by the docs) this will freeze your code until the next monthly is released.