Re: assertion failed: ipcache.cc:995: "tmpbuf" in 3.HEAD-CVS

Bernhard Schmidt wrote:
> Amos Jeffries wrote:
>
>>>>> safe_free happily accepts NULLs.. hence the name safe_...
>>>> I forget exactly why it was there. Likely a crash when it was
>>>> non-NULL when it should have been NULL. Fixed now anyway.
>>>
>>> Current CVS (checkout two minutes ago at 11.35pm GMT) is pretty much
>>> broken again regarding the internal DNS. Pages don't open when you
>>> hit a CNAME and I get frequent errors like
>>>
>>> 2008/01/12 00:33:12| ipcacheParse: No Address records in response to
>>> 'www.hp.com'
>>> 2008/01/12 00:33:37| ipcacheParse: No Address records in response to
>>> 'welcome.hp-ww.com'
>>> 2008/01/12 00:36:15| ipcacheParse: No Address records in response to
>>> 'www.google-analytics.com'
>>>
>>> in the cache.log. It looks like DNS times out a couple of times.
>>> Debugging section 14 does not give more results. The query
>>>
>>> 00:41:59.075658 IP 83.170.1.240.36282 > 83.170.1.240.53: 37174+
>>> AAAA? www.hp.com. (28)
>>> 00:41:59.075913 IP 83.170.1.240.53 > 83.170.1.240.36282: 37174 1/1/0
>>> CNAME www.hpgtm.nsatc.net. (116)
>>>
>>> is repeated several times. This only seems to happen when you hit a
>>> CNAME on an IPv4-only host, CNAME to dual-stacked or IPv4-only with
>>> an address directly associated to the hostname works.
>>
>> Sigh, thats so weird.
>>
>> Sorry the proper debug options to trace this are:
>> debug_options ALL,0 14,9 78,9
>>
>>
>> It's working perfectly here. On those same domains too.
>
> Found out it breaks when you set
>
> dns_v4_fallback no

Ah. Yes that would do it :-)

It seems you have been struggling under this recently fixed failover bug
all this time. Sorry about that.

<snip>
> If you don't do it it works, but at least back when you added it it was
> desperately needed.
>
> Regards,
> Bernhard

Amos

-- 
Please use Squid 2.6STABLE17+ or 3.0STABLE1+
There are serious security advisories out on all earlier releases.