As per Andreas comment
(https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1364298/comments/10),
the fix is available since bionic, hence, I am marking this as
fixreleased.
While xenial is still affected, it is now in ESM
(https://ubuntu.com/security/esm), and for that, I am marking it as
Just to get the plugin working a one-liner for xenial is attached. Any
unknown sections have to be explicitly skipped in the code.
** Patch added: "mysql_.patch"
https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1364298/+attachment/5442652/+files/mysql_.patch
--
You received this bug
https://github.com/munin-
monitoring/munin/commit/b45c07edcd3963936a7ac529620fc86f42ad6a1d is
present in 2.0.37-1ubuntu1 which is in cosmic.
It's also in the bionic package (2.0.37-1ubuntu0.1). Artful and older do
not have it.
--
You received this bug notification because you are a member of
https://github.com/munin-
monitoring/munin/commit/b45c07edcd3963936a7ac529620fc86f42ad6a1d is
present in 2.0.37-1ubuntu1 which is in cosmic.
It's also in the bionic package (2.0.37-1ubuntu0.1). Artful and older do
not have it.
--
You received this bug notification because you are a member of
for your reply and efforts. It's much
appreciated!
Kind regards,
Léon
-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of
ChristianEhrhardt
Sent: vrijdag 3 november 2017 13:54
To: Keijser, Leon
Subject: [Bug 1364298] Re: mysql plugins fail on mysql 5.5
Hi,
I beg your pardon for the delay, I didn't get the last update and lost track on
it sicne munin really isn't my home turf.
Anyway lets make something useful now.
The latest version is 2.0.34 and still does not have the fix.
Given that we are a sync to Debian we should fix it there as well,
Using 16.04 here with munin-plugins-core 2.0.25-2ubuntu0.16.04.3 and
experiencing the same problem. Using the mysql_ file from
https://github.com/munin-
monitoring/munin/blob/master/plugins/node.d/mysql_ fixes it. Can we
expect an update for xenial?
--
You received this bug notification because
Hi ChristianEhrhardt,
I patched the file mysql_ in /usr/share/munin/plugins/
This file is included in munin-plugins-core, see
http://packages.ubuntu.com/xenial/all/munin-plugins-core/filelist
I dont know what the .in-file is for, I also can not find it in source-git
Hi,
thanks Jan for the patch!
As note to the bug - in the packaging the patch is against
./plugins/node.d/mysql_.in, so it should become a quilt patch.
I checked the latest packaged version which is 2.0.30-1 which still does
not have the fix.
Although upstream that file is
The attachment "patch-munin-mysql_.diff" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
There are some Bugfixes you need:
https://github.com/munin-monitoring/munin/pull/109/
** Patch added: "patch-munin-mysql_.diff"
https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1364298/+attachment/4807523/+files/patch-munin-mysql_.diff
--
You received this bug notification because you
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Next steps are:
1) Update the development release to a new enough version, or cherry-pick this
fix into the development release.
2) Presumably the mysql plugin is completely broken in Trusty then, for the
Hey Robie,
thanks for the reply.
1) You are talking about a new version / cherry-pick, but who will do this? If
i had to decide this, i would make a cherry-pick. Do i have the ability to
cherry-pick this?
2) the mysql plugin is broken in 2 of 3 cases. As described, the error will
occur if
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Next steps are:
1) Update the development release to a new enough version, or cherry-pick this
fix into the development release.
2) Presumably the mysql plugin is completely broken in Trusty then, for the
Hey Robie,
thanks for the reply.
1) You are talking about a new version / cherry-pick, but who will do this? If
i had to decide this, i would make a cherry-pick. Do i have the ability to
cherry-pick this?
2) the mysql plugin is broken in 2 of 3 cases. As described, the error will
occur if
15 matches
Mail list logo
