Hi, I’m running rsyslogd 8.17.0 from the adiscon yum repo on CentOS 7. Forwarding logs successfully via TLS over TCP. Same versions on client that is forwarding the logs and on the central server that is receiving them. Everything works fine until I reboot the client. The rsyslogd process starts up, no diagnostics in the logs, stores log messages on local disk just fine, but doesn’t forward them to the remote server. ss -a shows no connection to the server. If I then stop and start the rsyslogd process, it immediately forwards the logs that had queued up and continues to work perfectly. ss -a shows the tcp connection, and I can watch the logs get logged locally on the client and arrive immediately on the server.
Does this sound familiar to anyone? I spent the evening trying to boot the system with rsyslogd in debug mode but wasn’t able to figure out a way to do it - probably too tired to think straight. Thanks in advance for any hints you might care to offer. Happy to send config files etc. Hoping for an “Oh, yeah, -that- problem” response… …Mark _______________________________________________ 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.
