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.
commit 63630b1ced49d0b4bb2a0a6a7c7ef3affbe53e9b
Author: Miroslav Grepl <mgrepl>
Date: Mon Oct 6 13:57:32 2014 +0200
radiusd wants to write own log files.
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, 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://rhn.redhat.com/errata/RHBA-2015-0458.html
Description of problem: selinux doesn't allow write for radiusd to /var/log/radius [test]ausearch -m avc -ts recent -i ---- type=SYSCALL msg=audit(09/25/2014 04:46:16.187:854) : arch=ppc64 syscall=open success=no exit=-13(Permission denied) a0=0x3fff8024b9c8 a1=O_WRONLY|O_CREAT a2=0600 a3=0x0 items=0 ppid=1 pid=6465 auid=unset uid=radiusd gid=radiusd euid=radiusd suid=radiusd fsuid=radiusd egid=radiusd sgid=radiusd fsgid=radiusd tty=(none) ses=unset comm=radiusd exe=/usr/sbin/radiusd subj=system_u:system_r:radiusd_t:s0 key=(null) type=AVC msg=audit(09/25/2014 04:46:16.187:854) : avc: denied { write } for pid=6465 comm=radiusd path=/var/log/radius/radacct/127.0.0.1/detail-20140925 dev="dm-1" ino=102396278 scontext=system_u:system_r:radiusd_t:s0 tcontext=system_u:object_r:radiusd_log_t:s0 tclass=file [test]sesearch -s radiusd_t -t radiusd_log_t -c file -AC Found 2 semantic av rules: allow daemon logfile : file { ioctl getattr lock append } ; allow radiusd_t radiusd_log_t : file { ioctl create getattr setattr lock append open } ; Version-Release number of selected component (if applicable): freeradius-3.0.4-1.el7 selinux-policy-3.12.1-153.el7_0.10 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: