Bug 177383 - selinux targeted policy denied syslogd
selinux targeted policy denied syslogd
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: selinux-policy-targeted (Show other bugs)
4.0
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-01-10 02:28 EST by Peter (Zebar) Astakhov
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-01-10 08:21:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Peter (Zebar) Astakhov 2006-01-10 02:28:25 EST
Description of problem:
AMD x86_64

[root@server ~]# rpm -qa | grep  selinux
libselinux-1.19.1-7
selinux-policy-targeted-1.17.30-2.110
libselinux-1.19.1-7

sysklogd-1.4.1-26_EL

If selinux enabled, syslog would not started, file /var/log/messages could not
contained any log messages.

dmesg said:
audit(1136866053.787:2): avc:  denied  { read } for  pid=2070 comm="syslogd"
name="syslog.conf" dev=sda2 ino=1022275 scontext=user_u:system_r:syslogd_t
tcontext=system_u:object_r:var_log_t tclass=file

Workaround:
Change in file /etc/selinux/targeted/booleans syslogd_disable_trans from 0 to 1.
Comment 1 Daniel Walsh 2006-01-10 08:21:33 EST
Why is /etc/syslog.conf labeled var_log_t?

restorecon /etc/syslog.conf  should fix the problem.

Did you cp syslog.conf from /var/log?

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