Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1104270 - SELinux reoccurring avc: denied { name_connect } for pid=14925 comm="ruby" dest=9200 scontext=system_u:system_r:passenger_t:s0 tcontext=system_u:object_r:port_t:s0 tclass=tcp_socket
Summary: SELinux reoccurring avc: denied { name_connect } for pid=14925 comm="ruby"...
Keywords:
Status: CLOSED DUPLICATE of bug 1078265
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SELinux
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-03 17:05 UTC by Jan Hutař
Modified: 2014-06-25 10:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-25 10:20:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jan Hutař 2014-06-03 17:05:00 UTC 
Description of problem:
SELinux reports reoccurring avc:  denied  { name_connect } for  pid=14925 comm="ruby" dest=9200 scontext=system_u:system_r:passenger_t:s0 tcontext=system_u:object_r:port_t:s0 tclass=tcp_socket


Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140529.0
# rpm -qa | grep selinux | sort
candlepin-selinux-0.9.7-1.el6_5.noarch
foreman-selinux-1.6.0-3.el6sat.noarch
libselinux-2.0.94-5.3.el6_4.1.x86_64
libselinux-devel-2.0.94-5.3.el6_4.1.x86_64
libselinux-python-2.0.94-5.3.el6_4.1.x86_64
libselinux-ruby-2.0.94-5.3.el6_4.1.x86_64
libselinux-utils-2.0.94-5.3.el6_4.1.x86_64
pulp-selinux-2.4.0-0.18.beta.el6sat.noarch
selinux-policy-3.7.19-231.el6.noarch
selinux-policy-targeted-3.7.19-231.el6.noarch


How reproducible:
Looks like ti appears periodically about every 3 minutes


Steps to Reproduce:
Unknown


Actual results:
type=AVC msg=audit(1401814096.195:9181): avc:  denied  { name_connect } for  pid=14925 comm="ruby" dest=9200 scontext=system_u:system_r:passenger_t:s0 tcontext=system_u:object_r:port_t:s0 tclass=tcp_socket
type=SYSCALL msg=audit(1401814096.195:9181): arch=c000003e syscall=42 success=no exit=-111 a0=f a1=7fc6b922f610 a2=1c a3=ff00 items=0 ppid=1 pid=14925 auid=4294967295 uid=497 gid=498 euid=497 suid=497 fsuid=497 egid=498 sgid=498 fsgid=498 tty=(none) ses=4294967295 comm="ruby" exe="/opt/rh/ruby193/root/usr/bin/ruby" subj=system_u:system_r:passenger_t:s0 key=(null)


Expected results:
No AVC SELinux messages
Comment 1 RHEL Program Management 2014-06-03 17:15:12 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Lukas Zapletal 2014-06-25 10:20:21 UTC 
Hey,

this will be fixed in the upcoming build. Unfortunately the latest two snaps did not contain valid selinux build. This was fixed some time ago.

*** This bug has been marked as a duplicate of bug 1078265 ***
Note You need to log in before you can comment on or make changes to this bug.