From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 27 18:01:48 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 272D516A434 for ; Mon, 27 Mar 2006 18:01:48 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 518AE43D46 for ; Mon, 27 Mar 2006 18:01:46 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.13.4/8.13.3) with ESMTP id k2RI1gNW088645; Mon, 27 Mar 2006 22:01:42 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Mon, 27 Mar 2006 22:01:42 +0400 (MSD) From: Maxim Konovalov To: "Michael W. Lucas" In-Reply-To: <20060327173841.GA58274@bewilderbeast.blackhelicopters.org> Message-ID: <20060327214209.U87890@mp2.macomnet.net> References: <20060327160130.GA57689@bewilderbeast.blackhelicopters.org> <20F3E06D-5727-4531-A81B-DF64765D1564@SARENET.ES> <20060327173841.GA58274@bewilderbeast.blackhelicopters.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 18:01:48 -0000 On Mon, 27 Mar 2006, 12:38-0500, Michael W. Lucas wrote: > On Mon, Mar 27, 2006 at 06:18:50PM +0200, Borja Marcos wrote: > > >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. That's not enough. You need to teach syslogd to use this new value. > > >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. > > I've disabled syslog to the console, writing instead to > /var/log/console.log. > > Moments after doing that, the problem reoccured. Thanks, Borja, but > no success. :-( > > Any other suggestions, folks? What's the incoming udp datagrams rate? netstat -sp udp | grep 'datagrams received'; sleep 10; \ netstat -sp udp | grep 'datagrams received' How much cpu time does syslogd use? -- Maxim Konovalov