On 22 Mar 2012, at 11:40, Traiano Welcome wrote:
That's what I thought as well, but it's the details that evade me. Almost
all traffic to and from this server is UDP (syslog), the graph I sent
earlier shows the kind of volumes and trends that are typical: Peak
traffic during the problem
Hi Mark
On 22/03/2012 13:54, Mark Blackman m...@exonetric.com wrote:
On 22 Mar 2012, at 11:40, Traiano Welcome wrote:
That's what I thought as well, but it's the details that evade me.
Almost
all traffic to and from this server is UDP (syslog), the graph I sent
earlier shows the kind of
On 23 Mar 2012, at 08:58, Traiano Welcome wrote:
Hi Mark
On 22/03/2012 13:54, Mark Blackman m...@exonetric.com wrote:
On 22 Mar 2012, at 11:40, Traiano Welcome wrote:
Somehow this doesn't strike me as a large volume of throughput Š
Ok, fair enough. You might try simulating the
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
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
On 22 Mar 2012, at 09:00, Traiano Welcome wrote:
My question is: What does this error mean, and how can I resolve it?
From 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
Hi Mark
On 22/03/2012 11:52, Mark Blackman m...@exonetric.com wrote:
On 22 Mar 2012, at 09:00, Traiano Welcome wrote:
My question is: What does this error mean, and how can I resolve it?
From a very casual inspection of the problem, I'd say you're pushing out
syslog messages faster
