Hide Forgot
SELinux is preventing /usr/libexec/mysqld from 'unlink' accesses on the sock_file mysql.sock. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that mysqld should be allowed unlink access on the mysql.sock sock_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 mysqld /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:mysqld_t:s0 Target Context system_u:object_r:tmp_t:s0 Target Objects mysql.sock [ sock_file ] Source mysqld Source Path /usr/libexec/mysqld Port <Unknown> Host (removed) Source RPM Packages mysql-server-5.5.10-2.fc15 Target RPM Packages Policy RPM selinux-policy-3.9.16-23.fc15 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 2.6.38.6-26.rc1.fc15.x86_64 #1 SMP Mon May 9 20:45:15 UTC 2011 x86_64 x86_64 Alert Count 10 First Seen Sun 15 May 2011 09:04:00 PM PDT Last Seen Mon 16 May 2011 08:07:10 AM PDT Local ID 2e09f538-b2a6-4ef5-b56e-a80cef51763b Raw Audit Messages type=AVC msg=audit(1305558430.153:70): avc: denied { unlink } for pid=2518 comm="mysqld" name="mysql.sock" dev=dm-1 ino=2254 scontext=system_u:system_r:mysqld_t:s0 tcontext=system_u:object_r:tmp_t:s0 tclass=sock_file type=SYSCALL msg=audit(1305558430.153:70): arch=x86_64 syscall=unlink success=no exit=EACCES a0=7fff66a3ef71 a1=2 a2=0 a3=7f723c23ed50 items=0 ppid=1146 pid=2518 auid=4294967295 uid=27 gid=27 euid=27 suid=27 fsuid=27 egid=27 sgid=27 fsgid=27 tty=(none) ses=4294967295 comm=mysqld exe=/usr/libexec/mysqld subj=system_u:system_r:mysqld_t:s0 key=(null) Hash: mysqld,mysqld_t,tmp_t,sock_file,unlink audit2allow #============= mysqld_t ============== allow mysqld_t tmp_t:sock_file unlink; audit2allow -R #============= mysqld_t ============== allow mysqld_t tmp_t:sock_file unlink;
It looks like a local modification. Did you change the path for "mysql.sock"?
Yes, I had changed it to /tmp/mysql.sock, which I thought shouldn't have permissions issues with SELinux. Sorry for the false alarm.
We don't want to allow daemons to use /tmp dir. This dir is for users. sock/pid files should be located in the /var/run directory.