On 21/12/2011 10:28 a.m., Igor NM wrote:
Hi Andy,
The permissions and path is ok.
I find the problem... In my server, I disabled the ipv6, but squid try use it
to connect 'external acl'... On the line of acl, put the 'ipv4' parameter and
the problem is gone!
I don't find any solution where say 'put ipv4 on....', but I find this:
http://wiki.squid-cache.org/Features/IPv6#How_do_I_make_squid_use_IPv6_to_its_helpers.3F
"With squid external ACL helpers there are two new options ipv4 and ipv6. Squid
prefers to use unix pipes to helpers and these are ignored. But on some networks TCP
sockets are required. To work with older setups, helpers are still connected over IPv4 by
default. You can add ipv6 option to use IPv6."
But the squid use ipv6... because, I don’t now...
Cause it was not part of the IPv6 feature, but a bug in the TCP stack
handling.
Considering the lack of problems it caused (you are only the second
report in 6 months since the bug was added). I am thinking of switching
that background channel over to default IPv6 in the next release.
On the side; you have identified a helper which needs to be
IPv6-enabled. If only to make it listen on all of the localhost IPs. It
would be a good idea to get that fixed soonish.
Amos
