Yes that looks like the same problem. I did an update yesterday and
there was no selinux update, but there was one today. This fixed my
problem.
Paolo
On 10/1/20 12:56 PM, Jonathan Billings wrote:
On Thu, Oct 01, 2020 at 11:53:00AM -0700, Paolo Galtieri wrote:
> Folks,
> since August 13 my backups have failed to run due the following errors:
>
> Oct 1 11:10:01 terrapin CROND[110219]: (root) CMD
> (/usr/local/bro/bin/zeekctl cron)
> Oct 1 11:12:01 terrapin crond[1565]: ((null)) No SELinux security context
> (/etc/crontab)
> Oct 1 11:12:01 terrapin crond[1565]: (root) FAILED (loading cron table)
> Oct 1 11:12:01 terrapin crond[1565]: ((null)) No SELinux security context
> (/etc/cron.d/0hourly)
> Oct 1 11:12:01 terrapin crond[1565]: (root) FAILED (loading cron table)
> Oct 1 11:12:01 terrapin crond[1565]: ((null)) No SELinux security context
> (/etc/cron.d/sbackup)
> Oct 1 11:12:01 terrapin crond[1565]: (root) FAILED (loading cron table)
Is your issue related to this BZ?
https://bugzilla.redhat.com/show_bug.cgi?id=1862823
If so, it appears there's an issue with the selinux policy on your
system.