Hide Forgot
Description of problem: SELinux is preventing /sbin/killall5 from getattr access on the file /var/lib/boinc/projects/www.worldcommunitygrid.org/wcg_hpf2_rosetta_6.40_i686-pc-linux-gnu. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that killall5 should be allowed getattr access on the wcg_hpf2_rosetta_6.40_i686-pc-linux-gnu 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 pidof /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Contesto della sorgente system_u:system_r:xdm_t:s0-s0:c0.c1023 Contesto target system_u:object_r:boinc_project_var_lib_t:s0 Oggetti target /var/lib/boinc/projects/www.worldcommunitygrid.org /wcg_hpf2_rosetta_6.40_i686-pc-linux-gnu [ file ] Sorgente pidof Source path /sbin/killall5 Port <Sconosciuto> Host Magic-4 RPM package source sysvinit-tools-2.88-5.dsf.fc16 Pacchetti RPM target RPM della policy selinux-policy-3.10.0-64.fc16 Selinux abilitato True Tipo di policy targeted Enforcing mode Permissive Host Name Magic-4 Platform Linux Magic-4 3.1.4-1.fc16.x86_64 #1 SMP Tue Nov 29 11:37:53 UTC 2011 x86_64 x86_64 Warning count 14 First seen ven 25 nov 2011 10:01:47 CET Last seen gio 08 dic 2011 10:26:51 CET Messaggi Raw Audit type=AVC msg=audit(1323336411.21:68): avc: denied { getattr } for pid=1418 comm="pidof" path="/var/lib/boinc/projects/www.worldcommunitygrid.org/wcg_hpf2_rosetta_6.40_i686-pc-linux-gnu" dev=sdd1 ino=3014863 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:boinc_project_var_lib_t:s0 tclass=file type=SYSCALL msg=audit(1323336411.21:68): arch=x86_64 syscall=stat success=yes exit=0 a0=7fff31d76c00 a1=7fff31d76b60 a2=7fff31d76b60 a3=0 items=0 ppid=1415 pid=1418 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=pidof exe=/sbin/killall5 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null) Hash: pidof,xdm_t,boinc_project_var_lib_t,file,getattr audit2allow #============= xdm_t ============== allow xdm_t boinc_project_var_lib_t:file getattr; audit2allow -R #============= xdm_t ============== allow xdm_t boinc_project_var_lib_t:file getattr; Comments: I am wordless, BOINC is the only software I have that still has problems with SELinux. I know it is not only SELinux's fault, but also BOINC developers have their part of negligence (I remember once I read "it is not our problem" or something else in #boinc chan). What should I do? To complete abandon SELinux or there is a possibility that one day they could work together?
what does # ps -eZ |grep xdm if you run this project using BOINC.
system_u:system_r:xdm_t:s0-s0:c0.c1023 1392 ? 00:00:00 kdm system_u:system_r:xdm_t:s0-s0:c0.c1023 1406 ? 00:00:00 kdm
Obviously when I entered this command the working unit of wcg_hpf2_rosetta_6.40_i686-pc-linux-gnu was ended. Now it is running "Go fight against malaria" from WCG project
Yes, I would like to see an output of this command while "wcg_hpf2_rosetta_6.40_i686-pc-linux-gnu" is running.
The "SELinux is preventing /sbin/killall5 from getattr access" is showing on many BOINC projects, not only minirosetta... I get it also on malariacontrol. There are also a lot of other errors that are triggered by BOINC projects (the last one seems SElinux is preventing milkyway@home for searching the home directory). I think I've already applied 5 or 6 local policies to stop SEalert popping out, only for BOINC... I think it would be better focusing on a BOINC wide SElinux policy, better than single project policies, I don't know if this would require a better programming by BOINC admins or coordination between BOINC and SElinux.
# ps -eZ |grep xdm system_u:system_r:xdm_t:s0-s0:c0.c1023 1442 ? 00:00:00 kdm system_u:system_r:xdm_t:s0-s0:c0.c1023 1456 ? 00:00:00 kdm and a just had (see under) SELinux is preventing /sbin/killall5 from getattr access on the file /var/lib/boinc/projects/www.worldcommunitygrid.org/wcg_hpf2_rosetta_6.40_i686-pc-linux-gnu. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that killall5 should be allowed getattr access on the wcg_hpf2_rosetta_6.40_i686-pc-linux-gnu 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 pidof /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Contesto della sorgente system_u:system_r:xdm_t:s0-s0:c0.c1023 Contesto target system_u:object_r:boinc_project_var_lib_t:s0 Oggetti target /var/lib/boinc/projects/www.worldcommunitygrid.org /wcg_hpf2_rosetta_6.40_i686-pc-linux-gnu [ file ] Sorgente pidof Percorso della sorgente /sbin/killall5 Porta <Sconosciuto> Host Magic-4 Sorgente Pacchetti RPM sysvinit-tools-2.88-5.dsf.fc16 Pacchetti RPM target RPM della policy selinux-policy-3.10.0-64.fc16 Selinux abilitato True Tipo di policy targeted Modalità Enforcing Permissive Host Name removed Piattaforma Linux Magic-4 3.1.4-1.fc16.x86_64 #1 SMP Tue Nov 29 11:37:53 UTC 2011 x86_64 x86_64 Conteggio avvisi 1 Primo visto sab 10 dic 2011 20:29:17 CET Ultimo visto sab 10 dic 2011 20:29:17 CET Messaggi Raw Audit type=AVC msg=audit(1323545357.441:68): avc: denied { getattr } for pid=1470 comm="pidof" path="/var/lib/boinc/projects/www.worldcommunitygrid.org/wcg_hpf2_rosetta_6.40_i686-pc-linux-gnu" dev=sdd1 ino=3014863 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:boinc_project_var_lib_t:s0 tclass=file type=SYSCALL msg=audit(1323545357.441:68): arch=x86_64 syscall=stat success=yes exit=0 a0=7fffcae4a040 a1=7fffcae49fa0 a2=7fffcae49fa0 a3=0 items=0 ppid=1467 pid=1470 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=pidof exe=/sbin/killall5 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null) Hash: pidof,xdm_t,boinc_project_var_lib_t,file,getattr audit2allow #============= xdm_t ============== allow xdm_t boinc_project_var_lib_t:file getattr; audit2allow -R #============= xdm_t ============== allow xdm_t boinc_project_var_lib_t:file getattr; The kill all command I can see inside this report, could be related to a my # /etc/init.d/boinc-client restart ??? I need to excecute this command everytime I start the computer because BOINC loads itself before nVidia drivers, so it does not find a proper driver to use nVidia CUDA. So restarting BOINC I make it work well with the GPU. Note that Rosetta has nothing to do with GPU, I use GPU for Einstein@home project. P.S. could you please remove my hostname inside my other posts in this bugreport? I did not notice them before. Thank you very much
So does it happen repeatedly?
Yes it continues to happen
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.