Description of problem: start riak SELinux is preventing /usr/lib64/erlang/erts-5.10.1/bin/beam.smp from 'write' accesses on the directory riak. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that beam.smp should be allowed write access on the riak directory 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 beam.smp /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:rabbitmq_beam_t:s0 Target Context system_u:object_r:var_log_t:s0 Target Objects riak [ dir ] Source beam.smp Source Path /usr/lib64/erlang/erts-5.10.1/bin/beam.smp Port <Unknown> Host (removed) Source RPM Packages erlang-erts-R16B-0.3.fc19.x86_64 Target RPM Packages Policy RPM selinux-policy-3.12.1-63.fc19.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.9.9-301.fc19.x86_64 #1 SMP Thu Jul 4 15:10:36 UTC 2013 x86_64 x86_64 Alert Count 46 First Seen 2013-07-13 02:01:46 EDT Last Seen 2013-07-13 02:01:48 EDT Local ID 0dc0577e-f33d-4bc2-8f06-f84f0827928d Raw Audit Messages type=AVC msg=audit(1373695308.844:950): avc: denied { write } for pid=5986 comm="beam.smp" name="riak" dev="dm-2" ino=1318982 scontext=system_u:system_r:rabbitmq_beam_t:s0 tcontext=system_u:object_r:var_log_t:s0 tclass=dir type=SYSCALL msg=audit(1373695308.844:950): arch=x86_64 syscall=open success=no exit=EACCES a0=7fc029743bc0 a1=241 a2=1a0 a3=676f6c2f7261762f items=0 ppid=5808 pid=5986 auid=4294967295 uid=989 gid=988 euid=989 suid=989 fsuid=989 egid=988 sgid=988 fsgid=988 ses=4294967295 tty=pts2 comm=beam.smp exe=/usr/lib64/erlang/erts-5.10.1/bin/beam.smp subj=system_u:system_r:rabbitmq_beam_t:s0 key=(null) Hash: beam.smp,rabbitmq_beam_t,var_log_t,dir,write Additional info: reporter: libreport-2.1.5 hashmarkername: setroubleshoot kernel: 3.9.9-301.fc19.x86_64 type: libreport
*** This bug has been marked as a duplicate of bug 984158 ***