Hi all, I have run into a remote logging issue with rsyslog-7.4.7 on Centos7 platform. With my setup, all logs are forwarded to central log server with syslog RFC5424-5425 and everything works fine, until the client system is rebooted. When the system boots, rsyslog fails to establish a connection to the central log server and starts to buffer messages on disk. Nevertheless, when rsyslog is restarted manually shortly after reboot, connection is established successfully. After troubleshooting this issue a bit, I have found that the root cause is a temporary short-term failure in name resolution -- for some reason, DNS-based name resolution is not working for few seconds during the boot, and thus rsyslog is not able to resolve the DNS name of the central log server. As a workaround, I have defined the IP->logserver_hostname mapping in /etc/hosts file, and this has resolved the issue.
I have nevertheless the following question -- is it possible to configure another workaround with rsyslog configuration file statements? I have tried the "$ActionResumeInterval 30" option, but apparently it does not force rsyslog to retry connection 30 seconds after the initial failure. Are there any other workarounds I could try with rsyslog? Kind regards, risto _______________________________________________ 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.
