Slash is not valid inside hostname,so the heuristic concludes no hostname and end of header.
Rg Sent from phone, thus brief. Jacob Steinberger <[email protected]> hat geschrieben: Syslog-ng 1.68, rsyslog 3.22.1 I'm in the process of setting up a new environment that's pure rsyslog and something more current than 3.22.1 ... but in the mean time put your old thinking caps back on as I've stumbled into a rather old installation! Syslog-ng is the current receptor for traffic. I'm forwarding those messages to rsyslog. When rsyslog gets them ... they don't look right. I've tried mucking with templates and regular expressions to reformat the message but that's taking a while and thought there might be an existing solution that I'm missing. Rsyslog rawmsg looks like thus: <133>Aug 28 14:45:41 local/hostnamebob notice syslog[tag]: message Rsyslog goes further to print out using the traditional templates like thus: August 28 14:45:41 relayhostname local/hostnamebob notice syslog[tag]: message Looks like syslog-ng is chaining, rsyslog doesn't like it and thinks its all part of the message. Is there an easy template fix to this? It's been a while since I've been able to work with rsyslog so I feel like I'm missing something quite obvious. Jacob _______________________________________________ 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 _______________________________________________ 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
