From owner-freebsd-questions Fri Jun 23 10:49:52 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id E59E837B551 for ; Fri, 23 Jun 2000 10:49:33 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id MAA17936; Fri, 23 Jun 2000 12:48:00 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 23 Jun 2000 12:47:59 -0500 (CDT) From: Chris Dillon To: Mauricio Westendorff Pegoraro Cc: "freebsd-questions@FreeBSD.ORG" Subject: Re: SQUID question - Urgent! In-Reply-To: <39539D40.A92EF4B1@pucrs.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Jun 2000, Mauricio Westendorff Pegoraro wrote: > Hi. > > Does anyone knows whats the following squid error means? > > 2000/06/23 14:20:23| comm_open: socket failure: (55) No buffer space > available > 2000/06/23 14:20:23| comm_open: socket failure: (55) No buffer space > available > 2000/06/23 14:20:24| comm_open: socket failure: (55) No buffer space > available > 2000/06/23 14:20:24| comm_open: socket failure: (55) No buffer space > available > 2000/06/23 14:20:24| comm_open: socket failure: (55) No buffer space > available > 2000/06/23 14:20:24| comm_open: socket failure: (55) No buffer space > available > 2000/06/23 14:20:25| comm_open: socket failure: (55) No buffer space > available > 2000/06/23 14:20:25| comm_open: socket failure: (55) No buffer space > available > 2000/06/23 14:20:25| comm_open: socket failure: (55) No buffer space > available > 2000/06/23 14:20:25| comm_open: socket failure: (55) No buffer space > available > > I didn't found anything like this in Squid's site. > My machine is 4.0 FreeBSD, running Squid 2.3. It's a 128MB memory > Pentium III. I don't think this is actually Squid's problem. What does netstat -m say when this is occurring? I've only ever seen this happen one time, on my mail server using a 3COM 3C509 (Etherlink III), and when it did no communication with anything was possible. The only way I could solve the problem was to use ifconfig to bring the link down and then back up. I'm not sure if it was really a network card or driver problem, but bringing the link down and back up probably triggered something in the kernel that set things straight. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message