|Summary:||TCP timer for TIME_WAIT state breaks|
|Product:||[Retired] Red Hat Linux||Reporter:||Need Real Name <adiorio>|
|Component:||inetd||Assignee:||Trond Eivind Glomsrxd <teg>|
|Status:||CLOSED DUPLICATE||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2001-01-25 19:26:11 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
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?