Hide Forgot
Description of problem: SELinux is preventing /usr/bin/ruby-mri from 'ioctl' accesses on the unix_stream_socket unix_stream_socket. ***** Plugin catchall (100. confidence) suggests *************************** If sie denken, dass es ruby-mri standardmässig erlaubt sein sollte, ioctl Zugriff auf unix_stream_socket unix_stream_socket zu erhalten. Then sie sollten dies als Fehler melden. Um diesen Zugriff zu erlauben, können Sie ein lokales Richtlinien-Modul erstellen. Do zugriff jetzt erlauben, indem Sie die nachfolgenden Befehle ausführen: # grep ruby-mri /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:passenger_t:s0 Target Context system_u:system_r:init_t:s0 Target Objects unix_stream_socket [ unix_stream_socket ] Source ruby-mri Source Path /usr/bin/ruby-mri Port <Unbekannt> Host (removed) Source RPM Packages ruby-2.0.0.247-15.fc19.x86_64 Target RPM Packages Policy RPM selinux-policy-3.12.1-73.fc19.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 3.10.10-200.fc19.x86_64 #1 SMP Thu Aug 29 19:05:45 UTC 2013 x86_64 x86_64 Alert Count 3 First Seen 2013-09-04 16:11:39 CEST Last Seen 2013-09-04 16:11:50 CEST Local ID 77d88267-afad-4f23-9940-fc019d7e8649 Raw Audit Messages type=AVC msg=audit(1378303910.33:577): avc: denied { ioctl } for pid=3969 comm="ruby-mri" path="socket:[47904]" dev="sockfs" ino=47904 scontext=system_u:system_r:passenger_t:s0 tcontext=system_u:system_r:init_t:s0 tclass=unix_stream_socket type=SYSCALL msg=audit(1378303910.33:577): arch=x86_64 syscall=ioctl success=no exit=ENOTTY a0=1 a1=5401 a2=7fffd344a010 a3=1166228 items=0 ppid=3967 pid=3969 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=ruby-mri exe=/usr/bin/ruby-mri subj=system_u:system_r:passenger_t:s0 key=(null) Hash: ruby-mri,passenger_t,init_t,unix_stream_socket,ioctl Additional info: reporter: libreport-2.1.6 hashmarkername: setroubleshoot kernel: 3.10.10-200.fc19.x86_64 type: libreport
Could you add your output of # ps -eZ |grep init
Here is the output: [root@localhost ~]# ps -eZ |grep init system_u:system_r:init_t:s0 1 ? 00:00:17 systemd system_u:system_r:init_t:s0 1280 ? 00:01:41 teamviewerd system_u:system_r:initrc_t:s0 1437 ? 00:00:17 ruby-mri system_u:system_r:initrc_t:s0 1886 ? 00:00:01 wineserver
Ok, I think I know what's going on. # ps -efZ |grep initrc basically it will relate with puppet.
Yeah, puppet was installed, what additional info do you need exactly?
I would like to see your output of # ps -efZ |grep initrc Thank you.
I'm afraid this development environment does no longer exist, so I can't provide the output.
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.