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 1161576 - Allow root to connect to port 9200
Summary: Allow root to connect to port 9200
Keywords:
Status: CLOSED DUPLICATE of bug 1161254
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Install Guide
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Athene Chan
QA Contact: David O'Brien
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-07 11:20 UTC by Pavel Moravec
Modified: 2018-12-09 19:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Build Name: 22922, Installation Guide-6.0-1 Build Date: 03-10-2014 10:50:13 Topic ID: 9711-714936 [Latest]
Last Closed: 2014-11-10 23:09:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1262303 0 None None None Never

Description Pavel Moravec 2014-11-07 11:20:05 UTC
Title: Installing Red Hat Satellite

Describe the issue:
Step 6: "Run the following commands to configure the firewall to limit elasticsearch to foreman and katello users and make these rules persistent during reboots: " modifies firewall in such a way, that elasticsearch (on port 9200) can get connections from processes owned by foreman or katello. While during installation, katello-install script runs a check:

/bin/bash /usr/share/katello-installer/modules/service_wait/bin/service-wait elasticsearch start

under root user that tests that port accessibility (wget and curl against http://localhost:9200 are invoked).

Following installation manual, this check would fail with error:

 Could not start Service[elasticsearch]: Execution of '/usr/share/katello-installer/modules/service_wait/bin/service-wait elasticsearch start' returned 5: Starting elasticsearch (via systemctl):  [  OK  ]

(installation will succeed, just the error will appear what's confusing for an end user)


Suggestions for improvement:
Add there a rule allowing root to access the port. I.e.:

- s/to foreman and katello users/to root, foreman and katello users/
- add line:

iptables -A OUTPUT -o lo -p tcp -m tcp --dport 9200 -m owner --uid-owner root -j ACCEPT \
&&

to the box with commands (before "-j DROP" line)


Additional information:
I am curious why installations (with default firewall set and strictly following manual) could ever succeed without hitting this error. I installed Sat6 many times and hit this for the first time - on RHEL7 installed from iso with few packages updated.

Comment 2 Athene Chan 2014-11-10 23:09:06 UTC
Hello Pavel,

This issue is being resolved today or tomorrow with an async update. Please check BZ#1161254 for more details

Thank you for your feedback!

Cheers,
Athene

*** This bug has been marked as a duplicate of bug 1161254 ***


Note You need to log in before you can comment on or make changes to this bug.