In fail2ban.log I see some lines like this:
WARNING Error decoding line from '/somewhere/mysqld.log' with 'utf-8'.
Consider setting logencoding=utf-8
I've added logencoding=utf-8 or logencoding = "utf-8" but it's not working,
I still see those WARNING line and the problem is that they are extremely
long. It's filling 13 MB of data in /var/log/fail2ban.log about every 5
minutes.
Doing a file -bi /somewhere/mysqld.log do show it is an utf-8 file.
I don't want to set the loglevel of fail2ban at CRITICAL or ERROR.
This error comes from:
/lib/python2.7/site-packages/fail2ban/server/filter.py
at line 806:
" to process line ignoring invalid characters: %r" %
I tried removing the %r but it's not crashing with a traceback. So I tried
removing the %r and the % at the end but crashing again.
I don't have much experience in python, I'd just like to remove the long
line in the log file. Actually it would be better to have the logencoding
option to work but in the meantime I just need a quick fix :)
Thanks for any help!
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine
_______________________________________________
Fail2ban-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fail2ban-users
