Hey all... I've got kind of a sanity check question here. I feel like after a couple of changes (adding some more hosts, adding error graphs in addition to traffic, upgrading spine and cacti and the PIA), I've got the boost poller process running infinitely it seems.
I've got the boost poller running from cron (as it doesn't seem to do anything if I don't do that). The line in cron (as given to me by TheWitness):
Code: Select all
0 */1 * * * /usr/local/bin/php -q /var/www/cacti-0.8.7a/plugins/boost/poller_boost.php -f -d
What should I realistically expect here? I extended the boost poller process to run for an hour max and it's even hitting that. I've got a 5 minute polling time (takes about a minute)
Code: Select all
Current Boost Status
Boost On Demand Updating: Running
Total Data Sources: 152704
Total Boost Records: 61306
Previous Runtime
Last Start Time: 2007-11-20 19:00:02
Last Run Duration: 3600.5804 Seconds
RRD's Updated: 13869763
That seems like an awful lot of records updated to me, but maybe that's accurate... 60 minutes / 5 would be 12 polls... 12 * 152704 would be 1832448.. Should I be expecting roughly 1832448?
Code: Select all
11/20/2007 07:00:02 PM - SYSTEM BOOST STATS: Time:3600.5804 RRDUpdates:13869763
11/20/2007 07:00:02 PM - CMDPHP: Poller[0] FATAL: RRD On Demand Updater Exceeded Runtime Limits!!!
I'm using the rrdtool from the 1.3 beta, just to see if it helped (it didn't really, assuming I did everything right). Just trying to figure out if there's a way to optimize that better somehow.