[Fwd: [squid-users] Update: #redirectors decays over time]

After patiently stracing some of my squirms it appears
they are exiting with ECONNRESET (connection reset by
peer) on a read(0) call. Presumably the peer is the
squid process sitting at the other end of the pipe.

How to avoid this? [this is a serious problem for us
as when the number of redirectors falls too low squid
decides instead of forking more, it'll just give up
and kill itself (which is poor!)]. This is happening
on all of our caches once every couple of hours. I need
to fix this...!!

thanks again,
Mike

-------- Original Message --------
Subject: [squid-users] #redirectors decays over time
Date: Tue, 21 Aug 2001 13:59:20 +0200
From: Mike Kiernan <mkiernan@onet.pl>
Organization: Onet.pl S.A.
To: squid user group <squid-users@squid-cache.org>

I have increased the max number of directors to 256 of which I am
currently using 90 [btw. why is it hardcoded so low - 32 ??]

I've noticed that over time the number of available redirectors
decays from 90. I get the following messages in my cache log:

2001/08/21 13:18:51| helperHandleRead: FD 58 read: (11) Resource
temporarily unavailable
2001/08/21 13:18:51| WARNING: redirector #22 (FD 58) exited

Can anyone explain what is happening here ? [my redirector is squirm,
and this is squid 2.4stable1 on linux]

Thanks for your help,
Mike
Received on Tue Aug 21 2001 - 09:45:28 MDT