1.2.19 Polling Cycle Exceeded Poller Interval

Post general support questions here that do not specifically fall into the Linux or Windows categories.

Moderators: Developers, Moderators

Post Reply
mpj
Posts: 19
Joined: Wed Jun 01, 2005 10:24 am
Contact:

1.2.19 Polling Cycle Exceeded Poller Interval

Post by mpj »

Ubuntu 20.04 LTS, 16 GB RAM, 8 CPUs, Cacti 1.2.19 recent upgrade from 1.2.18, Spine 1.2.19, 274 total devices, over 34,000 SNMP gets, 5 minute polling interval.

I have had this happen from time to time maybe once or twice a day, but after upgrading to 1.2.19, it seems to happen multiple times an hour. Whenever any device is slow to answer the SNMP queries, or unable to because of its own workload, the poller then is stuck for over the 300 second polling interval.
2022/02/22 12:05:17 - SYSTEM STATS: Time:16.2156 Method:spine Processes:3 Threads:16 Hosts:261 HostsPerProcess:87 DataSources:35107 RRDsProcessed:8603
2022/02/22 12:05:04 - MAILER INFO: Mail successfully sent via SMTP from 'Cacti <cacti@my.domain>', to 'Administrator <admin@my.domain>', cc '', and took 0.07 seconds, Subject 'Cacti System Warning'
2022/02/22 12:05:04 - SYSTEM STATS: Time:302.8541 Method:spine Processes:3 Threads:16 Hosts:261 HostsPerProcess:87 DataSources:35107 RRDsProcessed:8107
2022/02/22 12:03:08 - CMDPHP PHP ERROR Backtrace: (CactiShutdownHandler())
2022/02/22 12:03:08 - ERROR PHP ERROR: Maximum execution time of 299 seconds exceeded in file: /wwwsites/cacti/lib/database.php on line: 287
2022/02/22 12:00:20 - SPINE: Poller[Main Poller] PID[5228] PT[140192606308096] Device[MyRemoteDevice] HT[1] DS[MyRemoteDevice - Traffic - 192.192.192.193 - lan0] Graphs[MyRemoteDevice - Traffic - Port1 ] WARNING: SNMP timeout detected [1500 ms], ignoring host 'name.my.domain'
2022/02/22 12:00:20 - SPINE: Poller[Main Poller] PID[5228] PT[140192606308096] Device[MyRemoteDevice] HT[1] DS[MyRemoteDevice - Traffic - 192.192.192.192 - mgmt0] Graphs[MyRemoteDevice - Traffic - Port0 ] WARNING: SNMP timeout detected [1500 ms], ignoring host 'name.my.domain'
2022/02/22 12:00:20 - SPINE: Poller[Main Poller] PID[5228] PT[140192606308096] Device[MyRemoteDevice] HT[1] DS[MyRemoteDevice - Traffic - 192.192.192.192 - mgmt0] Graphs[MyRemoteDevice - Traffic - Port0 ] WARNING: SNMP timeout detected [1500 ms], ignoring host 'name.my.domain'
2022/02/22 12:00:20 - SPINE: Poller[Main Poller] PID[5228] PT[140192606308096] Device[MyRemoteDevice] HT[1] DS[MyRemoteDevice - Traffic - 8.8.8.8 - wanport1] Graphs[MyRemoteDevice - Traffic - wanport1 ] WARNING: SNMP timeout detected [1500 ms], ignoring host 'name.my.domain'
2022/02/22 12:00:20 - SPINE: Poller[Main Poller] PID[5228] PT[140192606308096] Device[MyRemoteDevice] HT[1] DS[MyRemoteDevice - Traffic - 8.8.8.8 - wanport1] Graphs[MyRemoteDevice - Traffic - wanport1 ] WARNING: SNMP timeout detected [1500 ms], ignoring host 'name.my.domain'
The resulting email just states:
WARNING: Cacti Polling Cycle Exceeded Poller Interval by 2.8581240177155 seconds
The command line that seems to be hanging as seen in top is:
/usr/bin/php -q /www/cacti/poller.php --force
I have had a couple instances where the poller has been stuck for over 1,000 seconds helping to cause two more polling cycles to throw errors. The "hanging" device is not always the same. I added a remote poller to eliminate the possibility that the single Cacti box is overloaded. Where do I go from here? Is there anyone else that is experiencing this that might point to a bug in this version?

Thanks,

--MPJ
User avatar
TheWitness
Developer
Posts: 17061
Joined: Tue May 14, 2002 5:08 pm
Location: MI, USA
Contact:

Re: 1.2.19 Polling Cycle Exceeded Poller Interval

Post by TheWitness »

You have to ensure that spine actually runs. That's generally one of the issues, and when it's running, use more than one thread, but don't use too many. There is a point of diminishing return on threading in spine (depending on the size of your system and database (it's own threads)), and the MariaDB version. Starting in the 10.5.x series, MariaDB threading reaches a new level, but the long lived branch is MariaDB 10.6. So, though my production instance is 10.5, there is no way to easily upgrade to 10.6+. It's basically restore from backup and my database is > 10TB. Not an easy upgrade.
True understanding begins only when we realize how little we truly understand...

Life is an adventure, let yours begin with Cacti!

Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages


For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests