Re: [squid-users] comm_accept

These might be seen if the client aborts the connection during early TCP
setup (i.e. before the connection is accepted by Squid). Generally
harmless, but might be a sign of a run-away client/robot.

--
Henrik Nordstrom
Suqid hacker
Chris Conn wrote:
> 
> Hello,
> 
> I am searching for a problem with messages in cache_log and have come
> across this:
> 
> http://www.squid-cache.org/mail-archive/squid-users/200101/0303.html
> 
> ========
> I have recently upgraded from Linux 2.2.16 to 2.2.18 and have begun
> suddenly getting a TON (about 20 per minute) of these:
> 
> 2001/03/20 17:04:10| comm_accept: FD 4: (104) Connection reset by peer
> 2001/03/20 17:04:10| httpAccept: FD 4: accept failure: (104) Connection
> reset by
>  peer
> 2001/03/20 17:04:10| comm_accept: FD 4: (104) Connection reset by peer
> 2001/03/20 17:04:10| httpAccept: FD 4: accept failure: (104) Connection
> reset by
>  peer
> 2001/03/20 17:04:12| comm_accept: FD 4: (104) Connection reset by peer
> 2001/03/20 17:04:12| httpAccept: FD 4: accept failure: (104) Connection
> reset by
>  peer
> 
> I am running S2.3STABLE4 and had never seen until today these messages.
> I have checked my FDs and I have 4096 useable and about 3000 available.
> 
> Any ideas?
> 
> Thanks,
> 
> Chris