Re: TCP Connection failures

From: Ralf Rudolph <>
Date: Thu, 30 Oct 1997 10:45:59 +0100

First of all, thanks for all of your replies.

On Wed, 29 Oct 1997 09:58:04 +0800, David Luyer <> wrote:
>(re: "TCP connection to xxx/3128 failed" problems)
>It's most likely a linux bug - up to 2.0.31 you can get "bind - address
>already in use" from autobinds or binds to port zero, meaning you fail
>connections which are meant to just come from random TCP ports.
>It's probably better to fix the network/machine/OS problems than to patch
>squid to handle them.

David, and all the others,
does that mean that upgrading to linux 2.0.(>31) will fix the problem? I dont care if the problem is within the squid or linux code, but I have to find a solution. BUT remember: Someone (sorry I lost the name) wrote on this list he had the same problem (loosing TCP connection to his parent cache) on a svr4 machine, not linux! And also to mention: Im not talking about the famous "operation already in progress" bug (yes, I have this one too, and yes, I can live with that, at least for now).

Upgrading all linux boxes would take me at least a day, but Im willing to do it if chances are that it will fix the problem.

Is there anybody who could affirm this? I mean, who had the lost TCP connections before upgrading, and solved it by upgrading to linux 2.0.31++ ?

Again, thanks for any hint or comment.

PS: Would this linux upgrade also solve the "operation already in progress" problems?

| Ralf Rudolph
| Dipl.-Inf. (FH)
| Artifex Editorial Services GmbH
| Johanna-Melber-Weg 4
| D-60599 Frankfurt / Germany
| Phone: +49-69-962217-24
| Fax: +49-69-610351
| E-Mail:
Received on Thu Oct 30 1997 - 01:51:16 MST

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:37:22 MST