boost is wraping the poller

[gsaray101]

I ran the boost manually again and redirected output to a file, and I see this type of errors in the log:

ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
OK
OK
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
OK
OK
OK
OK
OK
OK
OK

[TheWitness]

ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)
ERROR: illegal attempt to update using time 1223504705 when last update time is 1223504885 (minimum one second step)

Make sure before you run manually, that you don't already have one running. I believe forcing in cron is a bad idea frankly.

TheWitness

[gsaray101]

other than this error, I dont see any errors. Do I have to use boost and spine? What can I use so that I dont have to use boost?

Thanks,

mike

[TheWitness]

Big disk arrays and lot's of physical RAM. Those disk arrays can be solid state now, which is you have a RAID0 array of 6 Solid State 32GByte drives from the "right" vendor (an currently there is one), you can bring polling times way down. Don't forget to have 1GByte more of physical memory than you have RRDfiles.

TheWitness

[gsaray101]

witness:

I really appreciate your guidence here. But my question is that, we have similar servers (hardware wise) the same number of device on other cacti servers, and I dont see this behaviour. Is there a version of spine where polls and writes to the rrd files? If can ommit boost, that would be great?

[BorisL]

I ran into the same situation as described without any usage of cron - just cacti's web interface.

Symptoms were very simple: poller_boost.php starts, eats most of records from poller_output_table and then `hang' in while(1) loop (line 89) eating upto 100% CPU.
Inserting usleep(100) into end of while(1) cycle helps to reduce CPU to 15%, but not endless cycle. It stops when maximum runtime comes and next run of poller_ouput does the same things - it `hangs' because of old records that can not be written into rrd file due to 'too late' reason.

I tried a couple of time to reinitiate boost (truncate boost's tables, tuning settings) - but only that scenario came.

I AM SURE there was no poller_boost.php running just before I ticked "Enable on demand RRD updating".

[gsaray101]

I have 4 gigs of memory and 900giga bytes of disk space. The question I have is that, I have other servers with the same hardware and config, I dont see this problem there. Only this server.

[TheWitness]

Boost 2.0 is official. Please Check it Out Here:

http://forums.cacti.net/viewtopic.php?p=150337#150337

Regards,

TheWitness