Bug 55985 - netstat weirdness
Summary: netstat weirdness
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: net-tools
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Phil Knirsch
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-11-09 21:27 UTC by Frank Hirtz
Modified: 2015-03-05 01:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-05-23 08:08:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Frank Hirtz 2001-11-09 21:27:23 UTC
Description of Problem:

we've seen 2 strange problems:

1) netstat displays 2 identical lines

netstat -a |grep piics2
tcp        0      0 hqias4:mtflocal         piics2:33135
ESTABLISHED
tcp        0      0 hqias4:mtflocal         piics2:33135
ESTABLISHED

2) netstat display this:

 warning, got bogus tcp line.
------------------------------
tcp        0      0 hqias4:mtflocal         piics2:33235
ESTABLISHED ufilter    7312379
------------------------------
warning, got bogus tcp line.

---
Preston evaluated this and indicated that it could affect the performance
of anything using the proc/net/tcp, but it was possible to change netstat
to filter for duplicate entries. 

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


How Reproducible:


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:

Comment 1 Phil Knirsch 2002-02-24 12:36:20 UTC
Could you be a little more specific in how to recreate this problem? Otherwise
it's kinda hard to check if a fix actually fixes the problem.

Thanks,

Read ya, Phil

Comment 2 Phil Knirsch 2003-05-23 08:08:38 UTC
I still cannot reproduce this bug. Closing as works for me now.

Read ya, Phil

Comment 3 Vikul 2004-03-19 19:24:05 UTC
I am getting this error but not on a consistent basis. One more thing 
which might help replicating the issue is that we have too many 
connections in the CLOSING state.


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