Bug 1645300 - crond will not run after upgrade to F29
Summary: crond will not run after upgrade to F29
Keywords:
Status: CLOSED DUPLICATE of bug 1639381
Alias: None
Product: Fedora
Classification: Fedora
Component: cronie
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-01 21:02 UTC by Ferry Huberts
Modified: 2018-11-02 07:18 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-11-02 07:18:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ferry Huberts 2018-11-01 21:02:40 UTC
Description of problem:
Upgraded one of my machines to Fedora 29 yesterday.
Now crond will not run


Version-Release number of selected component (if applicable):
cronie-1.5.2-2.fc29.x86_64
crontabs-1.11-17.20150630git.fc29.noarch
cronie-anacron-1.5.2-2.fc29.x86_64


How reproducible:
always

Steps to Reproduce:
1. upgrade my working F28 machine to F29 with dnf
2.
3.

Actual results:

# journalctl -u crond  -r
Nov 01 21:52:32 storage.internal.hupie.com crond[2037]: (CRON) INFO (@reboot jobs will be run at computer's startup.)
Nov 01 21:52:32 storage.internal.hupie.com crond[2037]: (CRON) INFO (running with inotify support)
Nov 01 21:52:32 storage.internal.hupie.com crond[2037]: (root) FAILED (loading cron table)
Nov 01 21:52:32 storage.internal.hupie.com crond[2037]: ((null)) Unauthorized SELinux context=system_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 file_context=system_u:object_r:system_cron_spool_t:s0 (/etc/cron.d/raid-check)
Nov 01 21:52:32 storage.internal.hupie.com crond[2037]: (root) FAILED (loading cron table)
Nov 01 21:52:32 storage.internal.hupie.com crond[2037]: ((null)) Unauthorized SELinux context=system_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 file_context=system_u:object_r:system_cron_spool_t:s0 (/etc/cron.d/0hourly)
Nov 01 21:52:32 storage.internal.hupie.com crond[2037]: (root) FAILED (loading cron table)
Nov 01 21:52:32 storage.internal.hupie.com crond[2037]: ((null)) Unauthorized SELinux context=system_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 file_context=system_u:object_r:system_cron_spool_t:s0 (/etc/crontab)
Nov 01 21:52:32 storage.internal.hupie.com crond[2037]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 81% if used.)
Nov 01 21:52:32 storage.internal.hupie.com crond[2037]: (CRON) STARTUP (1.5.2)



# ls -lahZ /etc/crontab /etc/cron.d/0hourly /etc/cron.d/raid-check
-rw-r--r--. 1 root root system_u:object_r:system_cron_spool_t:s0 128 Jul 13 02:07 /etc/cron.d/0hourly
-rw-r--r--. 1 root root system_u:object_r:system_cron_spool_t:s0 108 Sep 14 00:51 /etc/cron.d/raid-check
-rw-r--r--. 1 root root system_u:object_r:system_cron_spool_t:s0 451 Jul 13 02:07 /etc/crontab

Comment 1 Tomas Mraz 2018-11-02 07:18:55 UTC

*** This bug has been marked as a duplicate of bug 1639381 ***


Note You need to log in before you can comment on or make changes to this bug.