Search squid archive

Re: Upgrade to 3.4.3 and TCP Connections to parent failing more often

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Are all these servers uses squid?
I am not sure If I understood right?
Two forward proxies?
I will test it on one which is 3.4.3 and the upper one will be 3.4.1.
What is the load on these servers?
What type of connections are we talking about? CONNECT or regular http?

Eliezer

On 02/17/2014 04:56 PM, Paul Carew wrote:
Hi

I have recently upgraded our Squid servers from 3.3.11 to 3.4.3 and am
seeing the following error every few minutes in the cache log.

2014/02/17 13:43:02 kid1| TCP connection to wwwproxy02.domain.local/8080 failed

I have 2 servers configured on the LAN which handle connections over a
private WAN and 2 other servers on another WAN connected to the
internet. The first 2 servers use the second pair of servers connected
to the internet as a parent with the following lines in squid.conf:

cache_peer wwwproxy01.domain.local parent 8080 0 no-query no-digest carp
cache_peer wwwproxy02.domain.local parent 8080 0 no-query no-digest carp

With 3.3.11 I occasionally got the error, maybe two or three times daily.

Does anyone have any ideas why this might be occurring on 3.4.3 but
not 3.3.11? I've had a look at debug_options but can't see a section
that screams "debug me" for this particular error. Maybe section 11 or
15?

Many Thanks

Paul






[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux