Now it seems to be another kind of problem. I see a lot of such
messages in fail2ban.log :
2006-03-24 03:16:02,585 ERROR: Please check the format and your locale settings.
2006-03-24 03:16:02,586 ERROR: time data did not match format: data=Mar 24
03:16:02 fmt=%b %d %H:%M:%S
2006-03-24 03:16:02,587 ERROR: Please check the format and your locale settings.
2006-03-24 03:16:02,588 ERROR: time data did not match format: data=Mar 24
03:16:02 fmt=%b %d %H:%M:%S
2006-03-24 03:16:02,588 ERROR: Please check the format and your locale settings.
2006-03-24 03:16:05,588 ERROR: time data did not match format: data=Mar 19
06:47:08 fmt=%b %d %H:%M:%S
I think my syslog locale is C or POSIX, but my user/application
locale is uk_UA.UTF-8 (set in ~/.bash_profile). May be it had
impacted fail2ban when I restarted it from the command line ? I
see this locale is present in /proc/N/environ of running fail2ban
process.
Just add
export LANG=C
to the initial statements in /etc/init.d/fail2ban. WFM.
Willi
This worked for me too :)
--
Ce message a été vérifié par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a été trouvé.
MailScanner remercie transtec pour son soutien.