Hello folks!
So one of my customers has configured 100+ rsyslog 5.8.10 & rsyslog
3.22.1 clients to log to a 5.8.10 server with TLS.
Sometimes when rsyslog is restarted on the clients, the server gets the
above netstream session errors. We've confirmed the messages are only
caused by rsyslog restarting by adding a bit of debug code, resulting in
output like the following:
> Dec 4 09:51:08 server rsyslogd: inst-debug: netstream session
0x7f867459af60 comes from peer 10.0.0.1.
> Dec 4 09:51:08 server rsyslogd-2078: netstream session
0x7f867459af60 will be closed due to error
> [try http://www.rsyslog.com/e/2078 ]
> Dec 4 09:51:08 server rsyslogd: inst-debug: netstream session
0x7f86742d6250 comes from peer 10.0.0.2.
> Dec 4 09:51:08 server rsyslogd-2078: netstream session
0x7f86742d6250 will be closed due to error
> [try http://www.rsyslog.com/e/2078 ]
Looking at the code, I understand that this is just the default result
when something unexpected happens with TLS, and I don't expect that
they're ever loosing messages (obviously if rsyslog restarts the TCP
connection has to be closed and reopened), but I just wanted to take a
moment to run this by people more experienced and more knowledgeable
than I -- any thoughts?
Thanks for taking the time to read!
Ryan Sawhill
_______________________________________________
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.
