Hi Stefan,
Could you please check once again either you keep experiencing this
issue you have reported long time ago? May be it is gone by now and I
could close this bugreport ;)
since last 2 years, there even was a new upstream release ;)
Thanks in advance
On Wed, 03 Sep 2008, Stefan wrote:
hard to figure out in all the config files if they are just in a list
(not in original directory structure targzipped for instance) but it
seems that fail2ban.conf/jail.conf wasn't even changed, and only
jail.local has modifications (the way it should be)
Oh, sorry about that. I've attached a
Package: fail2ban
Version: 0.8.3-1
Severity: important
fail2ban fails to start.
To do some testing I reinstalled it afther I had removed and purged the
package. but it didn't help.
The log-file is completely empty. Log level 4 (debug) doesn't help either. It's
still empty.
If I do
very interesting -- could we start with loglevel = 4 in fail2ban.conf
and send resultant fail2ban.log along with your configuration (full
/etc/fail2ban would be the best)
If I do /etc/init.d/fail2ban restart I get a message stating that
/var/run/fail2ban/fail2ban.sock is present, and a Failed.
hard to figure out in all the config files if they are just in a list
(not in original directory structure targzipped for instance) but it
seems that fail2ban.conf/jail.conf wasn't even changed, and only
jail.local has modifications (the way it should be)
So -- fail2ban-server is crashing. Could
5 matches
Mail list logo
