* David Liontooth
> $ cat /etc/cron.d/munin-node
> #
> # cron-jobs for munin-node
> #
>
> MAILTO=root
>
> # If the APT plugin is enabled, update packages databases approx. once
> # an hour (12 invokations an hour, 1 in 12 chance that the update will
> # happen), but ensure that there will never be more than two hour (7200
> # seconds) interval between updates..
> */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then
> /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x
> /etc/munin/plugins/apt ]; t$
>
> This cronjob should not be activated if the apt / apt_all plugin is
> not enabled.
I think you've got a corrupted installation. This line should not end
with «t$», it should read:
*/5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12
>/dev/null; fi
Could you try replacing it with the above, or reinstalling, and see if
that helps? This job should never generate any output whatsoever if
the APT plugins are disabled.
> I like a quiet syslog and discovered the bug from getting crowds of
> these.
It's strange that you get it in your syslog, cron is supposed to mail
output to root as per the MAILTO setting (even errors resulting from
your corrupted file). Weird.
What is the error that ends up in your syslog, exactly? Could you
please paste an example?
> There are clearly some residual issues with munin and cron -- cf.
>
> #301361
> #353979
> #332285
> #382947
None of these are about the cronjob of the apt plugin, so they're not
related to the problem you're describing.
> That said, this works beautifully out of the box, so thanks for expert
> packaging.
Thanks. :-)
--
Tore Anderson
