Thanks for your response Rainer!
While we haven't been able to reproduce the issue in house at all, going
through the report from my customer, I did notice that all the instances
of the error were due to rsyslog3 clients restarting and he just came
back with a definitive data point: restarting 40+ rsyslog5 clients
simultaneously didn't generate any of the errors.
As for rsyslog v7: I'd love to get people using it. We're looking at it
internally, but I have no idea when the Powers That Be are going to be
willing to rebase (we're only releasing v5 for rhel5 with the upcoming
5.9 point release and rhel6 only got it with 6.3) ... as you perhaps
know, Fedora isn't even using it yet. :(
All the best!
On 12/12/2012 06:06 AM, Rainer Gerhards wrote:
There has been a lot of work and bug fixes since these versions, especially in
the TLS area. I'd suggest to upgrade at least the server (should be sufficient)
to 7.2.4. Chances are good the problem will go away. But the issue may also be
rooted with the clients.
Rainer
_______________________________________________
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.
