munin comes with a cronjob that runs every 5 minutes as user munin:

    */5 * * * *     munin test -x /usr/bin/munin-cron && /usr/bin/munin-cron

Unfortunately this cronjobs triggers logtail segfaults every time it runs (and spams /var/log/messages while doing so) - see bug 1215399 for the logtail part of this bug.


On the munin side, the problem is:

/usr/lib/munin/plugins/amavis calls
    logtail /etc/hosts
which then segfaults because it can't write /etc/hosts.offset. (You can reproduce this by manually running   logtail /etc/hosts   as non-root.)


The fix is to specify a writeable path for the offset file:

--- /usr/lib/munin/plugins/amavis_ORIG  2023-09-15 21:49:38.926514309 +0200
+++ /usr/lib/munin/plugins/amavis       2023-09-15 21:50:45.762436708 +0200
@@ -77,6 +77,7 @@
 AMAVIS_LOG=${amavislog:-/var/log/mail/mail.info}
 LOGTAIL=${logtail:-logtail}
 STATEFILE=$MUNIN_PLUGSTATE/amavis.offset
+HOSTS_STATEFILE=$MUNIN_PLUGSTATE/amavis-hosts.offset

 if [ "$1" = "autoconf" ]; then
        if [ -f "${AMAVIS_LOG}" ] && [ -n "${LOGTAIL}" ] && [ -x "${LOGTAIL}" ] ; then
@@ -90,7 +91,7 @@

 # Try tailing a random file to check how arguments are passed
 ARGS=0
-"$LOGTAIL" /etc/hosts 2>/dev/null >/dev/null
+"$LOGTAIL" /etc/hosts "$HOSTS_STATEFILE" 2>/dev/null >/dev/null
 if [ $? = 66 ]; then
     if [ -z "$logtail" ]; then
        ARGS=1



/usr/lib/munin/plugins/courier_ and /usr/lib/munin/plugins/perdition also contain
    "$LOGTAIL" /etc/hosts 2>/dev/null >/dev/null
and will need a similar patch.


This bug is a regression in Leap 15.5.
On Leap 15.4, I didn't see these segfaults (maybe the old munin package didn't have the "logtail /etc/hosts" calls?)