Re: [squid-users] CLOSE_WAIT connections with ICAP

On 27/05/11 23:50, Daniel Beschorner wrote:
>> Which manager report? "idle connections" is a bit messy in the current
>> stables. It should only refer to the persistent, open, but not currently
>> in-use connections. The tag is left set sometimes and shows up on closed
>> ones.
> Under "File Descriptor Allocation".
>
>> If Squid actually sees them as closed or waiting in the idle pool, then
>> that would be one of the "large POST" or "large GET" bugs in bugzilla.
>>
>> Amos
>
> Actually it looks like that:
>
> Connections with FIN_WAIT1 state on ICAP server side seem ESTABLISHED at squid.

ICAP-closed connection.

  Idle pconn in Squid have readers set listening for FIN to arrive and
close the FD. This is strange but not conclusive.

  Looks a bit like the FIN never arrived.

> Squid connections in CLOSE_WAIT state are no longer visible at ICAP server side.

Squid-closed connection.

FIN packet sent by both sides. FIN-ACK packet from ICAP server not
arriving at Squid box. This confirms the FIN are not flowing right.

Both cases are pointing to packets containing FIN not flowing from the
ICAP server to Squid. Though strangely seem fine going in the other
direction.

>
> I will track the mentioned bugs und give feedback if next squid versions are making things better.
>
> Thank you!
> Daniel
>

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.12
   Beta testers wanted for 3.2.0.7 and 3.1.12.1