"FAIL: Scheduler is not running" after moving to dedicated database server

Help
1

After moving to dedicated database server with memcached enabled, i am getting the “Scheduler is not running” error. Everything else seems to be working, polling etc. Even if I check the scheduler service status on my server, I can see it running and doing it’s schedules. The suggested fix has no effect.

Validate.php:

Component Version
LibreNMS 25.1.0-119-g91840af2b (2025-02-17T18:35:47+02:00)
DB Schema 2025_01_30_000121_add_ifindex_index_to_ports_table (315)
PHP 8.3.13
Python 3.9.21
Database MySQL 8.0.36
RRDTool 1.7.2
SNMP 5.9.1
===========================================

[OK] Composer Version: 2.8.4
[OK] Dependencies up-to-date.
[OK] Database connection successful
[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] Distributed Polling setting is enabled globally
[OK] Connection to memcached is ok
[OK] Connected to rrdcached
[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
[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

daily.sh:

Updating to latest codebase OK
Updating Composer packages OK
Updating SQL-Schema OK
Updating submodules OK
Cleaning up DB OK
Fetching notifications OK
Caching PeeringDB data OK

2

Some update, everything indeed seems to be working except that fail in validate.php in UI or CLI.

systemctl status librenms-scheduler.timer

? librenms-scheduler.timer - LibreNMS Scheduler
Loaded: loaded (/etc/systemd/system/librenms-scheduler.timer; enabled; preset: disabled)
Active: active (waiting) since Fri 2025-02-21 11:55:36 EET; 3h 41min ago
Until: Fri 2025-02-21 11:55:36 EET; 3h 41min ago
Trigger: Fri 2025-02-21 15:38:00 EET; 47s left
Triggers: ? librenms-scheduler.service Started LibreNMS Scheduler.

systemctl status librenms-scheduler.service

? librenms-scheduler.service - LibreNMS Scheduler
Loaded: loaded (/etc/systemd/system/librenms-scheduler.service; static)
Active: inactive (dead) since Fri 2025-02-21 15:38:00 EET; 34s ago
TriggeredBy: ? librenms-scheduler.timer
Process: 275372 ExecStart=/usr/bin/env php artisan schedule:run --no-ansi --no-interaction (code=exited, status=0/SUCCESS)
Main PID: 275372 (code=exited, status=0/SUCCESS)
CPU: 500ms Starting LibreNMS Scheduler…
librenms-scheduler.service: Deactivated successfully.
Finished LibreNMS Scheduler.

3

I installed a poller and the issue followed there. A fresh install without errors including this part:

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

There are no errors in any logs and everything is running well and smoothly.

In another topic someone mentioned getting this error after running

./scripts/github-remove -d

5

I am still wondering is this something i should be worried about? Everything is running well and smooth, no problems anywhere what so ever and the latest major update went fine.

Component Version
LibreNMS 25.3.0-42-gf4e45f488 (2025-03-25T03:20:22+02:00)
DB Schema 2025_03_22_134124_fix_ipv6_addresses_id_type (323)
PHP 8.3.13
Python 3.9.21
Database MySQL 8.0.41
RRDTool 1.7.2
SNMP 5.9.1
===========================================

[OK] Composer Version: 2.8.6
[OK] Dependencies up-to-date.
[OK] Database connection successful
[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] Distributed Polling setting is enabled globally
[OK] Connection to memcached is ok
[OK] Connected to rrdcached
[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
[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

6

Yes, you need to enable the librenms-scheduler.timer. It does not do much at this time, but it will do more over time. (one thing it does is update the mac oui database)

7

Thanks for the info. The problem is that when i execute the suggested fix, nothing seems to happen. Even according to logs the timer runs at set times.

? librenms-scheduler.timer - LibreNMS Scheduler
Loaded: loaded (/etc/systemd/system/librenms-scheduler.timer; enabled; preset: disabled)
Active: active (waiting) since Mon 2025-03-24 04:34:21; 2 days ago
Until: Mon 2025-03-24 04:34:21; 2 days ago
Trigger: Wed 2025-03-26 09:14:00; 48s left
Triggers: ? librenms-scheduler.service

Mar 24 04:34:21 systemd[1]: Started LibreNMS Scheduler.

8

I added this to the cron file but no effect:

          • librenms cd /opt/librenms/ && php artisan schedule:run >> /dev/null 2>&1
9

Logs from scheduler itself:

2025-03-26 14:30:02 Running [Callback] … 1ms DONE

INFO No scheduled commands are ready to run.

INFO No scheduled commands are ready to run.

INFO No scheduled commands are ready to run.

INFO No scheduled commands are ready to run.

2025-03-26 14:35:02 Running [Callback] … 1ms DONE

INFO No scheduled commands are ready to run.

INFO No scheduled commands are ready to run.

INFO No scheduled commands are ready to run.

INFO No scheduled commands are ready to run.

2025-03-26 14:40:01 Running [Callback] … 1ms DONE

INFO No scheduled commands are ready to run.

10

Seems correct , maybe you have an issue with your cache driver.

11

Thank you! I went to look at that and… oh for crying out loud.

In addition to CACHE_DRIVER in .env I had to add the memcached host and port into the .env

" Using Memcached

Preferably you should set the memcached server settings via the web UI. Under Settings > Global Settings > Distributed poller, you fill out the memcached host and port, and then in your .env file you will need to add:

CACHE_DRIVER=memcached
MEMCACHED_HOST='myhost' <-----------------ADDED
MEMCACHED_PORT=memcachedport <--------------- ADDED

Even though they were added in the web UI.

Anyway thanks, seems to work now.

12

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