Bug 18213 - TCP timer for TIME_WAIT state breaks
Summary: TCP timer for TIME_WAIT state breaks
Status: CLOSED DUPLICATE of bug 16729
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: inetd
Version: 6.2
Hardware: i386
OS: Linux
high
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-10-03 13:27 UTC by Need Real Name
Modified: 2008-05-01 15:37 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2001-01-25 19:26:11 UTC

Attachments (Terms of Use)
log of sockets in TIME_WAIT state (2.90 KB, text/plain)
2000-10-03 13:32 UTC, Need Real Name 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Need Real Name 2000-10-03 13:27:44 UTC 
I'm running vmlinux-2.2.14-6.1.1smp on a Dell PowerEdge 2450.  Our 
application connects to numerous POP3 servers on a periodic basis.  We 
monitor the number of sockets in TIME_WAIT state, and observe this number 
going up and down, as expected.  After a while (can be an hour or a day), 
we notice that sockets no longer close, and the number of sockets in 
TIME_WAIT state increase steadily until the kernel crashes (>5000 sockets).

Is this a bug in the TCP/IP stack?  If so, are there any remedies?
Comment 1 Need Real Name 2000-10-03 13:32:26 UTC 
Created attachment 3660 [details]
log of sockets in TIME_WAIT state
Comment 2 Pekka Savola 2000-10-03 19:42:27 UTC 
Are you synchronizing time on the system?  _Could_ be related to #14876 and friends.
Comment 3 Need Real Name 2000-10-03 19:52:21 UTC 
I am using ntp 4.0.99i-1 to sync the clocks amongst various servers.  All other 
time services are off in inetd.conf.
Comment 4 Jeff Johnson 2000-10-06 21:32:14 UTC 
Can you run lsof to verify the ownership of the connections?
The output of netstat -a would be helpful as well. Simply knowing the number
of sockets in TIME_WAIT is not enough to identify the cause of the problem.

I'd also double check that the time service is actually off using netstat -a,
as my blind guess is that this problem is #14876 et al as well.
Comment 5 Trond Eivind Glomsrxd 2001-01-19 21:20:36 UTC 
I'd like to repeat the request for information...
Comment 6 Trond Eivind Glomsrxd 2001-01-25 19:26:07 UTC 
Can you see if the one at http://people.redhat.com/teg/ helps?
Comment 7 Trond Eivind Glomsrxd 2001-01-30 16:49:24 UTC 

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