On Wed, Apr 30, 2008, Usrbich wrote: > > In cache.log, all I get is this messages: > 2008/04/30 23:58:25| clientReadRequest: FD 121 (10.19.14.58:2014) Invalid > Request > 2008/04/30 23:58:25| clientReadRequest: FD 112 (10.19.14.58:2013) Invalid > Request > 2008/04/30 23:58:37| clientReadRequest: FD 170 (10.19.13.54:1317) Invalid > Request > 2008/04/30 23:58:38| clientReadRequest: FD 121 (10.19.20.55:1235) Invalid > Request > 2008/04/30 23:58:41| clientReadRequest: FD 169 (10.19.13.54:1318) Invalid > Request > 2008/04/30 23:58:41| clientReadRequest: FD 169 (10.19.13.54:1319) Invalid > Request > 2008/04/30 23:58:50| clientReadRequest: FD 126 (10.19.15.55:1662) Invalid > Request > > Is that the cause of my timeout problem? It'd be ncie to know what that is, but no, that in itself shouldn't hang browsing activities. > Is this startup output ok? > Memory usage for squid via mallinfo(): > total space in arena: 13768 KB > Ordinary blocks: 13023 KB 265 blks > Small blocks: 0 KB 5 blks > Holding blocks: 244 KB 1 blks > Free Small blocks: 0 KB > Free Ordinary blocks: 744 KB > Total in use: 13267 KB 95% > Total free: 745 KB 5% Well, squid is using bugger all memory then. Debugging this will require a little more effort.. you will probably have to begin by fiddling with your server stats and determine what else is going on. You may want to run the system call tracer on Squid to see what its doing when it slows down to see whats going on. This sort of stuff is precisely why I suggest people graph as much about their Squid servers as they can! Adrian -- - Xenion - http://www.xenion.com.au/ - VPS Hosting - Commercial Squid Support - - $25/pm entry-level VPSes w/ capped bandwidth charges available in WA -
