Hello every body,
i've postet last week about a prroblem with my graphs, they have gaps from time to time and its very anoing.
I ve checked and double checked everything and i have some data that i don't understand and i would like some help.
I have noticed some problems in the cacti.log file like
03/16/2009 10:55:03 AM - 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.
and
POLLER: Poller[0] WARNING: Cron is out of sync with the Poller Interval! The Poller Interval is '300' seconds, with a maximum of a '300' second Cron, but 304 seconds have passed since the last poll!
what should i do?
graph gap
Moderators: Developers, Moderators
hy everybody i solved the problem.
i have read :
http://docs.cacti.net/node/283
and at 10. it is written
Most rpm installations will setup the crontab entry now. If you've followed the installation instructions to the letter (which you should always do ), you may now have two poller running. That's not a good thing, though. Most rpm installations will setup cron in /etc/cron.d/cacti.
Now, please check all your crontabs, especially /etc/crontab and crontabs of users root and cactiuser. Leave only one poller entry for all of them. Personally, I've chosen /etc/cron.d/cacti to avoid problems when updating rpm's. Mosten often, you won't remember this item when updating lots of rpm's, so I felt more secure to put it here. And I've made some slight modifications, seeCode:
prompt> vi /etc/cron.d/cacti
*/5 * * * * cactiuser /usr/bin/php -q /var/www/html/cacti/poller.php > /var/local/log/poller.log 2>&1
This will produce a file /var/local/log/poller.log, which includes some additional informations from each poller's run, such as rrdtool errors. It occupies only some few bytes and will be overwritten each time.
If you're using the crontab of user "cactiuser" instead, this will look likeCode:
prompt> crontab -e -u cactiuser
*/5 * * * * /usr/bin/php -q /var/www/html/cacti/poller.php > /var/local/log/poller.log 2>&1
so i had in /etc/cron.d/cacti and in /etc/crontab the same thing added thats why it got stuck and had graph gaps.
so set only 1 pooler job like
*/5 * * * * /usr/bin/php -q /var/www/html/cacti/poller.php > /var/local/log/poller.log 2>&1
have a beer !
i have read :
http://docs.cacti.net/node/283
and at 10. it is written
Most rpm installations will setup the crontab entry now. If you've followed the installation instructions to the letter (which you should always do ), you may now have two poller running. That's not a good thing, though. Most rpm installations will setup cron in /etc/cron.d/cacti.
Now, please check all your crontabs, especially /etc/crontab and crontabs of users root and cactiuser. Leave only one poller entry for all of them. Personally, I've chosen /etc/cron.d/cacti to avoid problems when updating rpm's. Mosten often, you won't remember this item when updating lots of rpm's, so I felt more secure to put it here. And I've made some slight modifications, seeCode:
prompt> vi /etc/cron.d/cacti
*/5 * * * * cactiuser /usr/bin/php -q /var/www/html/cacti/poller.php > /var/local/log/poller.log 2>&1
This will produce a file /var/local/log/poller.log, which includes some additional informations from each poller's run, such as rrdtool errors. It occupies only some few bytes and will be overwritten each time.
If you're using the crontab of user "cactiuser" instead, this will look likeCode:
prompt> crontab -e -u cactiuser
*/5 * * * * /usr/bin/php -q /var/www/html/cacti/poller.php > /var/local/log/poller.log 2>&1
so i had in /etc/cron.d/cacti and in /etc/crontab the same thing added thats why it got stuck and had graph gaps.
so set only 1 pooler job like
*/5 * * * * /usr/bin/php -q /var/www/html/cacti/poller.php > /var/local/log/poller.log 2>&1
have a beer !
Who is online
Users browsing this forum: No registered users and 2 guests