Skip to content

Poller Service

Status: BETA

The new poller service ( replaces the old poller service (, improving its reliability. It's mostly compatible with the old service, but testing is recommended before switching over.

If you are currently using the old poller service, it's strongly recommended that you migrate away - it has a serious defect under certain versions of mysql/mariadb, and may be inadvertently DoS'ing your devices. The new service does not have this issue,

Make sure you uninstall the old poller service before deploying the new one.

External Requirements

A recent version of Python

The poller service won't work under Python 2.7+; some features require behaviour only found in Python3.4+.

Python modules

  • PyMySQL is recommended as it requires no C compiler to install. MySQLclient can also be used, but does require compilation.
  • python-dotenv .env loader
  • redis-py (if using distributed polling)

These can be obtained from your OS package manager, or from PyPI with the below commands. (You ma)

pip3 install -r requirements.txt

Redis (distributed polling only)

If you want to use distributed polling, you'll need a redis instance to coordinate the nodes. It's recommeded that you do not share the redis database with any other system - by default, redis supports up to 16 databases (numbered 0-15).

It's strongly recommended that you deploy a resilient cluster of redis systems, and use redis-sentinel.


You should already have this, but the pollers do need access to the SQL database. The poller service runs much faster and more aggressively than the standard poller, so keep an eye on the number of open connections and other important health metrics.


Connection settings are required in .env. The .env file is generated after composer install and APP_KEY and NODE_ID are set.

#APP_KEY=   #Required, generated by composer install
#NODE_ID=   #Required, generated by composer install


Distributed Polling Configuration

Once you have your redis database set up, configure it in the .env file on each node.


Basic Configuration

Additional configuration settings can be set in config.php or directly into the database.

The defaults are shown here - it's recommended that you at least tune the number of workers.

$config['service_poller_workers']              = 24;     # Processes spawned for polling
$config['service_services_workers']            = 8;      # Processes spawned for service polling
$config['service_discovery_workers']           = 16;     # Processes spawned for discovery

//Optional Settings
$config['service_poller_frequency']            = 300;    # Seconds between polling attempts       
$config['service_services_frequency']          = 300;    # Seconds between service polling attempts
$config['service_discovery_frequency']         = 21600;  # Seconds between discovery runs 
$config['service_billing_frequency']           = 300;    # Seconds between billing calculations
$config['service_billing_calculate_frequency'] = 60;     # Billing interval 
$config['service_poller_down_retry']           = 60;     # Seconds between failed polling attempts
$config['service_loglevel']                    = 'INFO'; # Must be one of 'DEBUG', 'INFO', 'WARNING', 'ERROR', 'CRITICAL'
$config['service_update_frequency']            = 86400;  # Seconds between LibreNMS update checks 

There are also some SQL options, but these should be inherited from your LibreNMS web UI configuration.

Logs are sent to the system logging service (usually journald or rsyslog) - see for the options available.

You should not rely on the password for the security of your system. See

distributed_poller                             = true;  # Set to true to enable distributed polling
distributed_poller_name                        = null;  # Uniquely identifies the poller instance
distributed_poller_group                       = 0;     # Which group to poll

Cron Scripts

Once the poller service is installed, the cron scripts used by LibreNMS are no longer required and must be removed.

Service Installation

A systemd unit file is provided - the sysv and upstart init scripts could also be used with a little modification.


A systemd unit file can be found in misc/librenms.service. To install run cp /opt/librenms/misc/librenms.service /etc/systemd/system/librenms.service && systemctl enable --now librenms.service

OS-Specific Instructions


To get the poller service running under python3.4+ on RHEL-derivatives with minimal fuss, you can use the software collections build:

First, enable SCL's on your system:

CentOS 7

# yum install centos-release-scl


# subscription-manager repos --enable rhel-server-rhscl-7-rpms

Then install and configure the runtime and service:

# yum install rh-python36 epel-release
# yum install redis
# vi /opt/librenms/config.php
# vi /etc/redis.conf
# systemctl enable --now redis.service
# scl enable rh-python36 bash
# pip install pymysql redis
# cp /opt/librenms/misc/librenms.service.scl /etc/systemd/system/librenms.service
# systemctl enable --now librenms.service

If you want to use another version of python 3, change rh-python36 in the unit file and the commands above to match the name of the replacement scl.


Debian 9 (stretch)

install python3 and python-mysqldb. python-dotenv is not yes available, but the testing package is working fine, you can grab it on (the package may be updated and have a new version number).

apt install python3 python-mysqldb
cd /tmp
dpkg -i python3-dotenv_0.9.1-1_all.deb