Librenms showing devices as unpolled after redis install

Hi team, I had a Librenms instance with a single poller (polling over 250 devices - 68 pollers 32 workers) running normally. We decided to prepare the environment to distributed pollers. After installing redis i started to see devices as unpolled (even if they are collecting normally). I would like to know if this is a bug or i made a mistake in the configuration

My validate output

===========================================

Component Version
LibreNMS 23.11.0 (2023-11-17T02:57:41+00:00)
DB Schema 2023_11_04_125846_packages_increase_name_column_length (273)
PHP 8.1.2-1ubuntu2.14
Python 3.10.12
Database MariaDB 10.6.12-MariaDB-0ubuntu0.22.04.1
RRDTool 1.7.2
SNMP 5.9.1
===========================================

[OK] Composer Version: 2.6.5
[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 is enabled
[OK] Locks are functional
[OK] No active python wrapper pollers found
[OK] Redis is functional
[OK] rrd_dir is writable
[OK] rrdtool version ok

In the .env file i added
REDIS_HOST= myiphere
REDIS_PORT=6379
CACHE_DRIVER=redis
REDIS_DB=0

Perhaps the pollers are attempting to use redis for something already.

If you remove the lines from your .env and restart the poller service does the issue go away?

I did remove the configuration from .env and restore the redis config file to default. I did see it connects to the Redis but it did not solve my issue. Could this be a bug? Because even if the device is showing as unpolled, i can see the correct information without gaps on the rdd files or weathermap

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.