Cycle plugin funny issue

[DeeL]

Hi,

No big deal but, just for you to know it happens.

Just reinstalled cycle-0.7 plugin on a brand new cacti on brand new VM, nothing has been configured apart from spine. I discovered that without configuring cyle, the default cyle "time" was about 1 sec, all graphs showing one after the other every less than a second.

I selected 5sec from the drop down menu of the cyle tab, and graphs showed every 5sec. I went back to another tab, went back again to cycle tab. Same issue.

After one last test, I checked cacti logs and saw :
07/22/2010 12:56:13 AM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
07/22/2010 12:55:48 AM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
07/22/2010 12:55:27 AM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="

I went to the configuration tab of cyle (in the settings menu), chose "5sec" and now it's ok.

Deel

[wormwood]

I had the same issue with the 1 second interval until I changed it from the console settings. However, I kind of liked the 1 second interval, I wouldn't mind seeing it as an option. However, even after changing it to 5 seconds I am still getting all those annoying cacti log entries:

Code: Select all

09/01/2010 03:49:09 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
09/01/2010 03:49:09 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
09/01/2010 03:49:09 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
09/01/2010 03:49:09 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
09/01/2010 03:49:09 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
09/01/2010 03:49:09 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="

I am still getting thousands of them. Any reason for me to be concerned?.

Thanks,

wormwood

[TheWitness]

Use latest from docs site. Hmm, maybe it's not updated from SVN. I'll have to check.

[wormwood]

Howdy,

I updated cycle to version 1.2 and I am still getting THOUSANDS of these irritating log entries:

Code: Select all

10/05/2010 05:04:03 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
10/05/2010 05:04:03 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
10/05/2010 05:04:03 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
10/05/2010 05:04:03 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
10/05/2010 05:04:03 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
10/05/2010 05:04:03 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
10/05/2010 05:04:03 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
10/05/2010 05:04:03 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
10/05/2010 05:04:03 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
10/05/2010 05:04:03 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
10/05/2010 05:04:03 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
10/05/2010 05:04:03 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
10/05/2010 05:04:03 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="
10/05/2010 05:04:03 PM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="

Doesn't seem to be causing any issues but its annoying as hell when your trying to read the logs. Any idea on how I can fix this?

Thanks,

wormwood

[TheWitness]

Looks like you have a messed up graph template. That's what I would think. Is it caused when viewing any graph in question?

TheWitness

[wormwood]

Doesn't seem to be caused by any graph in particular. I've removed cycle and watched the log when no graphs were being viewed and was still getting those log entries. They appeared after upgrading to version .7. I am now running 1.2.

Thanks,

wormwood

[TheWitness]

Run the "repair_database.php" script in the cli directory.

TheWitness

[Chrysalis]

I too have the same error and it seem to coincide with me putting the latest syslog plugin on although I have been trying tomake boost stable.

I have just uninstalled syslog but preserved data and waiting now for the next 5 minute log update to see what happens.

--edit--

in my case uninstalling the syslog plugin got rid of the errors.

[TheWitness]

Goto console->settings->syslog and press save...

TheWitness

[Chrysalis]

Goto console->settings->syslog and press save...

TheWitness

thanks can confirm this worked.

[wormwood]

So I have run the repair script in the past and completed another pass just now but to no avail. I am still seeing the same errors. My log files are now GINORMOUS:

Code: Select all

[root@cacti cli]# du -h /xfs/www/html/log/
2.9G    /xfs/www/html/log/
[root@cacti cli]# ls -alF /xfs/www/html/log/
total 2992344
drwxrwxrwx  2 apache apache      4096 Oct 14 04:02 ./
drwxr-xr-x  4 root   root          26 Jul 19 14:53 ../
-rw-r--r--  1 apache apache       101 Oct 14 13:49 boost.log
-rwxrwxrwx  1 apache apache 230362645 Oct 14 17:07 cacti.log*
-rwxrwxrwx  1 apache apache 408744633 Oct 14 04:02 cacti.log.1*
-rwxrwxrwx  1 apache apache 404626753 Oct 13 04:02 cacti.log.2*
-rwxrwxrwx  1 apache apache 406885300 Oct 12 04:02 cacti.log.3*
-rwxrwxrwx  1 apache apache 402942681 Oct 11 04:02 cacti.log.4*
-rwxrwxrwx  1 apache apache 402930012 Oct 10 04:02 cacti.log.5*
-rwxrwxrwx  1 apache apache 403009427 Oct  9 04:02 cacti.log.6*
-rwxrwxrwx  1 apache apache 403404524 Oct  8 04:02 cacti.log.7*
-rwxrwxrwx  1 apache apache   1106339 Aug 13 14:17 cacti.log.new*
-rwxrwxrwx  1 apache apache        33 May  7 09:45 .htaccess*
-rw-r--r--  1 apache apache       200 Oct 14 17:07 poller.log

I've got enough storage so luckily this isn't going to kill me. However parsing the logs is now a serious PITA. Anything else you can recommend?

Thanks again,

wormwood