Bug 668099 - lsof does not understand SCTP associations
lsof does not understand SCTP associations
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lsof (Show other bugs)
6.0
All Linux
low Severity medium
: rc
: 6.4
Assigned To: Peter Schiffer
Iveta Wiedermann
: Patch, Upstream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-01-07 16:53 EST by Jeff Morriss
Modified: 2015-07-24 04:59 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Previously, lsof did not recognize Stream Control Transmission Protocol (SCTP) associations and consequently printed "can't identify protocol" at the end of the line describing a process using this type of association. With this update, support for SCTP has been added, and as a result, lsof correctly identifies SCTP associations in its output.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-22 01:54:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
sctp_demo.sh (982 bytes, application/x-shellscript)
2015-02-11 07:50 EST, Peter Schiffer
no flags Details

  None (edit)
Description Jeff Morriss 2011-01-07 16:53:15 EST
Description of problem:
lsof understands TCP and UDP connections, showing information about the port when run.

It does not do the same about SCTP associations, instead it says "can't identify protocol"

Version-Release number of selected component (if applicable):
lsof-4.78-3

How reproducible:
Every time

Steps to Reproduce:
1. Establish an SCTP association
2. Run lsof and look/grep for the process that has the association
3. Note that it says "can't identify protocol"
  
Actual results:
sctp_pitc  8024   morriss    3u     sock    0,5              83282 can't identify protocol


Expected results:
Something like:

sctp_pitc  8024   morriss    3u     IPv4  85073                SCTP myhost:54820->peer.example.com:10000 (ESTABLISHED)


Additional info:
Comment 1 RHEL Product and Program Management 2011-09-22 20:30:50 EDT
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Comment 2 Peter Schiffer 2012-03-06 12:10:43 EST
I am moving this bug to the RHEL-6 as lsof probably won't be updated in RHEL-5 again.
Comment 5 RHEL Product and Program Management 2012-09-07 00:59:19 EDT
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 6 RHEL Product and Program Management 2013-10-13 21:12:21 EDT
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 7 Branislav Náter 2014-11-27 07:20:44 EST
qa_ack+ for rhel-6.7
Comment 11 Peter Schiffer 2015-02-11 07:50:14 EST
Created attachment 990447 [details]
sctp_demo.sh

Better sctp demo working on RHEL-6, RHEL-7 and Fedora
Comment 13 errata-xmlrpc 2015-07-22 01:54:46 EDT
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://rhn.redhat.com/errata/RHBA-2015-1246.html

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