search

debops / ansible-fail2ban

Install and configure fail2ban service
GNU General Public License v3.0
38 stars 14 forks source link

Log level #18

Open bleuchtang opened 7 years ago

bleuchtang commented 7 years ago

I think this commit broke fail2ban configuration: https://github.com/debops/ansible-fail2ban/commit/d56c36031bf9afa637cdee32480e7730cfc7bc34

According to journalctl when I restart: Mar 09 12:26:56 XXX fail2ban[31387]: Starting authentication failure monitor: fail2banWARNING Wrong value for 'loglevel' in 'Definition'. Using default one: '1

In debian jessie fail2ban.conf says:

# Option: loglevel
# Notes.: Set the log level output.
#         1 = ERROR
#         2 = WARN
#         3 = INFO
#         4 = DEBUG
# Values: [ NUM ]  Default: 1

When I setup 3 instead of WARNING, fail2ban start normally. It seems depend of the fail2ban's version. This is just a warning, Fail2ban start in any case.

drybjed commented 7 years ago

What fail2ban version are you using? Is the usage of codewords instead of numbers the correct one going forward (Jessie+)?

bleuchtang commented 7 years ago

I'm using debian jessie fail2ban version: 0.8.13-1 It seem that the switch from String to Int appear in 0.9.x: https://github.com/fail2ban/fail2ban/issues/657