[rsyslog-notify] Forum Thread: Re: filter invalid syslogtag - (Mode 'reply')

[noreply at adiscon.com]

User: dlang 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=26735#p26735

Message: 
----------
I think I see what's happening here. the position that the syslogtag is
supposed to be in has garbage in in it (`<87>....) rsyslog starts parsing
it and for some reason accepts the `, but decides that < is not a valid
character as a programname/syslogtag, so it makes that part of the message.

you had the same problem on the client side (the prior post I referenced).
the debug output thereshows that it came from inputname: imuxsock so it's
not reading from a file. It's a case that something that's writing to
/dev/log is doing it wrong, and from the contents of the message, it looks
like jboss

The other possibility is that you coudl be running across the message
corruption bug that caused us to fork json-c. But I only saw those problems
on $! variables, not on the core ones.