Confusing Spine cron interval messages

[displaced]

Hi,

I'm trying to get Cacti up and running on my FreeBSD box. So far, I've got most things working. However, the poller is often refusing to collect data, claiming that the cron job is set to run too often. However, the message makes no sense.

Here's the output from my log, showing the end of one successful run and the very next run which failed:

Code: Select all

10/10/2016 10:45:00 PM - SPINE: Poller[0] Host[1] TH[1] DS[16] SNMP: v1: 127.0.0.1, dsname: cpu_user, oid: .1.3.6.1.4.1.2021.11.50.0, value: 6438203
10/10/2016 10:45:00 PM - SPINE: Poller[0] Host[1] TH[1] Total Time:   0.2 Seconds
10/10/2016 10:45:00 PM - SPINE: Poller[0] Time: 0.2717 s, Threads: 1, Hosts: 2
10/10/2016 10:45:00 PM - SYSTEM STATS: Time:0.3389 Method:spine Processes:1 Threads:1 Hosts:2 HostsPerProcess:2 DataSources:10 RRDsProcessed:10
10/10/2016 10:50:00 PM - POLLER: Poller[0] NOTE: Poller Int: '300', Cron Int: '300', Time Since Last: '0', Max Runtime '298', Poller Runs: '1'

[next run]

10/10/2016 10:50:00 PM - POLLER: Poller[0] NOTE: Cron is configured to run too often!  The Poller Interval is '300' seconds, with a minimum Cron period of '300' seconds, but only 0 seconds have passed since the poller last ran.
1

Now, maths was never my strong point, but I'm reasonably sure there's more than 0 seconds between 10:45 PM and 10:50 PM!

I've checked all crontabs - the only crontab entry I have for cacti is in cactiuser's own crontab. The entry looks like this:

Code: Select all

*/5 * * * * /usr/local/bin/php /usr/local/share/cacti/poller.php > /dev/null 2>&1

...pretty standard stuff.

Now, I've just checked the log again, and it ran successfully at 11:05 PM. So, 10:45 was fine, then it refused at 10:50 and 11:00, before running fine at 11:05 and again fine at 11:10.

Very odd! Any ideas?!

Thanks,
Chris

[phalek]

did you also check /etc/cron.d/ for any cacti related jobs ?