Public bug reported: 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 ** Affects: munin (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/1014257 Title: MySQL monitoring fails when used with Percona or MariaDB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1014257/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
