<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Improved Cacti monitoring templates for MySQL</title>
	<link>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/</link>
	<description>Stay curious!</description>
	<pubDate>Fri, 16 May 2008 03:45:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>By: Dejc</title>
		<link>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/#comment-14519</link>
		<author>Dejc</author>
		<pubDate>Tue, 06 May 2008 05:54:01 +0000</pubDate>
		<guid>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/#comment-14519</guid>
		<description>When I try to import your xml I get the following error
    Error: XML: Hash version does not exist.
Is this a cacti version issue? I have 0.8.6i?

Pleas help me?</description>
		<content:encoded><![CDATA[<p>When I try to import your xml I get the following error<br />
    Error: XML: Hash version does not exist.<br />
Is this a cacti version issue? I have 0.8.6i?</p>
<p>Pleas help me?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/#comment-14494</link>
		<author>Matt</author>
		<pubDate>Wed, 30 Apr 2008 00:42:07 +0000</pubDate>
		<guid>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/#comment-14494</guid>
		<description>Great, thanks Mike.

That did clear up those script errors, and provides data when calling it directly.  Still no joy when running poller.

It's parsing correctly in the multi output parser section, but fails on the rrd update.

04/29/2008 07:40:10 PM - POLLER: Poller[0] Parsed MULTI output field 'rows_deleted:5066' [map rows_deleted-&#62;rows_deleted]
04/29/2008 07:40:10 PM - POLLER: Poller[0] CACTI2RRD: /usr/bin/rrdtool update /var/www/cacti/rra/mysql_server_rows_deleted_52.rrd --template  1209516001:U
ERROR: Not enough arguments

Gotta be something in the data template, but too much staring at it today.

Thanks for the help, and thanks again to the author for the software =)</description>
		<content:encoded><![CDATA[<p>Great, thanks Mike.</p>
<p>That did clear up those script errors, and provides data when calling it directly.  Still no joy when running poller.</p>
<p>It&#8217;s parsing correctly in the multi output parser section, but fails on the rrd update.</p>
<p>04/29/2008 07:40:10 PM - POLLER: Poller[0] Parsed MULTI output field &#8216;rows_deleted:5066&#8242; [map rows_deleted-&gt;rows_deleted]<br />
04/29/2008 07:40:10 PM - POLLER: Poller[0] CACTI2RRD: /usr/bin/rrdtool update /var/www/cacti/rra/mysql_server_rows_deleted_52.rrd &#8211;template  1209516001:U<br />
ERROR: Not enough arguments</p>
<p>Gotta be something in the data template, but too much staring at it today.</p>
<p>Thanks for the help, and thanks again to the author for the software =)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/#comment-14493</link>
		<author>Mike</author>
		<pubDate>Wed, 30 Apr 2008 00:26:08 +0000</pubDate>
		<guid>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/#comment-14493</guid>
		<description>Matt - this may be related - on my test system (no replication, hence no bin logging), the script crapped out when it tried to retrieve information about said logs.  I commented out anything referring to them- ie: lines 163ish-170ish (I've added some debug code to my own copy, so the line numbers might be a little off) (including "SHOW MASTER LOGS"), and lines 353ish-363ish ("including AS binary_log_space").  That seems to allow the script to run cleanly, though I haven't gone back to recreate the rrds, and whatnot.  Cacti kinda makes my brain bleed.</description>
		<content:encoded><![CDATA[<p>Matt - this may be related - on my test system (no replication, hence no bin logging), the script crapped out when it tried to retrieve information about said logs.  I commented out anything referring to them- ie: lines 163ish-170ish (I&#8217;ve added some debug code to my own copy, so the line numbers might be a little off) (including &#8220;SHOW MASTER LOGS&#8221;), and lines 353ish-363ish (&#8221;including AS binary_log_space&#8221;).  That seems to allow the script to run cleanly, though I haven&#8217;t gone back to recreate the rrds, and whatnot.  Cacti kinda makes my brain bleed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/#comment-14492</link>
		<author>Matt</author>
		<pubDate>Wed, 30 Apr 2008 00:21:11 +0000</pubDate>
		<guid>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/#comment-14492</guid>
		<description>Very glad someone took a crack at this, but i'm having some difficulties.

All NAN in the graphs, this error when you try to run the php script as the cacti user.

 AS binary_log_space ': Thread stack overrun:  120304 bytes used of a 131072 byte stack, and 10788 bytes needed.  Use 'mysqld -O thread_stack=#' 

I've used the older mysql templates with no issues, and fairly sure this is not a cacti issue, used for a lot of other stuff.</description>
		<content:encoded><![CDATA[<p>Very glad someone took a crack at this, but i&#8217;m having some difficulties.</p>
<p>All NAN in the graphs, this error when you try to run the php script as the cacti user.</p>
<p> AS binary_log_space &#8216;: Thread stack overrun:  120304 bytes used of a 131072 byte stack, and 10788 bytes needed.  Use &#8216;mysqld -O thread_stack=#&#8217; </p>
<p>I&#8217;ve used the older mysql templates with no issues, and fairly sure this is not a cacti issue, used for a lot of other stuff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xaprb</title>
		<link>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/#comment-14490</link>
		<author>Xaprb</author>
		<pubDate>Mon, 28 Apr 2008 19:37:50 +0000</pubDate>
		<guid>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/#comment-14490</guid>
		<description>One of the things I was thinking about doing was adding options to the make-template.pl script so you can easily generate templates with or without the InnoDB-specific things and the MyISAM-specific things, or even generate one template at a time so you can pick which ones you want.  Do you think this is helpful?

Also, in this case the PHP script should not try to monitor SHOW INNODB STATUS, of course :-)  I haven't tested it on servers that don't have InnoDB enabled.  Did it crash, or just return all 0 results?  I would like it to return all 0 results, not crash.</description>
		<content:encoded><![CDATA[<p>One of the things I was thinking about doing was adding options to the make-template.pl script so you can easily generate templates with or without the InnoDB-specific things and the MyISAM-specific things, or even generate one template at a time so you can pick which ones you want.  Do you think this is helpful?</p>
<p>Also, in this case the PHP script should not try to monitor SHOW INNODB STATUS, of course :-)  I haven&#8217;t tested it on servers that don&#8217;t have InnoDB enabled.  Did it crash, or just return all 0 results?  I would like it to return all 0 results, not crash.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pieter</title>
		<link>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/#comment-14489</link>
		<author>Pieter</author>
		<pubDate>Mon, 28 Apr 2008 19:27:12 +0000</pubDate>
		<guid>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/#comment-14489</guid>
		<description>Great stuff, working perfectly here, and came right on time. I needed to comment out the Innodb stuff since I have --skip-innodb enabled.</description>
		<content:encoded><![CDATA[<p>Great stuff, working perfectly here, and came right on time. I needed to comment out the Innodb stuff since I have &#8211;skip-innodb enabled.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/#comment-14488</link>
		<author>Mike</author>
		<pubDate>Mon, 28 Apr 2008 05:32:25 +0000</pubDate>
		<guid>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/#comment-14488</guid>
		<description>Oh man. Bless you. I'm going to try them out first thing in the morning. The temysql scripts were a great start, but haven't changed in years. Thanks so much for the work on this!</description>
		<content:encoded><![CDATA[<p>Oh man. Bless you. I&#8217;m going to try them out first thing in the morning. The temysql scripts were a great start, but haven&#8217;t changed in years. Thanks so much for the work on this!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank Mashraqi</title>
		<link>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/#comment-14487</link>
		<author>Frank Mashraqi</author>
		<pubDate>Mon, 28 Apr 2008 01:36:51 +0000</pubDate>
		<guid>http://www.xaprb.com/blog/2008/04/27/improved-cacti-monitoring-templates-for-mysql/#comment-14487</guid>
		<description>Very nice! Can't wait to try them in the coming week. Thanks for sharing.</description>
		<content:encoded><![CDATA[<p>Very nice! Can&#8217;t wait to try them in the coming week. Thanks for sharing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
