Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause: SELinux prevents logrotate to map its configuration file
Consequence: logrotate.service fails to start because it cannot map its configuration file in memory
Fix: Allow logrotate_t to map generic files in /etc
Result: logrotate.service is working
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (selinux-policy bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:6617
Description of problem: On a freshly installed MLS system, we can see logrotate.service unit failing: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- [root@vm-mls9 ~]# journalctl -b -u logrotate.service Aug 11 08:12:14 vm-mls9 systemd[1]: Starting Rotate log files... Aug 11 08:12:14 vm-mls9 logrotate[707]: error: Error mapping config file /etc/logrotate.conf: Permission denied Aug 11 08:12:14 vm-mls9 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE Aug 11 08:12:14 vm-mls9 systemd[1]: logrotate.service: Failed with result 'exit-code'. Aug 11 08:12:14 vm-mls9 systemd[1]: Failed to start Rotate log files. -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- This happens because it's not able to map its configuration file: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- type=PROCTITLE msg=audit(08/11/2023 08:12:14.244:13990) : proctitle=/usr/sbin/logrotate /etc/logrotate.conf type=SYSCALL msg=audit(08/11/2023 08:12:14.244:13990) : arch=x86_64 syscall=mmap success=no exit=EACCES(Permission denied) a0=0x0 a1=0x1f0 a2=PROT_READ a3=MAP_PRIVATE|MAP_POPULATE items=0 ppid=1 pid=707 auid=unset uid=root gid=root euid=root suid=root fsuid=root egid=root sgid=root fsgid=root tty=(none) ses=unset comm=logrotate exe=/usr/sbin/logrotate subj=system_u:system_r:logrotate_t:s0-s15:c0.c1023 key=(null) type=AVC msg=audit(08/11/2023 08:12:14.244:13990) : avc: denied { map } for pid=707 comm=logrotate path=/etc/logrotate.conf dev="dm-0" ino=33858546 scontext=system_u:system_r:logrotate_t:s0-s15:c0.c1023 tcontext=system_u:object_r:etc_t:s0 tclass=file permissive=0 -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Version-Release number of selected component (if applicable): selinux-policy-mls-38.1.11-2.el9_2.3.noarch How reproducible: Always Steps to Reproduce: 1. Start logrotate.service unit Actual results: Failure Expected results: No failure