From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 27 16:18:53 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92F0316A422 for ; Mon, 27 Mar 2006 16:18:53 +0000 (UTC) (envelope-from BORJAMAR@SARENET.ES) Received: from smtp1.sarenet.es (smtp1.sarenet.es [194.30.0.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3340043D46 for ; Mon, 27 Mar 2006 16:18:52 +0000 (GMT) (envelope-from BORJAMAR@SARENET.ES) Received: from [127.0.0.1] (borja.sarenet.es [192.148.167.77]) by smtp1.sarenet.es (Postfix) with ESMTP id 5E0E289; Mon, 27 Mar 2006 18:18:51 +0200 (CEST) In-Reply-To: <20060327160130.GA57689@bewilderbeast.blackhelicopters.org> References: <20060327160130.GA57689@bewilderbeast.blackhelicopters.org> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <20F3E06D-5727-4531-A81B-DF64765D1564@SARENET.ES> Content-Transfer-Encoding: 7bit From: Borja Marcos Date: Mon, 27 Mar 2006 18:18:50 +0200 To: "Michael W. Lucas" X-Mailer: Apple Mail (2.746.3) Cc: hackers@freebsd.org Subject: Re: syslogd not draining X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2006 16:18:53 -0000 > I've got a machine running syslogd, DNS, DHCP, flow-capture, and other > assorted UDP-loving programs. Occasionally, they all stop working. > The machine has been up for a couple of hours now, and I see: > > ns1/etc;netstat -s | grep full > Warning: sysctl(net.inet6.ip6.rip6stats): No such file or directory > 122066 dropped due to full socket buffers > ns1/etc; > > I've doubled kern.ipc.maxsockbuf a couple of times now, and yet it > still happens. > > After some help from questions@, I'm pretty sure that the culprit is > syslogd. > > udp4 0 0 *.67 *.* > udp4 43414 0 *.514 *.* > udp4 0 0 *.49661 *.* Are you using a serial console? I had similar problems in the past due to the serial port flow control. Borja.