Well, the template violates syslog format. I think this will be logged as Kern.=emergency
But i may be wrong. To see what's going on, add *.* /var/log/debug.log; RSYSLOG_DebugFormat To the receivers config. Post it's content. Rainer Sent from phone, thus brief. Am 23.04.2014 21:38 schrieb "Brian Huntington" <[email protected] >: > Thanks so much for the prompt reply, > > Logs transfer works just fine to remote log server when using "local.* > @<IP>:514" without a template, so I know there are no firewall issues. The > logging only stops when I modify the client configuration to use a > template, > as described in my previous post. > > The remote log server is configured for UDP, like so: > # UDP Syslog Server: > $ModLoad imudp.so # provides UDP syslog reception > $UDPServerRun 514 # start a UDP syslog server at standard port 514 > > Thanks again > > > > -- > View this message in context: > http://rsyslog-users.1305293.n2.nabble.com/imfile-templates-tp7585270p7585272.html > Sent from the rsyslog-users mailing list archive at Nabble.com. > _______________________________________________ > 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. > _______________________________________________ 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.
