Package: munin
Version: 2.0.6-4+deb7u1
Severity: important
Dear Maintainer,
I just found that munin-html don't display the services exceeded the critical
or warning limits correctely.
To reproduce, I use the hddtemp_smartctl plugin with warn forced in munin.conf
hddtemp_smartctl.sda.warning 22
hddtemp_smartctl.sda.critical 23
The limits are well detected by munin-limits :
# grep hddtemp_smartctl /var/lib/munin/limits
grenoble.cnrs.fr;vms.grenoble.cnrs.fr;hddtemp_smartctl;sda;critical Value is
26.00. Critical range (:23) exceeded
grenoble.cnrs.fr;vms.grenoble.cnrs.fr;hddtemp_smartctl;sda;state critical
grenoble.cnrs.fr;vms.grenoble.cnrs.fr;hddtemp_smartctl;sdb;critical Value is
25.00. Critical range (:23) exceeded
grenoble.cnrs.fr;vms.grenoble.cnrs.fr;hddtemp_smartctl;sdb;state critical
But in HTML, the level stay in normal, and the problems page is not refreshed.
Thanks !
-- System Information:
Debian Release: 7.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages munin depends on:
ii adduser 3.113+nmu3
ii cron 3.0pl1-124
ii libcgi-fast-perl 5.14.2-21
ii libdate-manip-perl 6.32-1
pn libdigest-md5-perl <none>
ii libfile-copy-recursive-perl 0.38-1
ii libhtml-template-perl 2.91-1
ii libio-socket-inet6-perl 2.69-2
ii liblog-log4perl-perl 1.29-1
ii librrds-perl 1.4.7-2
pn libstorable-perl <none>
ii liburi-perl 1.60-1
ii munin-common 2.0.6-4+deb7u1
ii perl [libtime-hires-perl] 5.14.2-21
ii perl-modules 5.14.2-21
ii rrdtool 1.4.7-2
ii ttf-dejavu 2.33-3
Versions of packages munin recommends:
pn munin-doc <none>
ii munin-node 2.0.6-4+deb7u1
Versions of packages munin suggests:
ii apache2-mpm-prefork [httpd] 2.2.22-13
pn libnet-ssleay-perl <none>
pn www-browser <none>
-- Configuration Files:
/etc/munin/apache.conf changed [not included]
/etc/munin/munin.conf changed [not included]
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]