On 11/20/2018 9:49 AM, Mike Schleif wrote:
What am I missing?
More than likely, you have a message coming across the wire with a
errant character in it, that when pushed to MySQL causes the error
you're seeing. The question is, what does that message look like, what
character is causing the problem, and then what kind of setup you can do
to strip that errant character. The previous suggestions are to attempt
to find those messages.
All of those events to be sent to the database are also going to
/var/log/secure.
What is the purpose of this rsyslog-debug.log?
Will this "debug output" rsyslog-debug.log be in _addition_ to regular
logfiles, or replace my current configuration?
Depends on your entire configuration and the placement of the action.
The goal would be to add a debug file, that may contain the problem
message, so you can then move forward with a technical fix.
We currently have ~10 different logfiles - if this debug configuration
replaces the original, won't that concatenate all logs into one file?
I'd suggest you pick a file name that isn't used, so it doesn't
*replace* anything.
_______________________________________________
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.
