On 2015-07-06 23:11:27 -0400, Yaroslav Halchenko wrote: > On Tue, 07 Jul 2015, Vincent Lefevre wrote: > > The problem is that fail2ban doesn't offer any protection at all > > because it fails silently. So, instead of possibly having one thing > > broken, one has everything broken!!! There should be a way for the > > user to know (without any special action on his part) that fail2ban > > could not start. > > brr -- didn't you get a log stating that it failed to start and a reason > for the failure stated (as you quoted above)?
This is only in the logs. The user isn't supposed to look at the logs each time he boots his machine to check whether some service has refused to start by design. If the goal of the failure is that the user can notice it, then there should be a clear notification in one of the usual methods (e.g. the same behavior when a cron command fails, which is usually a mail). > > > As a workaround you might like to configure your logrotation to > > > re-create empty files (create configuration option in your logrotate > > > configs). > > > apache2 isn't installed yet, so that it would not be possible. > > so disable that jail then! But this means that when I install apache2, I will need to remember to enable it. And if I remove apache2 (and the logs, then useless), I will need to remember to disable this jail again, otherwise fail2ban will start to fail silently again. -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
