On Mon, 21 Mar 2011 18:34:41 -0700 (PDT), david@xxxxxxx wrote:
one thing that I've found is that even with --disable-ipv6 squid will
still use IPv6 on a system that has it configured (next I'll try and
see if that's what's going wrong on the systems that don't have it
configured, but those systems don't have strace on them, so I'll have
to build a throw-away system instead of using one of my standard
build
test systems)
David Lang
There are several extremely strange things going on here.
I'm cc'ing squid-dev in on this so if the workers behaviour continues
after this test Alex can be aware of it. Please followup to that list.
Can you try a clean build (brand new build directory, fresh copy of the
sources, re-./configure and re-make) using the 3.2 daily snapshot
(tarball or rsync) ?
If that still fails with either the v6 or the workers issue please
provide a copy of the include/autoconf.h and config.log files generated.
NP: I have not read the earlier mails
Amos
On Mon, 21 Mar 2011, david@xxxxxxx wrote:
Date: Mon, 21 Mar 2011 17:07:42 -0700 (PDT)
From: david@xxxxxxx
To: squid-users@xxxxxxxxxxxxxxx
Subject: Re: squid 3.2.0.5 even slower than squid 3.1
and
doesn't work with workers >1
resending without the attachments since this doesn't appear to have
gotten through to the list. if this gets through I'll reply with them.
David Lang
On Mon, 21 Mar 2011, david@xxxxxxx wrote:
Date: Mon, 21 Mar 2011 16:41:19 -0700 (PDT)
From: david@xxxxxxx
To: squid-users@xxxxxxxxxxxxxxx
Subject: Re: squid 3.2.0.5 even slower than squid 3.1 and doesn't
work with
workers >1
testing on a different system that has IPv6 enabled I don't get the
permission denied messages.
but I also don't end up with squid listening on _any_ TCP port
according to lsof.
note that this is with the same config file (with the exception of
the workers line) in all three cases.
David Lang
On Mon, 21 Mar 2011, david@xxxxxxx wrote:
Date: Mon, 21 Mar 2011 16:23:51 -0700 (PDT)
From: david@xxxxxxx
To: squid-users@xxxxxxxxxxxxxxx
Subject: squid 3.2.0.5 even slower than squid 3.1 and doesn't work
with
workers >1
In my testing of different squid versions, I attempted to use
squid 3.2.0.5
with workers 1 it's even slower than squid 3.1 (3.0 will do 4200
requests/sec, 3.1 will do 2100 requests/sec, 3.2 will do 1400
requests/sec)
when I set workers 2, squid won't even startup, see the attached
logs of startup for all the gory details, but short version is that
with workers 2 both threads fail to bind to the port, getting
permission denied.
below is the config options used to build this version, in case
there is something I should have put in (or shouldn't have put in)
that would affect either the speed or the ability to startup
Squid Cache: Version 3.2.0.5
configure options: '--prefix=' '--bindir=/usr/squid/bin'
'--sbindir=/usr/squid/sbin' '--libexecdir=/usr/squid/libexec'
'--datadir=/usr/squid/share' '--sysconfdir=/etc/squid'
'--localstatedir=/usr/squid/var' '--mandir=/usr/squid/man'
'--disable-ident-lookups' '--disable-wccp'
'--enable-kill-parent-hack' '--disable-loadable-modules'
'--disable-ssl' '--disable-translation' '--with-large-files'
'--with-logdir=/var/log' '--disable-ipv6'
'--with-filedescriptors=65535' '--disable-auto-locale'
--enable-ltdl-convenience
note that the system this is on doesn't have IPv6 compiled into
the kernel, but I used '--disable-ipv6' to disable it in squid as
well.
David Lang
