On Fri, 28 Feb 2014, Tanky Woo wrote:
A few days before, Some machines I just deployed all have problems, the rsyslog is running, but can’t log to file.I change a little in configuration, the main config is: *.* @syslog.xxx.com:514 And others (include Main Queue) use default configuration. Because syslog.xxx.com is our intra domain, and resolve by our name server , the vpn is not running, so can’t resolve this domain, and just block the queue. Then I started openvpn, and it just wait, can’t write to log caused it also blocked. I add syslog.xxx.com to /etc/hosts. and restart openvpn, the openvpn and rsyslog is ok. Now I want to imitate the situation that day, but I can’t. Does anyone now how to imitate the queue blocked in rsyslog, my version is 5.8.6?
add an iptables rule that blocks outbound port 514 to the destination syslog.xxx.com. that should cause things to back up.
David Lang
_______________________________________________ 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.
