Home > Cacti > CactiEZ 0.6 not graphing after time change

CactiEZ 0.6 not graphing after time change

Recently I did a fresh install of CactiEZ 0.6. After I changed the timezone and time (synced it to a NTP source), the graphs didn’t get filled anymore. Even the localhost graphs, which are installed by default, aren’t working anymore.

Here I do the sync with a NTP source;

[root@localhost /]# ntpdate pool.ntp.org
27 Mar 17:07:18 ntpdate[4602]: adjust time server 83.98.201.133 offset -0.025180 sec

After this, the graphs are not being filled anymore. At first seeing, I had no idea what caused this problem. So i decided to put the logging level of the poller in DEBUG mode to see what is going wrong. This can by done in the Cacti console via Settings > Poller Logging Level > DEBUG.

Now, when I do a poller cycle, the following output is generated;

[root@localhost /]# php /var/www/html/poller.php
03/27/2009 05:14:04 PM – POLLER: Poller[0] NOTE: Poller Int: ’60′, Cron Int: ’60′, Time Since Last: ‘-20937′, Max Runtime ’58′, Poller Runs: ’1′

03/27/2009 05:14:04 PM – POLLER: Poller[0] NOTE: Cron is configured to run too often!  The Poller Interval is ’60′ seconds, with a minimum Cron period of ’60′ seconds, but only -20937 seconds have passed since the poller last ran.

As you can see, the time since the last poll has passed is a negative number! Somewhere, there is a timestamp at which the poller can see that it must not run yet. But because the time has been changed, this timestamp is somewhere in the future.

To solve this problem, you have to run the poller mode in forced mode;

[root@localhost /]# php /var/www/html/poller.php –force

Now the poller start all over again with a new timestamp. You can see the timestamp is accurate when you launch the poller again;

[root@localhost /]# php /var/www/html/poller.php
03/27/2009 05:25:18 PM – POLLER: Poller[0] NOTE: Poller Int: ’60′, Cron Int: ’60′, Time Since Last: ’17′, Max Runtime ’58′, Poller Runs: ’1′

03/27/2009 05:25:18 PM – POLLER: Poller[0] NOTE: Cron is configured to run too often!  The Poller Interval is ’60′ seconds, with a minimum Cron period of ’60′ seconds, but only 17 seconds have passed since the poller last ran.

Categories: Cacti Tags:
  1. Benjamin
    July 5th, 2010 at 10:59 | #1

    Awesome solution!
    Thank you so much!

    I was trying for hours to fix this problem.

    :)

  2. Benjamin
    July 11th, 2010 at 12:32 | #2

    bah…

    today timer moved backwards again…
    had to change timezone, and now it doesnt poll again..
    have any idea what it could be?

    [root@cacti html]# php /var/www/html/poller.php –force
    07/11/2010 02:30:53 PM – POLLER: Poller[0] NOTE: Poller Int: ’60′, Cron Int: ’60′, Time Since Last: ’52′, Max Runtime ’58′, Poller Runs: ’1′
    Waiting on 1/1 pollers.
    OK u:0.00 s:0.00 r:1.10
    OK u:0.00 s:0.00 r:1.10
    ERROR: illegal attempt to update using time 1278847854 when last update time is 1278869911 (minimum one second step)
    OK u:0.00 s:0.00 r:1.10
    OK u:0.00 s:0.00 r:1.10
    ERROR: illegal attempt to update using time 1278847854 when last update time is 1278869911 (minimum one second step)
    ERROR: illegal attempt to update using time 1278847854 when last update time is 1278869911 (minimum one second step)
    ERROR: illegal attempt to update using time 1278847854 when last update time is 1278869911 (minimum one second step)
    ERROR: illegal attempt to update using time 1278847854 when last update time is 1278869911 (minimum one second step)
    OK u:0.00 s:0.00 r:1.10
    ERROR: illegal attempt to update using time 1278847854 when last update time is 1278869911 (minimum one second step)
    OK u:0.00 s:0.00 r:1.11
    ERROR: illegal attempt to update using time 1278847854 when last update time is 1278869911 (minimum one second step)
    ERROR: illegal attempt to update using time 1278847854 when last update time is 1278869911 (minimum one second step)
    ERROR: illegal attempt to update using time 1278847854 when last update time is 1278869911 (minimum one second step)
    ERROR: illegal attempt to update using time 1278847854 when last update time is 1278869911 (minimum one second step)
    ERROR: illegal attempt to update using time 1278847854 when last update time is 1278869911 (minimum one second step)

  1. No trackbacks yet.