MySQL monitoring fails when used with Percona or MariaDB

[Mikkel Høgh]

Several of the MySQL monitors give errors like the following when used with a MariaDB server in Precise:

2012/06/17-12:10:27 [30020] Error output from mysql_qcache:
2012/06/17-12:10:27 [30020] Unknown section: Main thread process no. 9457, id 140001932375808, state: waiting for server activity at /etc/munin/plugins/mysql_qcache line 1086.
2012/06/17-12:10:27 [30020] Service 'mysql_qcache' exited with status 255/0.

As far as I can tell, this issue has been addressed upsteam:

* https://github.com/kjellm/munin-mysql/issues/34
* https://github.com/kjellm/munin-mysql/issues/37

I'm pretty sure that these fixes were included in the 1.4.7 release of Munin, but sadly, Precise only include 1.4.6.
http://munin-monitoring.org/browser/tags/1.4.7/ChangeLog

[Rowan Wookey (rwky)]

This is still present in trusty, it appears the plugin is ancient and hasn't been updated in years.

[Barry O'Donovan (barryo)]

Looks like it's fixed by this patch:

https://github.com/kjellm/munin-mysql/commit/77c3f88f4807fb07d0ce6c26ef86d0c7eb196f8b

[Oleg Cherkasov (o1e9)]

Thanks Barry! The patch did the fix the issue.