Re: (root) FAILED (loading cron table)
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. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: (root) FAILED (loading cron table)
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. -- Jonathan Billings ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
(root) FAILED (loading cron table)
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)
ls -lZ /etc/cron.d/sbackup
-rw-r--r--. 1 root root unconfined_u:object_r:system_cron_spool_t:s0 76
Oct 1 11:11 /etc/cron.d/sbackup
ls -lZ /etc/cron.d/0hourly
-rw-r--r--. 1 root root system_u:object_r:system_cron_spool_t:s0 128 Jul
24 2019 /etc/cron.d/0hourly
ls -lZ /etc/crontab
-rw-r--r--. 1 root root system_u:object_r:system_cron_spool_t:s0 451 Jul
24 2019 /etc/crontab
ls -lZ /usr/sbin/sbackupd
-rwxr-xr-x. 1 root root system_u:object_r:usr_t:s0 21024 Apr 29 08:53
/usr/sbin/sbackupd*
I ran:
sudo sesearch -A -s unconfined_t -t user_cron_spool_t -c file
allow application_domain_type user_cron_spool_t:file { append getattr
ioctl lock read write };
allow crontab_domain user_cron_spool_t:file { append create getattr
ioctl link lock open read rename setattr unlink write };
allow domain file_type:file map; [ domain_can_mmap_files ]:True
allow files_unconfined_type file_type:file execmod; [
selinuxuser_execmod ]:True
allow files_unconfined_type file_type:file { append audit_access create
execute execute_no_trans getattr ioctl link lock map mounton open
quotaon read relabelfrom relabelto rename setattr swapon unlink write };
allow unconfined_t user_cron_spool_t:file entrypoint; [
cron_userdomain_transition ]:True
allow unconfined_t user_cron_spool_t:file { getattr ioctl read write };
This made no difference, my backups still don't run. The last backup
ran Aug 13.
What do I need to change to get my backups to start running
automatically again?
Paolo
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
