Hello, Our rsyslog processes are crashing frequently since we switched to RELP from TCP.
Some of the common messages seen are: omrelp[10.10.10.5:11514]: error 'TLS record write failed [gnutls error -53: Error in the push function.]', object 'conn to srvr 10.10.10.5:11514' - action may not work as intended [v8.2408.0 try https://www.rsyslog.com/e/2353 ] omrelp[10.10.10.5:11514]: error 'io error in RawSendCommand, session broken', object 'conn to srvr 10.10.10.5:11514' - action may not work as intended [v8.2408.0 try https://www.rsyslog.com/e/2353 ] librelp error 10007[connection broken] forwarding to server 10.10.10.5:11514 - suspending [v8.2408.0 try https://www.rsyslog.com/e/2291 ] action 'action-1-omrelp' suspended (module 'omrelp'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2408.0 try https://www.rsyslog.com/e/2007 ] But these do not result in a crash 100% of the time, sometimes a few seconds after the above messages we get the following from systemd. rsyslog.service: Main process exited, code=exited, status=1/FAILURE syslog.service: Failed with result 'exit-code'. Seeing these on v8.2408.0 rockylinux8. Any ideas for troubleshooting? Debug logging option suggestions maybe? Thankyou -- Mehmet _______________________________________________ rsyslog mailing list https://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.
