On Tue, 3 Feb 2015, Rainer Gerhards wrote:
If you like, I can craft a patch for you (quickly done) that emits exact
errors on each send. But it's pretty specific, so before doing even a
trivial patch, let's see if that work would be useful at all...
Interesting... I got curios which error code this is. So I tried
strerror() on those that looked valid to me. This is the result:
ENOBUFS: No buffer space available
ENOMEM: Cannot allocate memory
Maybe it's a good idea to output the errno itself into the message. This
may be clearer... I'll craft a patch for that and would suggest that you
apply it before testing.
that would help. the current error is so generic that it doesn't point at
anything.
The patch can be seen in this PR:
https://github.com/rsyslog/rsyslog/pull/243
it is again master-candidate, but should apply against v8.7.0 as well. It
would be great if you could try it out, as I don't have a system where I
get into that situation, so I cannot really test it...
I'll give it a try, outside of about one hour last night I haven't seen the
problem before or since :-(
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
