I found it listed in 3.0PRE3 bugs, here is the link that I found, it is listed as fixed. http://ftp.isu.edu.tw/pub/Unix/Proxy/Squid/Versions/v3/3.0/bugs/index.html#squid-3.0.PRE3-accel_cache_peer_name However, this exact problem was occurring I would have never gotten out, I discovered since taking the name= option off that it was apparently just occurring less often. Maybe just a coincidence, that it got better when I changed it. I have changed the rule back to IP address to see if it continues without error over a longer period of time. I have ruled out any network connection problems being the cause (at least on my end). Let me know if there is any debug options I should enable to give you more information. -----Original Message----- From: Henrik Nordström [mailto:henrik@xxxxxxxxxxxxxxxxxxx] Sent: Wednesday, March 31, 2010 2:24 PM To: Dean Weimer Cc: squid-users@xxxxxxxxxxxxxxx Subject: Re: cache_peer using DNS name ons 2010-03-31 klockan 12:25 -0500 skrev Dean Weimer: > I am working on testing a hosted web filter solution, this involves > chaining our internal squid proxy to the hosted web filter proxy > server. I was seeing very poor performance and found several "TCP > connection to filters.dnsdomainname.com/8081 failed" entries in the > log. I discovered that changing he line to the IP address stopped > this problem. Further searching found a bug in 3.0 where using a DN > name for a parent and the name= option on a chace_peer line caused it > to try and lookup the name= value instead of the DNS name. I went > back and removed the name= option and set or line back to the DNS > domain name. TCP connection errors are gone now. Very Odd.. is there an open bug report on this? I don't see any trace of this happening from reading the sources. There is a very clear distinction between host and name. Regards Henrik
