Tell me more ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.
up vote 0 down vote favorite

fail2ban does not start at boot, and I can't start it either by:

1.- sudo service fail2ban restart, which shows:

* Restarting authentication failure monitor fail2ban [fail]

or

2.- sudo service fail2ban start, which shows nothing at all.

Nothing is logged to /var/log/fail2ban.log in any case

This has happened after I reinstalled it (from Synaptic), since I wanted default jails and configs back.

Any hint?

share|improve this question
Have you completely removed fail2ban configuration in /etc? – enzotib Jul 6 '11 at 17:50
No, it's all there – luri Jul 6 '11 at 17:54
Of course after reinstall it is there, what I mean is "you completely removed then installed again?". Only in this way you can be sure nothing of the old configuration is left around. – enzotib Jul 6 '11 at 17:57
Ok, sorry... no I just simply reinstalled.... but the old config was working fine... I might have changed some file just prior to reinstall... Going to check that – luri Jul 6 '11 at 18:09
1  
Yes... But I swear I can't recall how I managed to solve it. If I recall correctly, something was messed up with my config, and not with fail2ban default configuration. I would even say it had to do with long names I had given to some custom jails. – luri Mar 15 '12 at 8:28
show 1 more comment

closed as too localized by fossfreedom♦ Mar 23 '12 at 18:45

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, see the FAQ.

Browse other questions tagged or ask your own question.