On 09/28/2016 02:22 AM, Eugene M. Zheganin wrote: > I took the debug trace and both the tcpdump client-side and server-side > (towards the internet) capturea. ... > I requested a http://www.ru/index.html from a client machine Chrome. AFAICT, Squid did not receive a request for www.ru: > $ egrep -c 'wwww.ru|217.112.35.75' cache.log.debug > 0 > $ tshark -V -r squid-stuck-reference-client.pcap | egrep -c 'wwww.ru|217.112.35.75' > 0 If you find that request in your client-to-Squid packet captures, please point me to it. Otherwise, please fix your captures and redo the test from scratch. Also, please include access.log and/or some other indication of which transactions got stuck. You may want to stop captures _after_ you cancel the stuck request -- it is more difficult to find "what has not happened" (no answer for X seconds) than "what has happened" (e.g., a TCP connection was reset). Keep in mind that, in general, the request for the URL you type in the browser may succeed, but the browser may get stuck getting some resource on that page. You may limit captures to TCP and DNS traffic to and from Squid. Finally, for the future, [if you cannot isolate the problem to one HTTP transaction(*),] it is best to capture everything that Squid receives or sends rather than trying to guess what the browser and Squid will receive or send -- according to cache.log, there were lots of Squid-server packets that your tcpdump configuration did not capture. Thank you, Alex. P.S. (*) Entering a regular page URL in the browser usually results in more than one HTTP transaction between the browser and Squid. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
