SELinux is preventing /bin/systemctl from 'write' accesses on the sock_file private. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that systemctl should be allowed write access on the private 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 telinit /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:prelink_cron_system_t:s0-s0:c0.c 1023 Target Context system_u:object_r:tmpfs_t:s0 Target Objects private [ sock_file ] Source telinit Source Path /bin/systemctl Port <Unknown> Host (removed) Source RPM Packages systemd-units-21-2.fc15 Target RPM Packages Policy RPM selinux-policy-3.9.16-6.fc15 Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 2.6.38.2-9.fc15.x86_64 #1 SMP Wed Mar 30 16:55:57 UTC 2011 x86_64 x86_64 Alert Count 1 First Seen Thu 31 Mar 2011 11:32:20 AM CEST Last Seen Thu 31 Mar 2011 11:32:20 AM CEST Local ID bcdea526-f820-4dc4-884a-a9494ddf51bd Raw Audit Messages type=AVC msg=audit(1301563940.418:192): avc: denied { write } for pid=27756 comm="telinit" name="private" dev=tmpfs ino=9013 scontext=system_u:system_r:prelink_cron_system_t:s0-s0:c0.c1023 tcontext=system_u:object_r:tmpfs_t:s0 tclass=sock_file type=SYSCALL msg=audit(1301563940.418:192): arch=x86_64 syscall=connect success=yes exit=0 a0=3 a1=7fff0deb1450 a2=16 a3=0 items=0 ppid=26322 pid=27756 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=2 comm=telinit exe=/bin/systemctl subj=system_u:system_r:prelink_cron_system_t:s0-s0:c0.c1023 key=(null) Hash: telinit,prelink_cron_system_t,tmpfs_t,sock_file,write audit2allow #============= prelink_cron_system_t ============== allow prelink_cron_system_t tmpfs_t:sock_file write; audit2allow -R #============= prelink_cron_system_t ============== allow prelink_cron_system_t tmpfs_t:sock_file write;
*** This bug has been marked as a duplicate of bug 692436 ***
This morning i checked my logs and still see: SELinux is preventing /bin/systemctl from write access on the sock_file private Dec 25 03:18:08 zeus setroubleshoot: SELinux is preventing /bin/systemctl from write access on the sock_file private. For complete SELinux messages. run sealert -l 2f223120-aa91-4956-b83e-4b99f7bc1066 [root@zeus log]# sealert -l 2f223120-aa91-4956-b83e-4b99f7bc1066 SELinux is preventing /bin/systemctl from write access on the sock_file private. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that systemctl should be allowed write access on the private 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 systemctl /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp [root@zeus log]# grep systemctl /var/log/audit/audit.log type=AVC msg=audit(1324779485.708:1797): avc: denied { write } for pid=27830 comm="systemctl" name="private" dev=tmpfs ino=10351 scontext=system_u:system_r:logrotate_t:s0-s0:c0.c1023 tcontext=system_u:object_r:init_var_run_t:s0 tclass=sock_file type=SYSCALL msg=audit(1324779485.708:1797): arch=c000003e syscall=42 success=no exit=-13 a0=3 a1=7fffebbb98e0 a2=16 a3=0 items=0 ppid=27829 pid=27830 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=173 comm="systemctl" exe="/bin/systemctl" subj=system_u:system_r:logrotate_t:s0-s0:c0.c1023 key=(null)
Eddie, could you open a new bug for this?