Bug 520536 – =net-analyzer/fail2ban-0.9.0-r1 - WARNING Wrong value for 'loglevel' in 'Definition'. Using default one: ''INFO'' in log

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Fabio Scaccabarozzi 2014-08-22 12:29:33 UTC]

This is due to a bug in the way the conf file parser reads fail2ban.conf.
It expects an "int" when in fact the documentation says it should be a "string".
This has already been fixed upstream in the following issue:
https://github.com/fail2ban/fail2ban/issues/657

Reproducible: Always

Steps to Reproduce:
1. emerge fail2ban
2. start fail2ban
3.
Actual Results:  
Even the default value that comes with the config file produces the warning:
WARNING Wrong value for 'loglevel' in 'Definition'. Using default one: ''INFO'' in log

Expected Results:  
fail2ban should correctly read the provided value.

Attached is the patch that fixes the issue, I had to rebuild it as the original from github didn't apply cleanly.
It should not be necessary to maintain it for versions later than 0.9.0, as it is already queued for the 0.9.1 release.

[Comment 1 Fabio Scaccabarozzi 2014-08-22 12:30:05 UTC]

Created attachment 383368 [details, diff]
Fix loglevel to expect a string instead of an int

[Comment 2 Jeroen Roovers (RETIRED) 2014-08-22 15:13:12 UTC]

We could be patching 0.9.0 forever. They should really release a new version by now.

[Comment 3 Jeroen Roovers (RETIRED) 2014-08-22 15:16:06 UTC]

Fixed in -r2.