Package: munin-plugins-core
Version: 2.0.6 and earlier
Severity: normal
The check used in mysql_ to determined whether InnoDB is disabled on a MySQL
server is using either an outdated or wrong string for comparison. The patch
below will fix this, leaving the original check intact for backward
compatibility.
Suggested patch:
Description: Patch to fix test for now changed response when
InnoDB is disabled on MySQL/MariaDB.
Origin: other
Bug-Debian:
Forwarded: no
Author: Stefan Rubner <ste...@whocares.de>
Last-Update: 2013-01-13
Index: munin-2.10/plugins/node.d/mysql_.in
===================================================================
--- munin-2.0.10.a/plugins/node.d/mysql_.in 2013-01-09
--- 16:46:54.000000000 +0100
+++ munin-2.0.10/plugins/node.d/mysql_.in 2013-01-13
22:22:37.269463569 +0100
@@ -970,7 +970,7 @@
$sth->execute();
};
if ($@) {
- if ($@ =~ /Unknown table engine 'INNODB'|Cannot call SHOW INNODB
- STATUS because skip-innodb is defined/i) {
+ if ($@ =~ /Unknown (storage|table) engine 'INNODB'|Cannot call SHOW
- INNODB STATUS because skip-innodb is defined/i) {
$data->{_innodb_disabled} = 1;
return;
}
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
