Re: [squid-users] commBind: Cannot bind socket FD 98 to *:0: (98) Address already in use

Hi Henrik,

thanks for your hints.

I increased the ip_local_port_range as suggested. It was 10k to 32k before.
But, how can I maintain persistent connections from the front-side
Apache to the squid?

The setup is as follows:

World -> apache2 (using mod_rewrite and mod_proxy) -> squid -> App-Server

As far as I understand, the connection from apache2 to squid should be persistent, right?
This might be a problem, because Apache's mod_proxy doesn't seem to support persistent
connections. If I'm wrong, can anyone give me a clue how to get this working?

Regards
Stefan

Henrik Nordstrom wrote:
> fre 2007-02-02 klockan 14:11 +0100 skrev Stefan Bohm:
>> Hi all,
>>
>> yesterday we had some strange problems running our reverse-proxy squid cluster.
>> During some high-traffic sports event, squid starts to emit messages
>> like:
>>
>> commBind: Cannot bind socket FD 98 to *:0: (98) Address already in use
>
> You have run out of free ports, all available ports occupied by
> TIME_WAIT sockets.
>
> Things to look into
>
> 1. Make sure you internally use persistent connections between Squid and
> the web servers. This cuts down on the number of initiated connections/s
> considerably.
>
> 2. Configure the unassigned port range as big as possible in your OS. On
> Linux this is set in /proc/sys/net/ipv4/ip_local_port_range. The biggest
> possible range is 1024-65535 and can sustain up to at least 500
> connections/s continuous load squid->webservers.
>
> Regards
> Henrik
Received on Fri Feb 02 2007 - 09:50:48 MST