On Thu, 4 Feb 2010 10:25:44 +1100, "Michael Bowe" <mbowe@xxxxxxxxxxxxxxx> wrote: >> -----Original Message----- >> From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] > >> Same ./configure options? > > Yes > > ./configure \ > --enable-linux-netfilter \ > --enable-async-io --with-pthreads --enable-storeio=ufs,aufs \ > --enable-removal-policies=lru,heap \ > --with-large-files \ > --disable-auth \ > --with-filedescriptors=65536 \ > --enable-cache-digests > >> Any relevant difference in the config.log produced during build? > > I had a good dig around but couldn't see any differences > > > I found this in a strace : > > [pid 11780] socket(PF_INET6, SOCK_STREAM, IPPROTO_TCP) = 4 > [pid 11780] setsockopt(4, SOL_IP, 0x13 /* IP_??? */, [1], 4) = 0 > [pid 11780] bind(4, {sa_family=AF_INET6, sin6_port=htons(0), > inet_pton(AF_INET6, "::2", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, > 28) = -1 EADDRNOTAVAIL (Cannot assign requested address) > [pid 11780] close(4) = 0 > [pid 11780] write(2, "2010/02/04 10:21:55| FATAL: http("..., 862010/02/04 > 10:21:55| FATAL: http(s)_port: TPROXY support in the system does not work. > ) = 86 > > So sounds like something related to IPv6 ? There are TPROXY IPv6 patches floating around, so Squid now actively tests to see if your kernel supports it as well. Thats not expected to succeed in most cases for quite some time yet. The problem is that there should be some IPv4 probes to check that the current mainstream support is available immediately afterward, before declaring it broken. Your trace shows no sign of those happening at all. If you don't mind doing a few builds and working with me to track it down I'll get back to you shortly with a patch to do some better debugging. Amos
