-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
understanding fail2ban log level #2008
Comments
Since v.0.10 you can use both forms of log-level (so numeric also). Duplicate of #1968 |
@sebres ,
I'm I right with this statement ? Thanks for the clarifications |
It looks indeed so, but according to the code it was another "numeric" [0..3]. |
OK, then it would be summarized like this:
Source: Matth |
Environment:
The issue:
I don't understand, what log level format Fail2ban is expecting, seems to be both...
Basically if I set the log level with a numeric the config is refused and got the error message above,
but if I use string to set the log level (ERROR, WARNING, NOTICE, INFO, DEBUG) everything works properly.
My understanding is that fail2ban is supporting both format in the
fail2ban.conf
file but this is not what I'm experiencing.Steps to reproduce
In /etc/fail2ban/fail2ban.conf set
loglevel = 1
Expected behavior
I'm expecting to see only the ERROR message showing up in
fail2ban.log
Observed behavior
On
fail2ban-client reload
I got an error messageERROR NOK: ('Invalid log level',)
Any additional information
This is impacting a 3rd party tool (Webmin #742) to setup fail2ban.
Not 100% sure if it's a fail2ban issue or Debian package maintainer issue...
fail2ban config reader is expecting string #657 not sure if it as an impact here...
Configuration, dump and another helpful excerpts
Any customizations done to /etc/fail2ban/ configuration
This config is not working, see
loglevel
This config is working properly
Relevant parts of /var/log/fail2ban.log file:
When loglevel is set to **1 **
When log level is set to INFO
Thanks for any input
Kind regards
Matth
The text was updated successfully, but these errors were encountered: