Re: [squid-users] Squid giving "(21) Is a directory" error

Hi Eliezer,

I discover the source of the bug with squid. The problem was that
someone had setup the /etc/localtime to /usr/local/timezone. It is
very wrong and keep the squid giving to the user the mentioned
problem. :'(

I get this when I resolved to take a strace to fill up a bug report :)

Thanks anyway,

Ricardo

On Thu, May 15, 2014 at 10:00 AM, Ricardo Lucca <rlucca_at_gmail.com> wrote:
> Hi there,
>
> $ uname -a
> Linux localhost 3.2.54 #1 SMP Mon Apr 7 12:40:28 GMT 2014 x86_64 GNU/Linux
>
> The gcc version is 4.7.1.
>
> Ricardo Lucca
>
>
> On Thu, May 15, 2014 at 3:54 AM, Eliezer Croitoru <eliezer_at_ngtech.co.il> wrote:
>> Hey Ricardo,
>>
>> Squid 2.7 is not under maintenance for a very long time and it's recommended
>> to use newer versions such as 3.3 at least.
>> 3.4.5 version of squid is production ready but since there are new features
>> inside this branch some may not feel comfort to use this new code untested
>> for their environment.
>> I recommend on any transition from old version to new version first make a
>> test to verify that all your needs are compatible with the newer version.
>>
>> You can always ask here for guidance about testing and verification to make
>> sure you are not alone in the process.
>>
>> What OS are you using?
>> What Kernel?
>> note that many already use 3.4.5 and can compare your version to their.
>> For me google works and many other sites.
>> it seems like a non usual issue which needs further testing.
>>
>> Lets try to first fill the missing details about the environment.
>>
>> Eliezer
>>
>> On 05/15/2014 07:56 AM, Ricardo Lucca wrote:
>>>
>>> Hi there,
>>>
>>> I recently installed the squid and I tried the minimal configuration
>>> in a virtual machine. The squid gives access to other machine, but it
>>> keeps failing with a error "(21) Is a directory" when I tried access
>>> the "www.google.com.br". I replaced the version 3.4.5 with the version
>>> 3.2 and 3.1 and all get the same error. The version 2.7 worked well.
>>> Can it be my configuration mistake or it is a bug? I used the
>>> squid.conf.default that came in the source.
>>>
>>> I managed to get the log of this error:
>>>
>>> 2014/05/13 19:14:00.603| comm.cc(1114) connect: to 173.194.42.183:80
>>> 2014/05/13 19:14:00.603| comm_connect_addr: connecting socket 12 to
>>> 173.194.42.183:80 (want family: 2)
>>> 2014/05/13 19:14:00.603| comm_connect_addr: sock=12, addrinfo(
>>> flags=4, family=2, socktype=1, protocol=6, &addr=0x112ff70, addrlen=16
>>> )
>>> 2014/05/13 19:14:00.603| connect FD 12: (-1) (21) Is a directory
>>> 2014/05/13 19:14:00.603| connecting to: 173.194.42.183:80
>>> 2014/05/13 19:14:00.603| comm.cc(1147) connect: FD 12: * - try again
>>>
>>> I compiled this version of the squid myself running:
>>>
>>> $ ./configure --enable-ssl --disable-ipv6 && make
>>>
>>> Another question, is the version 3.4.5 suitable for production use? Or
>>> it is recommend the use of version 2.7 yet?
>>>
>>> Thanks
>>>
>>
Received on Mon May 19 2014 - 18:45:50 MDT