Error in daily.log / daily.php

In daily.log, the following error occurs again and again:

Updating SQL-Schema
INFO  Nothing to migrate.
Returned: 0
Cleaning up DB
Refreshing alert rules queries
ESC[31mPHP Error(2)ESC[0m: Undefined array key “options” in /opt/librenms/daily.php:270
ESC[31mPHP Error(2)ESC[0m: Trying to access array offset on null in /opt/librenms/daily.php:270
ESC[31mPHP Error(2)ESC[0m: Undefined array key “options” in /opt/librenms/daily.php:270
ESC[31mPHP Error(2)ESC[0m: Trying to access array offset on null in /opt/librenms/daily.php:270 (max reported errors reached)
Refreshing device group table relationships
Eventlog cleared for entries over 30 days
Deleting alert_logs more than 365 days that are not active
Deleting history of active alert_logs more than 365 days
Ports fdb cleared for entries over 10 days
Route cleared for entries over 10 days
All deleted ports now purged
Returned: 0

Does anyone know what causes this error?

Output of validate.php:

###########################

librenms@librenms-prod:~$ ./validate.php

Component Version
LibreNMS 25.12.0-dev.40+dcc07df10 (2025-12-03T01:26:34+01:00)
DB Schema 2025_11_26_170658_set_device_stats_timestamp_nullable (360)
PHP 8.4.11
Python 3.13.5
Database MariaDB 11.8.3-MariaDB-0+deb13u1 from Debian
RRDTool 1.7.2
SNMP 5.9.4.pre2
===========================================

[OK] Composer Version: 2.9.2
[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
[FAIL] We have detected that your database schema may be wrong
Database: incorrect column (cef_switching/punt)
Database: incorrect column (cef_switching/punt_prev)
[FIX]:
Run the following SQL statements to fix it
SQL Statements:
ALTER TABLE cef_switching CHANGE punt punt int NOT NULL ;
ALTER TABLE cef_switching CHANGE punt_prev punt_prev int NOT NULL ;
Attempt to fix this issue (y or n)?:n
[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] rrdtool version ok
[OK] Connected to rrdcached

###########################

Thank you in advance!

why didn’t you allow the fix?

That’s a long story. Actually, it is a bugfix for devices which report back too large numbers.

See the bug here: SQL Error: Numbers to be written into MariaDB are too large · Issue #16859 · librenms/librenms · GitHub

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