On 11/02/2012 2:27 a.m., Helmut Hullen wrote:
Hallo, Ralf,
Du meintest am 10.02.12:
my self made squid 3.2.0.14 sometimes produces messages like
Jan 30 08:56:58 Arktur squid[4263]: Failed to select source for
'http://ivwbox.de/'
ivwbox.de does not resolve. Maybe that's normal?
I may not believe it. I never had these messages with older squid
versions.
Older Squid versions only gt as fars as figuring out DIRECT yes/no. Then
passed the domain name to be connected to by a slow iterative process
which did multiple DNS lookups before timing out with no such warnings.
3.2 looks up the domain IPs before deciding how to connect to it (IPv4
or IPv6, or an existing open persistent connection). Which resolves the
long standing problems with deciding the TCP outgoing address and TOS
values before figuring out what remote server IP they will be used to
connect to.
The side effect is all those problems resolved, and you now get this
nice report when a request does not have a valid destination to go to.
This message appeared not only with "ivwbox.de" but also p.e. with
"google.com". About 5 to 10 messages within 1 minute, and then a long
pause (long = more than 30 minutes ...)
Sounds a bit like behaviour Alex S reported to squid-dev about the new
parallel A/AAAA lookups. Which full version string was that squid?
I've just re-installed an older version - my colleague doesn't like
restarting "squid" hourly ... (I don't know if that's related to "Failed
to select" ...)
Possibly is. Every restart the DNS gets shutdown and cannot resolve any
domains for the requests which are still only being parsed at that time
(cached DNS records should be okay, new domains orwith expired records
will fail).
Amos
