Since last daily update on midnight (local time) the poller stopped working.
Anyone else seeing this behavior?
Regards,
Time of incident: 2021-08-09 20:15 PST OS: Raspbian GNU/Linux 10 (buster) Issue: Poller is not successfully polling any devices
Cronic detected failure or error output for the command:
/opt/librenms/poller-wrapper.py 4
RESULT CODE: 1
ERROR OUTPUT:
ERROR: Could not execute command [['/usr/bin/env', 'php', '/opt/librenms/config_to_json.php']]: Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
File "/opt/librenms/poller-wrapper.py", line 37, in <module>
log_dir = config["log_dir"]
TypeError: 'NoneType' object is not subscriptable
VALIDATE OUTPUT:
librenms@server-3-1:~$ ./validate.php
====================================
Component | Version
--------- | -------
LibreNMS | 21.7.0-61-g93209a0fc
DB Schema | 2021_08_04_102914_add_syslog_indexes (213)
PHP | 7.4.22
Python | 3.7.3
MySQL | 10.3.29-MariaDB-0+deb10u1
RRDTool | 1.7.1
SNMP | NET-SNMP 5.7.3
====================================
[OK] Composer Version: 2.1.5
[OK] Dependencies up-to-date.
[OK] Database connection successful
[OK] Database schema correct
[WARN] IPv6 is disabled on your server, you will not be able to add IPv6 devices.
[WARN] Your local git contains modified files, this could prevent automatic updates.
[FIX]:
You can fix this with ./scripts/github-remove
Modified Files:
includes/definitions/ciscosb.yaml
includes/definitions/dahua-nvr.yaml
rrd/.gitignore
Cronic detected failure or error output for the command:
/opt/librenms/poller-wrapper.py 6
RESULT CODE: 1
ERROR OUTPUT:
ERROR: Could not execute command [['/usr/bin/env', 'php', '/opt/librenms/config_to_json.php']]: Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
File "/opt/librenms/poller-wrapper.py", line 37, in <module>
log_dir = config["log_dir"]
TypeError: 'NoneType' object is not subscriptable
STANDARD OUTPUT:
I was seeing the same problem this morning - but manually ran the daily update script again and it looks like there’s a new patch already if the version numbering is anything to go by. No longer getting any errors about being unable to import the .env.