Package: munin-node Version: 2.0.44-1 Severity: normal Dear Maintainer,
The 'df' plugin no longer reports on the size of the /home partition. This seems to be due to the "ProtectHome=true" setting in the munin-node.service for systemd. I think this behaviour started with the upgrade in testing from version 2.0.37-2 to 2.0.42-5. The effect can be observed by looking at the different output of 'munin-run df config' on one hand (which reports on /home, provided you have a separate /home partition :-) ), and on the other hand using telnet or nc to connect to the running munin-node instance and to ask for the config there: 'echo -e "config df\nquit\n" | nc localhost 4949' (which does not report /home). After changing the "ProtectHome" setting in munin-node.service to "read-only" (and restarting etc.) munin-node again reports on /home. I understand the reason for the ProtectHome=true setting for munin-node in general, but unfortunately this makes it impossible to monitor /home. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages munin-node depends on: ii libnet-server-perl 2.009-1 ii lsb-base 10.2018112800 ii munin-common 2.0.44-1 ii munin-plugins-core 2.0.44-1 ii perl 5.28.1-3 Versions of packages munin-node recommends: ii gawk 1:4.2.1+dfsg-1 ii munin-plugins-extra 2.0.44-1 ii procps 2:3.3.15-2 Versions of packages munin-node suggests: ii munin 2.0.44-1 pn munin-plugins-java <none>
