I also just got a snippet of their client config and realized that
they're using the (o) option with the tcp action (per the rsyslog tls
doc's suggestion I suppose). Given all your disclaimers in
http://www.rsyslog.com/doc/rsyslog_conf_actions.html ... I wonder if the
errors would go away if they removed that. Heh. In any case, it doesn't
really matter -- this is all academic. They'll update the clients to
rsyslog5 when rhel5.9 comes out and we'll go from there.
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.
