Your message dated Fri, 1 Mar 2019 03:29:07 +0100
with message-id <[email protected]>
and subject line Fixed in 2.0.27-1
has caused the Debian Bug report #698302,
regarding munin_stats: wrong values for munin graph
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
698302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698302
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: munin-plugins-core
Version: 2.0.6-3
Severity: normal
Dear Maintainer,
after upgrading from squeeze to wheezy the munin_stats plugin
provides wrong values for the "munin graph" time (only a fraction
of a second) while I can see the munin-graph process running for
about half a minute when I watch processes with e.g. top.
A graph which shows munin processing times before and after the
upgrade to wheezy is attached.
Regards
Uwe
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages munin-plugins-core depends on:
ii munin-common 2.0.6-3
ii perl 5.14.2-16
Versions of packages munin-plugins-core recommends:
ii libnet-snmp-perl 6.0.1-2
Versions of packages munin-plugins-core suggests:
pn libnet-netmask-perl <none>
ii libnet-telnet-perl 3.03-3
ii python 2.7.3~rc2-1
ii ruby 4.9
ii ruby1.8 [ruby-interpreter] 1.8.7.358-6
ii ruby1.9.1 [ruby-interpreter] 1.9.3.194-5
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.0.27-1
Hello,
it seems that the issue was fixed in 2.0.27-1.
Cheers,
Lars
--- End Message ---
