Package: munin-node
Version: 2.0.6-4
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
dist-upgrade from debian 6 to 7 thus munin upgrade from 1.4.x to 2.0.x
* What exactly did you do (or not do) that was effective (or
ineffective)?
deleting rdm-files to reset graph, did not work
guessing whatever fw_conntrack reads has changed
* What was the outcome of this action?
fw_conntrack shows cumulative graph
* What outcome did you expect instead?
fw_conntrack showing correct graph
*** End of the template - remove these lines ***
-- System Information:
Debian Release: 7.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages munin-node depends on:
ii adduser 3.113+nmu3
ii gawk 1:4.0.1+dfsg-2.1
ii libnet-server-perl 2.006-1
ii lsb-base 4.1+Debian8
ii munin-common 2.0.6-4
ii munin-plugins-core 2.0.6-4
ii perl 5.14.2-21
ii procps 1:3.3.3-3
Versions of packages munin-node recommends:
ii libnet-snmp-perl 6.0.1-2
ii munin-plugins-extra 2.0.6-4
Versions of packages munin-node suggests:
ii acpi 1.6-1
pn ethtool <none>
pn hdparm <none>
ii libcache-cache-perl 1.06-2
pn libcrypt-ssleay-perl <none>
ii libdbd-mysql-perl 4.021-1+b1
pn libdbd-pg-perl <none>
pn liblwp-useragent-determined-perl <none>
pn libnet-irc-perl <none>
pn libtext-csv-xs-perl <none>
ii libwww-perl 6.04-1
pn libxml-simple-perl <none>
ii lm-sensors 1:3.3.2-2
pn logtail <none>
ii munin 2.0.6-4
pn munin-plugins-java <none>
ii mysql-client-5.5 [mysql-client] 5.5.31+dfsg-0+wheezy1
ii net-tools 1.60-24.2
ii python 2.7.3-4
pn ruby <none>
pn smartmontools <none>
-- Configuration Files:
/etc/munin/plugin-conf.d/munin-node [Errno 13] Keine Berechtigung:
u'/etc/munin/plugin-conf.d/munin-node'
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
