Bug 726562 - SELinux is preventing /usr/sbin/squid from 'read' accesses on the arquivo squid.pid.
Summary: SELinux is preventing /usr/sbin/squid from 'read' accesses on the arquivo squ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 15
Hardware: i386
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: setroubleshoot_trace_hash:0c7da441fae...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-29 02:08 UTC by rodrigoatique
Modified: 2012-03-05 04:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-29 06:47:36 UTC
Type: ---


Attachments (Terms of Use)

Description rodrigoatique 2011-07-29 02:08:05 UTC
SELinux is preventing /usr/sbin/squid from 'read' accesses on the arquivo squid.pid.

*****  Plugin catchall (100. confidence) suggests  ***************************

If you believe that squid should be allowed read access on the squid.pid file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep squid /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:squid_t:s0
Target Context                unconfined_u:object_r:var_run_t:s0
Target Objects                squid.pid [ file ]
Source                        squid
Source Path                   /usr/sbin/squid
Port                          <Desconhecido>
Host                          (removed)
Source RPM Packages           squid-3.1.12-2.fc15
Target RPM Packages           
Policy RPM                    selinux-policy-3.9.16-30.fc15
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 2.6.38.6-26.rc1.fc15.i686.PAE #1
                              SMP Mon May 9 20:36:50 UTC 2011 i686 i686
Alert Count                   8
First Seen                    Sáb 16 Jul 2011 20:03:21 BRT
Last Seen                     Sáb 16 Jul 2011 20:12:18 BRT
Local ID                      769c3036-6acd-44ce-8c00-182b61052d57

Raw Audit Messages
type=AVC msg=audit(1310857938.752:136): avc:  denied  { read } for  pid=4668 comm="squid" name="squid.pid" dev=tmpfs ino=65981 scontext=system_u:system_r:squid_t:s0 tcontext=unconfined_u:object_r:var_run_t:s0 tclass=file


type=SYSCALL msg=audit(1310857938.752:136): arch=i386 syscall=open success=no exit=EACCES a0=22822c20 a1=8000 a2=1b6 a3=0 items=0 ppid=4658 pid=4668 auid=4294967295 uid=0 gid=23 euid=0 suid=0 fsuid=0 egid=23 sgid=23 fsgid=23 tty=(none) ses=4294967295 comm=squid exe=/usr/sbin/squid subj=system_u:system_r:squid_t:s0 key=(null)

Hash: squid,squid_t,var_run_t,file,read

audit2allow

#============= squid_t ==============
allow squid_t var_run_t:file read;

audit2allow -R

#============= squid_t ==============
allow squid_t var_run_t:file read;

Comment 1 Miroslav Grepl 2011-07-29 06:47:36 UTC
Have you ever started squid without using the service script. It looks so.

# restorecon -R -v /var/log/squid*

will fix it.


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