From: Yaroslav H. <li...@on...> - 2012-01-24 23:17:12
|
so it shows consistently for you on both 2.6.5 and 2.6.6... for me on Debian, with your locale settings and python 2.6.6-8+b1 (so there is a few patches on top of pristine 2.6.6) I did not spot any oddity in the the log file, BUT my logline looks like 2012-01-24 18:01:48,955 fail2ban.actions: WARNING [ssh] Ban 129.170.XX.XX vs your Jan 24 09:01:32 hostname <U+FEFF><28>fail2ban.actions: WARNING [jail] Ban 127.0.0.2 aha -- you must be using SYSLOG logtarget? (that is why we ask to reveal configuration right away ;-) ), but even with SYSLOG it looks like Jan 24 18:13:06 hostname fail2ban.actions: WARNING [apache-badbots] Ban 180.76.XX.XX so nope -- can't reproduce... but so -- what happens if you switch from syslog to custom log file (e.g. /var/log/fail2ban.log)? also it could be the syslog which you use..., so it might be not even fail2ban or python at fault -- errorneous characters right at the beginning of the line f2b provides: # Syslog daemons already add date to the message. formatter = logging.Formatter("%(name)-16s: %(levelname)-6s %(message)s") hm, could it also be an effect of having -16 indentation? what if you remove -16? On Tue, 24 Jan 2012, Mario Witte wrote: > > Good point, I hadn't checked so far. It's python 2.6.6 versus 2.6.5 on > > the machines that work. > > I cannot do a downgrade as the old package isn't available anymore, > > but I'll try updating one of the other machine to see if the problem > > show up there as well. > The error is also showing on the machine where I updated python, so it > seems to be a problem with python 2.6.6, at least on RHEL6. Can anybody > confirm that the problem is not showing up on python 2.6.6 with a > different distro? -- =------------------------------------------------------------------= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic |