Confirmed (using stop && rm -r && start and also using reload). After
creating
$ sudo mkdir /var/run/fail2ban
as suggested it works.
Very annoying is that fail2ban does not seam to be very talkative
(except when log level 4 -- 3 is default -- AND everything going well;
failure -> not even anything in log!) and nothing to shell (except when
reloading insted of stop && start):
*********************************************
$ sudo /etc/init.d/fail2ban stop
## from fail2ban.log:
## 2008-05-17 15:35:21,369 fail2ban.server : DEBUG Removed socket file
/var/run/fail2ban/fail2ban.sock
## 2008-05-17 15:35:21,369 fail2ban.server : DEBUG Socket shutdown
$ ll /var/run/fail2ban -d
drwxr-xr-x 2 root root 40 2008-05-17 15:01 /var/run/fail2ban
$ ll /var/run/fail2ban
total 0
$ sudo rm -r /var/run/fail2ban
$ sudo /etc/init.d/fail2ban start
## note: not even does it say nothing but this returns 0!
## nothing in fail2ban.log
$ sudo ls -l /var/run/fail2ban
ls: cannot access /var/run/fail2ban: No such file or directory
$ sudo mkdir /var/run/fail2ban
$ sudo /etc/init.d/fail2ban start
## note: same output as when failing!
## from fail2ban.log:
## 2008-05-17 15:35:21,369 fail2ban.server : DEBUG Socket shutdown
## 2008-05-17 15:51:38,580 fail2ban.comm : DEBUG Command: ['add',
'apache-noscript', 'gamin']
## 2008-05-17 15:51:38,582 fail2ban.jail : INFO Using poller
## 2008-05-17 15:51:38,600 fail2ban.filter : INFO Created Filter
## ... heaps more :)
$ sudo ls -l /var/run/fail2ban/
total 4
-rw-r--r-- 1 root root 6 2008-05-17 15:08 fail2ban.pid
srwx------ 1 root root 0 2008-05-17 15:08 fail2ban.sock
$ sudo ls -l /var/run/fail2ban/ -d
drwxr-xr-x 2 root root 80 2008-05-17 15:08 /var/run/fail2ban/
*********************************************
Btw, takes ages to fail starting -- necessary?:
$ time sudo /etc/init.d/fail2ban start
real 0m30.630s
user 0m0.536s
sys 0m0.068s
$ time sudo /etc/init.d/fail2ban restart
* Restarting authentication failure monitor fail2ban
...fail! # note: that's all there is to notify.
# At first I laught at it and thought "funny people, confirming by
# saying 'fail!' as if to say 'Let's kick ass' refering to package
name :)
real 0m30.744s
user 0m0.648s
sys 0m0.080s
And even normal start-up, well:
$ time sudo /etc/init.d/fail2ban start
real 0m2.071s
user 0m0.692s
sys 0m0.072s
System:
$ uname -a
Linux amd64.nimm.merseine.nu 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC
2008 i686 GNU/Linux
$lsb_release -dcs
Ubuntu 8.04
hardy
$ apt-cache policy fail2ban
fail2ban:
Installed: 0.8.2-2
Candidate: 0.8.2-2
Version table:
*** 0.8.2-2 0
500 http://de.archive.ubuntu.com hardy/universe Packages
100 /var/lib/dpkg/status
** Changed in: fail2ban (Ubuntu)
Status: New => Confirmed
--
fail2ban will not start if fail2ban socket is present
https://bugs.launchpad.net/bugs/123916
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
