-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fail2ban 0.9.6 stopped working on CentoOS 6.8 after timezone update to tzdata2017c #1959
Comments
Please try verbose variant: fail2ban-regex -vvv /var/log/maillog /etc/fail2ban/filter.d/dovecot.conf Then you'll be able to see the date-time, fail2ban has really recognized. Please see also #1804 (comment)
Please note that fail2ban will ban only failures occurred |
Ok, I extracted some fails from huge maillog...
and run the fail2ban-regex on that list...
the find time is 5 mins.. and maxretry is 3 ... so is should have triggered..
but the #1804 brought me to something: 2017-11-06 **14:52:51,**149 fail2ban.datedetector [10477]: DEBUG Got time 1509983571.000000 for "u'Nov 6 13:52:51'" using template (?:DAY )?MON Day 24hour:Minute:Second(?:.Microseconds)?(?: Year)? so the de time of the fail2ban log and the detected time really differ in 1 hour. |
Problem solved !!
the logs are now on the correct hour...
|
Glad you've found it. Thus let close the issue... |
I used fail2ban 0.9.4 until October 17 2017 without issues.
Coincidence or not, on October 17th I updated the tzdata to 2017b due to daylight savings time switch, and after this, fail2ban stopped working.
tzdata changed from the previous version the way the timezone is displayed ( now -02 instead of BRT / BRST ).
I rolled back to a 2016 version, without change.
Now I updated again to the last available for the rather old distro ( tzdata 2017c and fail2ban 0.9.6 now )
What happens is that no login attempts get detected anymore.
fail3ban-regex for Dovecot for example shows 3980 hits...:
and this is the output from the client:
no failed logins get detected.
I already tried the DEBUG option, but the output is really huge, not sure where to look at.
I also tried to force backends ( polling and gamin ) no change either.
Any clues ?
The text was updated successfully, but these errors were encountered: