Re: [squid-users] Inaccessible google.com (squid-3.4)

Il 27/03/2014 15:25, Eliezer Croitoru ha scritto:
> I have the same issue and since they had couple issues with their dns
> cache services I assume it's not the only issue.
> Can you try to use tcpdump and filter it to google related
> packets\connections?
>
> Eliezer

I will next time it happens.

I haven't been able to reproduce the issue at will yet.

Thanks.

>
> On 03/28/2014 01:56 PM, Marcello Romani wrote:
>> Hi,
>> I'm struggling with a recurring problem, namely the very long time
>> it takes (and often the impossibility) to reach www.google.com from my
>> LAN, which sits behind a custom compiled squid-3.4.
>>
>> When this happens, other websites are not affected.
>> Also, if I change the browser setting to "no proxy", the problem goes
>> away.
>>
>> As a workaround, issuing /usr/local/squid/sbin/squid -k reconfigure
>> temporarily fixes the problem: after it has completed, pressing F5 or
>> trying to directly access www.google.com again succeds within the usual
>> time frame.
>>
>> My squid.conf has
>>
>> dns_v4_first on
>>
>> Also, /proc/sys/net/ipv6/conf/default/disable_ipv6 == 1
>>
>> squid -v reads as follows:
>>
>> # /usr/local/squid/sbin/squid -v
>> Squid Cache: Version 3.4.4
>> configure options:
>> '--prefix=/usr/local/squid'
>> '--enable-xmalloc-statistics'
>> '--enable-storeio=aufs diskd rock ufs'
>> '-enable-removal-policies=heap lru'
>> '--enable-icmp'
>> '--enable-delay-pools'
>> '--enable-ssl'
>> '--disable-auth'
>> --enable-ltdl-convenience
>>
>> The box is a Primergy TX200 server running debian 6.0.9, with
>> 2.6.32-5-686-bigmem kernel.
>>
>> Any hints as to where to look to pinpoint the issue would be greatly
>> appreciated.
>>
>> Thank you in advance.
>>
>

-- 
Marcello Romani