Follow Up to Munin Cron Error

[curtiser]

I am following up on another closed topic but I can’t post there.

Munin cron error daily at 03:32

Since upgrading to v62, I’ve been getting an error from a munin cron job. More specifically, this one that runs at 03:32: `32 03 * * * www-data cgitmpdir=$({ cat /etc/munin/munin.conf /etc/munin/munin-conf.d/* 2>/dev/null || true; } | sed -nE 's/^\s*cgitmpdir\s+(\S.*)$/\1/p' | tail -1); cgitmpdir=${cgitmpdir:-/var/lib/munin/cgi-tmp}; if [ -d "$cgitmpdir" ]; then find "$cgitmpdir/" -type f -mtime +1 -delete; find "$cgitmpdir/" -mindepth 1 -type d -empty -delete; fi` It looks like it’s runni…

find: cannot delete ‘/var/lib/munin/cgi-tmp/munin-cgi-graph/example.com/mail.example.com’: Permission denied

I checked /var/lib/munin is owned by munin:munin.

/var/lib/munin is owned by munin:www-data with 775, and its subdirectory munin-cgi-graph is owned by munin:munin with 775.

Do I need to change /var/lib/munin and its subdirectories to munin:www-data?

Thanks.
Curtis

[darond]

If it’s any consolation I am getting the same error on a daily basis but unable to resolve either.

I have renamed the directory that the cron job appears to be trying to delete on the basis it’s labelled as a ‘tmp’ parent directory. Munin monitoring appears to continue to be operating as normal.

I will see if I get another report overnight of a failure.

[darond]

Update; cron job reported failure again but against the renamed directory.

Will now delete the renamed directory and see what gets reported tomorrow