PHP Fatal error on 25.05 Update

I am making this posting in case someone can debug the problem. I have done a manual update, although the reporting has not been blocking, and everything seems to work fine, I got an error.
Standard system and installation, without customs.

I just run a ./daily.sh upgrade after 25.05 announcement ( congrats!)
I have recived a PHP fatal error

librenms@monitoritzacio:~$ ./daily.sh
Fetching new release information                   OK
Updating to latest release                         OK
PHP Fatal error:  Uncaught BadMethodCallException: Method Illuminate\Foundation\Application::configure does not exist. in /opt/librenms/vendor/laravel/framework/src/Illuminate/Macroable/Traits/Macroable.php:86
Stack trace:
#0 /opt/librenms/bootstrap/app.php(7): Illuminate\Foundation\Application::__callStatic()
#1 /opt/librenms/LibreNMS/Util/Laravel.php(43): require_once('...')
#2 /opt/librenms/includes/init.php(90): LibreNMS\Util\Laravel::bootCli()
#3 /opt/librenms/daily.php(42): require('...')
#4 {main}
  thrown in /opt/librenms/vendor/laravel/framework/src/Illuminate/Macroable/Traits/Macroable.php on line 86
PHP Fatal error:  Uncaught BadMethodCallException: Method Illuminate\Foundation\Application::configure does not exist. in /opt/librenms/vendor/laravel/framework/src/Illuminate/Macroable/Traits/Macroable.php:86
Stack trace:
#0 /opt/librenms/bootstrap/app.php(7): Illuminate\Foundation\Application::__callStatic()
#1 /opt/librenms/LibreNMS/Util/Laravel.php(43): require_once('...')
#2 /opt/librenms/includes/init.php(90): LibreNMS\Util\Laravel::bootCli()
#3 /opt/librenms/daily.php(42): require('...')
#4 {main}
  thrown in /opt/librenms/vendor/laravel/framework/src/Illuminate/Macroable/Traits/Macroable.php on line 86
Updating Composer packages                         OK
Updated from 25.3.0 to 25.5.0                      OK
Updating SQL-Schema                                OK
Updating submodules                                OK
Cleaning up DB                                     OK
Fetching notifications                             OK
Caching PeeringDB data                             OK

I have throwed again, daily.sh

librenms@xxxxxxxx:~$ ./daily.sh
Clearing caches                                    OK
Fetching new release information                   OK
Updating to latest release                         OK
Updating Composer packages                         OK
Updating SQL-Schema                                OK
Updating submodules                                OK
Cleaning up DB                                     OK
Fetching notifications                             OK
Caching PeeringDB data                             OK

Now, it seems that all is correct
validate.php

librenms@xxxxx:~$ ./validate.php
===========================================
Component | Version
--------- | -------
LibreNMS  | 25.5.0 (2025-05-16T17:51:05+02:00)
DB Schema | 2025_05_03_152418_remove_invalid_sensor_classes (338)
PHP       | 8.3.6
Python    | 3.12.3
Database  | MariaDB 10.11.11-MariaDB-0ubuntu0.24.04.2
RRDTool   | 1.7.2
SNMP      | 5.9.4.pre2
===========================================

[OK]    Composer Version: 2.8.9
[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]    Active pollers found
[OK]    Dispatcher Service not detected
[OK]    Locks are functional
[FAIL]  Some poller nodes have not checked in recently
        Inactive Nodes:
         myVM
[OK]    Redis is unavailable
[OK]    rrd_dir is writable
[OK]    rrdtool version ok
[FAIL]  Scheduler is not running
        [FIX]:
        sudo cp /opt/librenms/dist/librenms-scheduler.service /opt/librenms/dist/librenms-scheduler.timer /etc/systemd/system/
        sudo systemctl enable librenms-scheduler.timer
        sudo systemctl start librenms-scheduler.timer

I repaired the timer manually following the fix.

It seems that everything is working fine.

Big thanks to all contributors!!! :pray:

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