-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Philipp, On Tue, 18 Sep 2007 14:50:54 +0200 Philipp Rusch <philipp.rusch@xxxxxxxxxxxxxxx> wrote: > Sorry to bother you, but I don't get it. > > We have a SuSE 10.1 system and have our www-traffic going through squid. > Since upgrade from 2.5 to version 2.6 STABLE5-30 (SuSE versions) we notice > that Squid is behaving strange. After running normally a while Squid seems > to go "DIRECT" only and the browsers on the clients seem to hang and or > surfing is ultra slow. This is happening every three or four websites we > try > to access, it seems to work normal for one or two, then the next four or > five > GETs are very slow again and the circle begins again. > In /var/logs/Squid/access.log I see that most of the connections are going > DIRECT, sometimes we get connection timeouts (110) and sometimes we > see that "somehow" an :443 is added to the URL-lines. STRANGE. > Any hints appreciated. Since you upgraded from version 2.5 to 2.6, your squid.conf must have changed too. Do you have a local caching DNS server running in your Squid box? Posting your squid.conf and output of "squidclient mgr:info" and "squid -v" might help. If you have large ACLs, then squid might be busy processing them rather than serving web requests! Are you running Squid transparently and do you also have parent caches? What does cache.log say? Maybe upgrading to the latest stable version of Squid might help? Check out the URL below: http://www.squid-cache.org/Versions/v2/2.6/squid-2.6.STABLE16.tar.gz Thanking you... > > Regards from Germany, > Mit freundlichen Grüßen > Philipp Rusch > > - -- With best regards and good wishes, Yours sincerely, Tek Bahadur Limbu System Administrator (TAG/TDG Group) Jwl Systems Department Worldlink Communications Pvt. Ltd. Jawalakhel, Nepal http://wlink.com.np/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFG79f5fpE0pz+xqQQRAlVdAJ45QFZ6PjL2BWASWa8DboE644PkMwCfR84p F44uMq9jzryGBiHCt7sC8a0= =brq1 -----END PGP SIGNATURE-----
