Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1259692

Summary:	netstat to print also ESTABLISHED connections
Product:	Red Hat Satellite	Reporter:	Pavel Moravec <pmoravec>
Component:	Foreman Debug	Assignee:	Katello Bug Bin <katello-bugs>
Status:	CLOSED ERRATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1.1	CC:	bbuckingham, cwelton, sthirugn
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
URL:	http://projects.theforeman.org/issues/11677
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 08:55:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pavel Moravec 2015-09-03 11:24:17 UTC

Description of problem:
foreman-debug generates netstat file as an output of "netstat -tulpn" command. -l means only listening sockets are displayed. While it is often important to see also _established_ connections, i.e. celery connected to CDN:443 during repo sync, goferd on a content host to 5647, dispatch router on capsule to 5646, etc. If some such connection is missing, it is a symptom of some problem - but netstat in foreman-debug does not provide that info.

Please provide "netstat -putna" output rather (-l --> -a, print _all_ sockets).


Version-Release number of selected component (if applicable):
foreman-debug-1.7.2.34-1.el7sat.noarch


How reproducible:
100%


Steps to Reproduce:
1. foreman-debug
2. (in extracted tarball):  grep ESTAB netstat


Actual results:
no established TCP connection


Expected results:
many established connections, like:

tcp        0      0 1.2.3.4:40912      1.2.3.4:5671       ESTABLISHED 25428/qdrouterd     


Additional info:

Comment 2 Bryan Kearney 2015-09-04 14:04:19 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/11677 has been closed
-------------
Pavel Moravec
Applied in changeset commit:ee3275af331a74e8aae6c3654c914ebd7d4267c7.

Comment 3 Tazim Kolhar 2015-11-19 09:39:27 UTC

VERIFIED:
# rpm -qa | grep foreman
hp-dl360g7-01.lab.eng.brq.redhat.com-foreman-proxy-1.0-1.noarch
foreman-release-1.11.0-0.develop.201511161350git860ef06.el7.noarch
foreman-vmware-1.11.0-0.develop.201511161350git860ef06.el7.noarch
foreman-debug-1.11.0-0.develop.201511161350git860ef06.el7.noarch
foreman-libvirt-1.11.0-0.develop.201511161350git860ef06.el7.noarch
foreman-selinux-1.11.0-0.develop.201510071426git6234447.el7.noarch
tfm-rubygem-foreman_hooks-0.3.9-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.8-1.el7.noarch
tfm-rubygem-foreman_gutterball-0.0.1-3.el7.noarch
foreman-postgresql-1.11.0-0.develop.201511161350git860ef06.el7.noarch
hp-dl360g7-01.lab.eng.brq.redhat.com-foreman-proxy-client-1.0-1.noarch
tfm-rubygem-foreman_discovery-4.1.2-1.fm1_11.el7.noarch
foreman-1.11.0-0.develop.201511161350git860ef06.el7.noarch
foreman-ovirt-1.11.0-0.develop.201511161350git860ef06.el7.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-3.el7.noarch
foreman-proxy-1.11.0-0.develop.201511161424gitf24be74.el7.noarch
foreman-compute-1.11.0-0.develop.201511161350git860ef06.el7.noarch
tfm-rubygem-hammer_cli_foreman_docker-0.0.3-4.el7.noarch
hp-dl360g7-01.lab.eng.brq.redhat.com-foreman-client-1.0-1.noarch
tfm-rubygem-foreman_bootdisk-6.0.0-2.fm1_10.el7.noarch
tfm-rubygem-hammer_cli_foreman-0.4.0-1.201511111650gitdda13df.el7.noarch
foreman-gce-1.11.0-0.develop.201511161350git860ef06.el7.noarch
foreman-release-scl-1-1.el7.x86_64
tfm-rubygem-foreman_docker-1.4.1-2.fm1_10.el7.noarch
tfm-rubygem-foreman-tasks-0.7.6-1.fm1_10.el7.noarch

steps:
30607/ntpd          
udp6       0      0 ::1:123                 :::*                                30607/ntpd          
udp6       0      0 :::123                  :::*                                30607/ntpd          
udp6       0      0 :::45455                :::*                                15518/dhcpd         
udp6       0      0 ::1:33704               ::1:33704               ESTABLISHED 4220/postgres: fore

Comment 6 errata-xmlrpc 2016-07-27 08:55:48 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1500