Comments on: MySQL Cacti templates 1.0.0 released http://www.xaprb.com/blog/2008/06/01/mysql-cacti-templates-100-released/ Stay curious! Thu, 09 Feb 2012 09:56:43 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Mike Wallace http://www.xaprb.com/blog/2008/06/01/mysql-cacti-templates-100-released/#comment-14768 Mike Wallace Thu, 19 Jun 2008 01:16:18 +0000 http://www.xaprb.com/blog/2008/06/01/mysql-cacti-templates-100-released/#comment-14768 Yep - that's the guide we're using. Nice work :) Yep – that’s the guide we’re using. Nice work :)

]]> By: Xaprb http://www.xaprb.com/blog/2008/06/01/mysql-cacti-templates-100-released/#comment-14767 Xaprb Wed, 18 Jun 2008 14:52:54 +0000 http://www.xaprb.com/blog/2008/06/01/mysql-cacti-templates-100-released/#comment-14767 The best way I've found to clear out that deadlock, without impacting your server: http://www.xaprb.com/blog/2006/08/08/how-to-deliberately-cause-a-deadlock-in-mysql/ The best way I’ve found to clear out that deadlock, without impacting your server:

http://www.xaprb.com/blog/2006/08/08/how-to-deliberately-cause-a-deadlock-in-mysql/

]]> By: Mike Wallace http://www.xaprb.com/blog/2008/06/01/mysql-cacti-templates-100-released/#comment-14765 Mike Wallace Wed, 18 Jun 2008 05:16:27 +0000 http://www.xaprb.com/blog/2008/06/01/mysql-cacti-templates-100-released/#comment-14765 Baron, I posted this over at the cacti forums: http://forums.cacti.net/viewtopic.php?p=138104 - but thought I'd hit you here, too: What does it take to update these templates to be compatible with 0.8.7b (in my case)? I'm definitely not one with the internals of cacti and templating. The most I've done is deconstruct the db schema in order to bulk add several thousand existing RRDs from another system... I've been running the xaprb templates for a month or so on a test 0.8.6x environment, and I'd love to pull it forward now that the spine kinks have been worked out. Apart from the spine issues and an ongoing 'show engine innodb status' deadlock oveflow we're going to try clearing tomorrow morning, the new graphs have been *great* on 8 of our production DBs. Unfortunately, the deadlock cruft is on our master production farm scheduling node, and we're really gun-shy about screwing with that one. The last time I tried being clever with it, I took $Company down for about two and a half hours. I suck at life. Baron,
I posted this over at the cacti forums: http://forums.cacti.net/viewtopic.php?p=138104 – but thought I’d hit you here, too:

What does it take to update these templates to be compatible with 0.8.7b (in my case)? I’m definitely not one with the internals of cacti and templating. The most I’ve done is deconstruct the db schema in order to bulk add several thousand existing RRDs from another system…

I’ve been running the xaprb templates for a month or so on a test 0.8.6x environment, and I’d love to pull it forward now that the spine kinks have been worked out. Apart from the spine issues and an ongoing ‘show engine innodb status’ deadlock oveflow we’re going to try clearing tomorrow morning, the new graphs have been *great* on 8 of our production DBs. Unfortunately, the deadlock cruft is on our master production farm scheduling node, and we’re really gun-shy about screwing with that one. The last time I tried being clever with it, I took $Company down for about two and a half hours. I suck at life.

]]>