Can you share the squid.conf??
This will make sure we understand what you are doing\trying to do.
please feel free to share squid.conf while removing any personal data.
Once we would have the squid.conf we can try to understand more what
might be the source of the problem..
If you do not want to share squid.conf try to share some tcpdump and
network digram that can assist us to identify the source of the problem.
I see the logs and understand the basic infrastructure but it still far
from drawing a picture of what is needed to understand.
Regards,
Eliezer
On 08/12/2013 01:10 PM, x-man wrote:
> Hi Amos,
>
> we were actually thinking of trying something else, which is
>
> Configure each squid worker to interact with different cache peer on, which
> is listening on different port.
>
> We will start multiple instances of our cache peer software listening on
> different ports as well.
>
> This way every squid kid will talk to particular cache peer and I hope this
> way there will be no problem with the return traffic from cacher peer to
> squid kid.
>
> Let me know your thoughts on this.
>
> Also what is the best way in squid config to put some specific setting for
> particular kid? I saw some examples with IF clauses, is this working in
> 3.3.8?
>
> Thanks in advance.
>
>
>
>
> --
> View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/icp-query-timeout-directive-is-not-working-in-3-3-8-for-some-reason-tp4661324p4661527.html
> Sent from the Squid - Users mailing list archive at Nabble.com.
>
Received on Mon Aug 12 2013 - 10:39:24 MDT
This archive was generated by hypermail 2.2.0 : Mon Aug 12 2013 - 12:00:07 MDT