From owner-freebsd-questions@FreeBSD.ORG Thu Mar 22 09:52:18 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 799DF106564A for ; Thu, 22 Mar 2012 09:52:18 +0000 (UTC) (envelope-from mark@exonetric.com) Received: from relay0.exonetric.net (relay0.exonetric.net [178.250.72.161]) by mx1.freebsd.org (Postfix) with ESMTP id 3B86C8FC2C for ; Thu, 22 Mar 2012 09:52:18 +0000 (UTC) Received: from [172.16.0.139] (94-30-105-106.xdsl.murphx.net [94.30.105.106]) by relay0.exonetric.net (Postfix) with ESMTP id 1BCCE5701F; Thu, 22 Mar 2012 09:52:23 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=us-ascii From: Mark Blackman In-Reply-To: Date: Thu, 22 Mar 2012 09:52:15 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <4C89080E-48D3-4C6C-8945-227713769E91@exonetric.com> References: To: Traiano Welcome X-Mailer: Apple Mail (2.1257) Cc: freebsd questions Subject: Re: FreeBSD: syslog-ng: I/O error occurred while writing; fd='xx', error='No buffer space available (yy)' X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2012 09:52:18 -0000 On 22 Mar 2012, at 09:00, Traiano Welcome wrote: >=20 >=20 > My question is: What does this error mean, and how can I resolve it? =46rom a very casual inspection of the problem, I'd say you're pushing = out syslog messages faster than the kernel can get them out the interface. How many syslog messages are going in (per second) and what kind of network interface are you trying to send them out through? >=20 > I have tried to frame this as an operating system kernel resource = issue, > and experimented with increasing the freebsd kernel sysctls for UDP > performance: I think you can push nmbclusters up to about 600k, but if your input is running faster than your output, no amount of buffering will permanently stave off this problem. - Mark