Thank you for taking the time to get this through Christian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038044
Title:
munin-node: apt_all does not Grok Ubuntu (possible regression)
To manage
The latest version got merged in Disco - this is fixed in
https://launchpad.net/ubuntu/+source/munin/2.0.47-1ubuntu3
** Changed in: munin (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FYI: I filed bug 1818208 to check if we would be allowed to still sync
it now or if we have to wait for 19.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038044
Title:
munin-node: apt_all does
Ubuntu 19.04 has entered Feature Freeze already.
Given the (embarrassing) age of the bug and it's rather low priority I think it
will not drive a Feature Freeze exception. But we can easily fix this in early
19.10 by syncing the most recent package as the only Ubuntu Delta we have for
bug
** Changed in: munin (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038044
Title:
munin-node: apt_all does not Grok Ubuntu (possible regression)
** Changed in: munin (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038044
Title:
munin-node: apt_all does not Grok Ubuntu (possible regression)
To
** Changed in: munin (Debian)
Importance: Undecided => Unknown
** Changed in: munin (Debian)
Status: New => Unknown
** Changed in: munin (Debian)
Remote watch: None => Debian Bug tracker #715141
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Just for your information:
* There is a merge request for solving this issue (i.e. determining the set of
suitable release names) without `lsb_release`:
https://github.com/munin-monitoring/munin/pull/1128.
* The related Debian issue is d#715141
I had a look in the Debian bug system for a matching bug but could not find
one.
The closest thing I could find was Bug#314610: munin-node: wrong regexp in
apt_all
I had a look in the Debian bug system for a matching bug but could not find
one.
The closest thing I could find was Bug#314610: munin-node: wrong regexp in
apt_all
OK, it has run overnight, and the update behavior is precisely what I
would expect (no cron spam). However, it is not drawing the graphs for
the number of pending packages (claiming it is missing a label). I need
to investigate this behavior a bit further.
--
You received this bug notification
OK, I have modified all the places that use the release name, and the
graph is being drawn, but the graphs look...strange. Not all of the
categories show up and those that do all report zero packages pending.
When telnet'ing to 4949 fetch apt_all reports the right info, so someone
with more
OK, it has run overnight, and the update behavior is precisely what I
would expect (no cron spam). However, it is not drawing the graphs for
the number of pending packages (claiming it is missing a label). I need
to investigate this behavior a bit further.
--
You received this bug notification
OK, I have modified all the places that use the release name, and the
graph is being drawn, but the graphs look...strange. Not all of the
categories show up and those that do all report zero packages pending.
When telnet'ing to 4949 fetch apt_all reports the right info, so someone
with more
Standby. In leaving this running overnight, it throws errors (or at
least warnings) if all categories are not actually enabled - as it turns
out, I haven't enabled -proposed on my firewalls. I need to rethink
the release determination mechanism slightly to account for this. One
more iteration
I have installed this on my test systems (mixture of Debian and Ubuntu),
and will post after this has run a few hours. There should be no
unexpected cron spam. If there isn't, I would request that the patch be
reviewed again and considered for inclusion in Ubuntu.
Clearly the fix part of this
Update patch:
1) Query potential releases with -t $release prior to updating status
** Patch added: Updated patch
https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1038044/+attachment/3267842/+files/apt_all.in.patch
--
You received this bug notification because you are a member of
Standby. In leaving this running overnight, it throws errors (or at
least warnings) if all categories are not actually enabled - as it turns
out, I haven't enabled -proposed on my firewalls. I need to rethink
the release determination mechanism slightly to account for this. One
more iteration
Update patch:
1) Query potential releases with -t $release prior to updating status
** Patch added: Updated patch
https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1038044/+attachment/3267842/+files/apt_all.in.patch
--
You received this bug notification because you are a member of
I have installed this on my test systems (mixture of Debian and Ubuntu),
and will post after this has run a few hours. There should be no
unexpected cron spam. If there isn't, I would request that the patch be
reviewed again and considered for inclusion in Ubuntu.
Clearly the fix part of this
Thanks for your patch!
You might want to handle the case where lsb_release is not installed/executable
and then fallback to the Debian default instead of exiting.
(I do not know if the dependency of lsb_release is fulfilled when installing
munin-node)
Apart from that the patch looks decent and
On 08/18/2012 04:34 PM, Daniel Hahler wrote:
Thanks for your patch!
You might want to handle the case where lsb_release is not
installed/executable and then fallback to the Debian default instead of
exiting.
(I do not know if the dependency of lsb_release is fulfilled when installing
Updated patch:
1) Include call to determine_releases() inside update_state() sub, as several
code paths need it
2) Default to Debian-specific behaviors if lsb_release is not Ubuntu (at
Daniel's suggestion)
** Patch added: Handle both Debian and Ubuntu for apt_all in munin-node
Thanks for your patch!
You might want to handle the case where lsb_release is not installed/executable
and then fallback to the Debian default instead of exiting.
(I do not know if the dependency of lsb_release is fulfilled when installing
munin-node)
Apart from that the patch looks decent and
On 08/18/2012 04:34 PM, Daniel Hahler wrote:
Thanks for your patch!
You might want to handle the case where lsb_release is not
installed/executable and then fallback to the Debian default instead of
exiting.
(I do not know if the dependency of lsb_release is fulfilled when installing
Updated patch:
1) Include call to determine_releases() inside update_state() sub, as several
code paths need it
2) Default to Debian-specific behaviors if lsb_release is not Ubuntu (at
Daniel's suggestion)
** Patch added: Handle both Debian and Ubuntu for apt_all in munin-node
I have checked the source for the versions in both 12.04 and Quantal and
I see the same behavior. I'm decent at Perl; I hope to be able to
submit a patch tonight.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in Ubuntu.
** Description changed:
/usr/share/munin/plugins/apt_all is hard-coded to look for releases
stable, testing, unstable which Ubuntu doesn't use. A very
- similar problem was reported before in LP#245031; is it possible that
+ similar problem was reported before in bug 245031; is it possible
The relevant patch appears to be: http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/karmic/munin/karmic/revision/15/debian/patches/221-apt-
ubuntu-changes.patch
I think that this should be generalized to work also with Debian by
default (and then incorporated there) or it needs to get added to
Here is a patch to discover the distributor and codename. It will work
for Debian and Ubuntu; it is my hope that this would be accepted
upstream.
** Patch added: Patch to discover distributor and determine releases for
apt_all munin plugin
The attachment Patch to discover distributor and determine releases for
apt_all munin plugin of this bug report has been identified as being a
patch. The ubuntu-reviewers team has been subscribed to the bug report
so that they can review the patch. In the event that this is in fact
not a patch
I have checked the source for the versions in both 12.04 and Quantal and
I see the same behavior. I'm decent at Perl; I hope to be able to
submit a patch tonight.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
/usr/share/munin/plugins/apt_all is hard-coded to look for releases
stable, testing, unstable which Ubuntu doesn't use. A very
- similar problem was reported before in LP#245031; is it possible that
+ similar problem was reported before in bug 245031; is it possible
The relevant patch appears to be: http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/karmic/munin/karmic/revision/15/debian/patches/221-apt-
ubuntu-changes.patch
I think that this should be generalized to work also with Debian by
default (and then incorporated there) or it needs to get added to
Here is a patch to discover the distributor and codename. It will work
for Debian and Ubuntu; it is my hope that this would be accepted
upstream.
** Patch added: Patch to discover distributor and determine releases for
apt_all munin plugin
The attachment Patch to discover distributor and determine releases for
apt_all munin plugin of this bug report has been identified as being a
patch. The ubuntu-reviewers team has been subscribed to the bug report
so that they can review the patch. In the event that this is in fact
not a patch
36 matches
Mail list logo
