On Monday 10 December 2007 03:03:26 you wrote: > Çäðàâñòâóéòå, ian. > > Âû ïèñàëè 8 ??????? 2007 ?., 2:32:33: > > On Friday 07 December 2007 11:54:45 Tek Bahadur Limbu wrote: > >> Hi nix_kot, > >> > >> nix_kot wrote: > >> >> Hello, squid-users. > >> >> > >> >> In my cache.log very many such messages > > >> >> > >> >> 2007/12/06 08:44:37| commBind: Cannot bind socket FD 7703 to *:0: > >> >> (49) Can't assign requested address > >> >> 2007/12/06 08:44:37| commBind: Cannot bind socket FD 7703 to *:0: > >> >> (49) Can't assign requested address > >> >> 2007/12/06 08:44:38| commBind: Cannot bind socket FD 7697 to *:0: > >> >> (49) Can't assign requested address > >> >> 2007/12/06 08:44:38| commBind: Cannot bind socket FD 7697 to *:0: > >> >> (49) Can't assign requested address > >> >> 2007/12/06 08:49:10| comm_accept: FD 80: (53) Software caused > >> >> connection abort 2007/12/06 08:49:10| httpAccept: FD 80: accept > >> >> failure: (53) Software caused connection abort 2007/12/06 08:50:03| > >> >> parseHttpRequest: Unsupported method '..CONNECT' 2007/12/06 08:50:03| > >> >> clientReadRequest: FD 103 Invalid Request > >> >> 2007/12/06 08:52:31| sslReadServer: FD 91: read failure: (54) > >> >> Connection reset by peer > >> >> > >> >> I don't know, that is it. > >> >> Squid restarted after per minutes. > >> >> Users message in browser on the opening page: Can't assign requested > >> >> address > >> > >> You seem to be running out of file descriptors or mbufs. > >> > >> >> And in this time squid load all Processor (80-90%). > >> > >> Use the latest version of Squid which is Squid-2.6.17. It's very CPU > >> friendly. > >> > >> > >> http://www.squid-cache.org/Versions/v2/2.6/squid-2.6.STABLE17.tar.gz > >> > >> > squid 2.5 stable12 > >> > freebsd 4.11 > >> > > >> > Please help me!!!! > >> > >> Try increasing your file descriptors and mbufs. > > > > I ran 4.11 up to mid Feb this year. Don't have cache logs that far back. > > > > IIRC I had to tune nmbclusters (32768). > > > > If it's this you should be seeing > > /kernel: All mbuf clusters exhausted, please see tuning(7). > > in /var/log/messages > > > > What does "netstat -m" say? > > netstat -m > 355/5360/32768 mbufs in use (current/peak/max): > 303 mbufs allocated to data > 52 mbufs allocated to packet headers > 291/5122/8192 mbuf clusters in use (current/peak/max) > 11584 Kbytes allocated to network (47% of mb_map in use) > 0 requests for memory denied > 0 requests for memory delayed > 0 calls to protocol drain routines > > in /var/log/messages nothing So it looks like nmbclusters is already tuned, and you didn't hit the limit for mbufs or clusters. I would say mbufs are not the issue. Never had to tune files but sysctl -a | grep files would seem to be a good place to start. kern.maxfiles: 12328 kern.maxfilesperproc: 11095 kern.openfiles: 318 p1003_1b.mapped_files: 1 HTH -- ian j hart
