Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Mar 2012 19:47:33 +1000
From:      Da Rock <freebsd-questions@herveybayaustralia.com.au>
To:        freebsd-questions@freebsd.org
Subject:   Re: FreeBSD: syslog-ng: I/O error occurred while writing; fd='xx', error='No buffer space available (yy)'
Message-ID:  <4F6AF535.9010302@herveybayaustralia.com.au>
In-Reply-To: <CB90B6BA.DD17%traiano.welcome@mtnbusiness.co.za>
References:  <CB90B6BA.DD17%traiano.welcome@mtnbusiness.co.za>

next in thread | previous in thread | raw e-mail | index | archive | help
On 03/22/12 19:00, Traiano Welcome wrote:
> Hi List
>
> I've been seeing the following in the messages log of my freebsd syslog
> server for quite some time now:
>
> ---
> Mar 20 12:19:12 syslog2 syslog-ng[35313]: I/O error occurred while
> writing; fd='12', error='No buffer space available (55)'
> Mar 20 12:19:12 syslog2 syslog-ng[35313]: Connection broken;
> time_reopen='60'
> Mar 20 12:19:12 syslog2 syslog-ng[35313]: I/O error occurred while
> writing; fd='13', error='No buffer space available (55)'
> Mar 20 12:19:12 syslog2 syslog-ng[35313]: Connection broken;
> time_reopen='60'
> ---
>
> These happen at a frequency of about 7 per minute on average. See attached
> trend graphs for an idea of the volume of traffic we're doing, as well as
> the memory and cpu utilisation trends on this server during this period.
> As can be seen from the graphs, load does not seem to be the issue.
> Occasionally during the week, the system freezes and requires a reboot, I
> think it's related to the above message, though I'm not sure.
>
> My question is: What does this error mean, and how can I resolve it?
>
> I have tried to frame this as an operating system kernel resource issue,
> and experimented with increasing the freebsd kernel sysctls for UDP
> performance:
>
> ---
> [root@syslog2<mailto:root@syslog2.ops.mtnbusiness.co.za>  /var/log]#
> sysctl kern.ipc.nmbclusters=102400
> kern.ipc.nmbclusters: 25600 ->  102400
>
> [root@syslog2<mailto:root@syslog2.ops.mtnbusiness.co.za>  /var/log]#
> sysctl kern.ipc.maxsockbuf=201326592
> kern.ipc.maxsockbuf: 100663296 ->  201326592
>
> [root@syslog2<mailto:root@syslog2.ops.mtnbusiness.co.za>  /var/log]#
> sysctl net.inet.udp.recvspace=33554432
> net.inet.udp.recvspace: 16777216 ->  33554432
> ---
>
> This has reduced the frequency of the errors a little, but in general the
> problem still remains.
>
> Syslog version:
>
> --
> [root@syslog2]# syslog-ng -V
> syslog-ng 2.0.10
>
> --
>
> FreeBSD version:
>
> --
> FreeBSD 7.2-STABLE #0
> --
>
> Any help would be much appreciated!
I'm sorry I can't shed some light on a solution, but this happens on 
ping and some other network related apps and tools for me too; just not 
often enough for me concern with atm due to higher priorities.

Perhaps net@ might be a better resource for an answer to this one?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F6AF535.9010302>