From owner-freebsd-questions Tue Jan 18 11:19:49 2000 Delivered-To: freebsd-questions@freebsd.org Received: from luke.cpl.net (luke.cpl.net [192.216.136.195]) by hub.freebsd.org (Postfix) with ESMTP id E5E7D150FA for ; Tue, 18 Jan 2000 11:18:26 -0800 (PST) (envelope-from shawn@megadeth.org) Received: from shawn (firewall.cpl.net [192.216.87.251] (may be forged)) by luke.cpl.net (8.9.3/8.9.3) with ESMTP id LAA06185; Tue, 18 Jan 2000 11:18:22 -0800 (PST) Message-Id: <4.2.0.58.20000118111336.01c767f0@mail.cpl.net> X-Sender: megadeth@mail.cpl.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 18 Jan 2000 11:17:25 -0800 To: Gary Jennejohn From: Shawn Ramsey Subject: Re: No buffer space? Cc: Jim Conner , questions@FreeBSD.ORG In-Reply-To: <200001180950.KAA87899@peedub.muc.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:50 AM 1/18/00 +0100, Gary Jennejohn wrote: >Shawn Ramsey writes: > >AHow much memory do you have? How much swap space you have available? > > > > > >Plenty of both... 198MB of RAM and about 320MB of swap space. > > > >This message usually means that queued packets are not going out the >interface. If you ``ifconfig down'' followed by ``ifconfig up'' the >interface the queued packets will be discarded - easier than doing a >reboot. > >IMHO this indicates that you have a problem with your hardware (NIC, hub, >switch, what have you). > >This shows up alot with ISDN, that's why I know about it. Ok... will try the easiest first. Will replace the primary NIC and cable and see what happens. If it was a bad switch, wouldn't other systems exist the same problem? This server is really the only really loaded server on the network though, so if it is traffic dependant, maybe not. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message