On 11/02/11 01:56, Alex Sharaz wrote:
Sent this out a while back. Don't think I got any replies. Anyway, Still happening but now with squid 3.1.10/3.1.11 I'd like to do a phased upgrade to 3.1.x but don;t want to try it if I'm still getting these netdb errors Rgds Alex Hi, For a while now I've been running a squid 2.7stable7 service here (just upgraded to stable9) and thought I'd try out the 3.1.4 build on my test web cache. Although the test cache is linked into my production cache cluster as a sibling the universtiy access the cache service via a serveriron hardware load balancer which load balances traffic over all my 2.7.STABLE9 boxes. I access the test cache directly. Since this morning, when i upgraded to 3.1.4 I've been seeing the following in the 3.1.4 cache.log file
> <snip>
2010/06/21 13:40:18| netdbExchangeHandleReply: corrupt data, aborting 2010/06/21 13:40:25| netdbExchangeHandleReply: corrupt data, aborting 2010/06/21 13:40:26| netdbExchangeHandleReply: corrupt data, aborting 2010/06/21 13:55:15| NETDB state saved; 821 entries, 3 msec Don't think I've seen this before. Web cache configs available if necessary. Anyone else trying to mix 2.7 and 3.1 siblings? Rgds
This message is not fatal to Squids operation. It just means something unknown as encountered in the exchange and the remaining input data had to be discarded.
The whole NetDB transfer is open to machine architecture mis-match problems and 64-bit/32-bit problems. Along with unknown record type coding.
Is it showing up just on the squid-3 boxes or on the 2.x boxes as well? Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.11 Beta testers wanted for 3.2.0.4
