Trying to run daily.sh with distributed poller and get the following error

Help
1

I have 2 pollers when I run ./daily.sh on the “primary” poller I get the below.

Re-running /opt/librenms/daily.sh as librenms user
Updating to latest release OK
Updating Composer packages OK
Updating SQL-Schema OK
Updating submodules OK
Cleaning up DB FAIL
Another poller () has lock: lock.refresh_alert_rules
Clearing OS cache
Another poller () has lock: lock.syslog_purge
Another poller () has lock: lock.eventlog_purge
Another poller () has lock: lock.authlog_purge
Another poller () has lock: lock.perf_times_purge
Another poller () has lock: lock.device_perf_purge
Another poller () has lock: lock.purgeusers
Another poller () has lock: lock.syslog_purge
Another poller () has lock: lock.alert_log_purge
Another poller () has lock: lock.rrd_purge
Fetching notifications FAIL
Another poller () has lock: lock.notifications
Caching PeeringDB data FAIL
Another poller () has lock: lock.peeringdb

Any ideas do I need to stop the poller service on both pollers then run ./daily.sh?

2

I am not used to distributed polling,

but does it make sense to have “purging” activeted on both pollers?

Maybe remove the purge items from one config.

3

Will give that a try, thank you.

4

remove the purged items from one poller and still get the same error.

5

Hm,

I’m sorry, now I’m out.

We use LibreNMS just with the poller on localhost.

We have the purge options enabled without any issues.

Sorry

6

I don’t think you can actually disable those from running.

Can just ignore that output though, as long as one poller is running those jobs it’s fine.

7

Sorry for necromancy, but is there any way to move it between pollers?