Cacti

Ran into the same problem with upgrade from 0.8.7i -> 0.8.8, using MySQL 5.0.51a - fixed by changing the query slightly:

"PRIMARY KEY (`local_data_id`, `rrd_name`, `time`) USING BTREE"

becomes

"PRIMARY KEY USING BTREE (`local_data_id`, `rrd_name`, `time`)"


Shaun

Any further news on this? MySQL Bug#30590 would appear to relate directly to this, and was committed to versions > 5.0.52 / 4.1.24. I have also tested this using a Debian 5.0.5 package (assumed fairly common) which reports MySQL 5.0.51a and the issue mentioned isn't replicable. Additionally, boost h...

I'm currently deploying a rather large installation on minimal hardware and have been making a number of changes to achieve the desired results. Whilst I understand the merits of the delete operation currently in use within boost, using a temporary rcaston_[random] table in memory, over the older me...

IMHO you may consider some 10,000 data source as a no-brainer Above 100,000 data sources it will become tricky, but doable. Never heard of 1,000,000. Just a rule of thumb. Reinhard I agree that 100,000 data sources should be doable - however this will depend on hardware really. We are currently up ...

This whole situation worries me as this should not happen. The only process that uses temp tables is the main poller process. So, you should probably send me your "modified" version so that I can assess what should be carried upstream and where the bug is. You are absolutely correct, my m...

Not sure how to explain this well, but here goes... Under Data Queries, find the relevant data query for the graph with this problem and then click on the relevant 'Associated Graph Templates' - under suggested values for the graph template you will need to put two titles, one with the |query_ifAlia...

Are you using Boost with the boost server? If so make sure the Boost server is running and that it hasn't lost its connection to the database (a common problem that has been recently fixed in Boost v2.3). The boost server loosing its connection to the MySQL database will cause this to happen and wil...

Currently running a fairly large installation using a heavily modified version of Boost 2.1, however a problem that has come up with this (and other versions) is that the temporary table used when running poller_boost already exists - bad rand(). This causes major headaches when it occurs (albeit no...

I don't know how "easy" that would be, but it seems to me like it would be a more permanent fix to the current structure, rather than re-vamping the whole thing. We were experiencing the same problem - generating the graph tree from the database was a killer on a first-visit when the user...