Hide Forgot
SELinux error: SELinux is preventing /usr/sbin/opendkim from write access on the directory /tmp. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that opendkim should be allowed write access on the tmp 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 opendkim /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:dkim_milter_t:s0 Target Context system_u:object_r:tmp_t:s0 Target Objects /tmp [ dir ] Source opendkim Source Path /usr/sbin/opendkim Port <Unknown> Host kolab. Source RPM Packages opendkim-2.8.4-1.fc19.x86_64 Target RPM Packages filesystem-3.2-13.fc19.x86_64 Policy RPM selinux-policy-3.12.1-74.14.fc19.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name kolab. Platform Linux kolab. 3.11.9-200.fc19.x86_64 #1 SMP Wed Nov 20 21:22:24 UTC 2013 x86_64 x86_64 Alert Count 185 First Seen 2013-11-30 22:47:22 PST Last Seen 2013-12-05 11:42:03 PST Local ID b29c6a7c-0599-47d4-acb0-57fea4a34284 Raw Audit Messages type=AVC msg=audit(1386272523.27:664): avc: denied { write } for pid=5167 comm="opendkim" name="/" dev="tmpfs" ino=1897 scontext=system_u:system_r:dkim_milter_t:s0 tcontext=system_u:object_r:tmp_t:s0 tclass=dir type=AVC msg=audit(1386272523.27:664): avc: denied { add_name } for pid=5167 comm="opendkim" name="dkim.28F65E017B.m8kXaA" scontext=system_u:system_r:dkim_milter_t:s0 tcontext=system_u:object_r:tmp_t:s0 tclass=dir type=AVC msg=audit(1386272523.27:664): avc: denied { create } for pid=5167 comm="opendkim" name="dkim.28F65E017B.m8kXaA" scontext=system_u:system_r:dkim_milter_t:s0 tcontext=system_u:object_r:tmp_t:s0 tclass=file type=AVC msg=audit(1386272523.27:664): avc: denied { write open } for pid=5167 comm="opendkim" path="/tmp/dkim.28F65E017B.m8kXaA" dev="tmpfs" ino=38283 scontext=system_u:system_r:dkim_milter_t:s0 tcontext=system_u:object_r:tmp_t:s0 tclass=file type=SYSCALL msg=audit(1386272523.27:664): arch=x86_64 syscall=open success=yes exit=ECHILD a0=7fccf174ab50 a1=c2 a2=180 a3=3 items=0 ppid=1 pid=5167 auid=4294967295 uid=409 gid=409 euid=409 suid=409 fsuid=409 egid=409 sgid=409 fsgid=409 ses=4294967295 tty=(none) comm=opendkim exe=/usr/sbin/opendkim subj=system_u:system_r:dkim_milter_t:s0 key=(null) Hash: opendkim,dkim_milter_t,tmp_t,dir,write
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/17107c1a7ed1592c76e7e3d0ced81a05c07ccb3a bug 1038793: EAP Cartridge manifest mentions 6.1.0
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.