Munin not updating
In the following article we will show you how to install Munin on a Cent OS 6 VPS so you can monitor your virtual servers resource usage.Munin is a networked resource monitoring tool that can help analyze resource usage of servers and services.It has a master/slave architecture in which the master connects to all the slaves at regular intervals and asks them for data.It is written in perl and is very fast and robust monitoring tool.
This also applies to 2.0.14-1~bpo70 1 and 2.0.16 seems to contain this too.It would be nice to replace this with something like this: Hi, I've applied the proposed solution (using $ENV) but ran into an unsuspected issue: munin-node package creates a cron jobs file ("/etc/cron.d/munin-node") where it directly runs the apt_all plugin, as an executable script, not through Munin's system (like `munin-run` would), thus not taking munin-node configuration into account. The extra $ARGV will be transparently given to the plugin, as the "config" or "update" is already./dev/null; fi My naive attempt to fix this was to replace direct `/etc/munin/plugins/apt_all update 7200 12` calls with a `munin-run apt_all update 7200 12` But sadly munin-run don't push the extra "7200" and "12" parameters to the apt_all, which in turns only has "update" in it's $ARGV and sees it as an error and display the helping usage text: But sadly munin-run don't push the extra "7200" and "12" parameters to the apt_all Looking closely, that was done specifically like that. which in turns only has "update" in it's $ARGV and sees it as an error and display the helping usage text: Another way to fix this bug is to add additional configuration: [apt_all] user root Because the update is performed as root by the cronjob, the plugin statefile is written to /var/lib/munin-node/plugin-state/root/plugin-apt.state.Without this configuration item, munin_run would look in /var/lib/munin-node/plugin-state/nobody/plugin-apt.state By default, there is only an entry for the 'apt' plugin, so 'apt_full' was missing.Well, as it's an upstream issue, it will be solved upstream :) Has already been anything done to fix it?I also got a bunch of servers, that update only if I work around it manually, as #720275 broke the cronjob by introducing munin-run to run them.If you'd like I can try to prepare a pull request for merging upstream.Kind regards, Andre -- Andre Klärner Package: munin-plugins-core Version: 2.0.25-1 deb8u2 Followup-For: Bug #715141 Hi, This issue just appeared on my Jessie stable in one of the recent update of the package through unattended-upgrades.For now I've worked around by manually editing the apt_all script to change my @releases = ("stable") and using dpkg-divert to avoid subsequent updates to nuke the change... What fix can be expected for jessie concerning this issue?Regards Marc -- System Information: Debian Release: 8.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US. UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages munin-plugins-core depends on: ii munin-common 2.0.25-1 deb8u2 ii perl 5.20.2-3 deb8u6 Versions of packages munin-plugins-core recommends: ii libnet-snmp-perl 6.0.1-2 Versions of packages munin-plugins-core suggests: ii conntrack 1:1.4.2-2 deb8u1 ii libcache-cache-perl 1.07-2 ii libdbd-mysql-perl 4.028-2 deb8u2 ii libnet-dns-perl 0.81-2 deb8u1 pn libnet-netmask-perl .Last modified: Sat Mar 3 2018; Machine Name: beach Debian Bug tracking system Debbugs is free software and licensed under the terms of the GNU Public License version 2.