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". If I
> remove that file and then do "/etc/init.d/fail2ban start" the error
interesting... the fact that sock file is left is ok (ie feature not a
bug) but why it doesn't start after you remove the socket file --
that is interesting ;-)
> 2008-08-26 11:45:18,901 fail2ban.server : INFO Starting Fail2ban v0.8.3
> 2008-08-26 11:45:18,909 fail2ban.server : INFO Starting in daemon mode
> And then fail2ban-server is present in the process list, but no enties in the
> log file.
that is ok -- since fail2ban-client has to 'populate' the server with
rules etc
after you started it manually you can try to do
fail2ban-client reload
and see if there is any 'effect'
On Tue, 26 Aug 2008, Stefan Carslöv wrote:
> 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.
--
Yaroslav Halchenko
Research Assistant, Psychology Department, Rutgers-Newark
Student Ph.D. @ CS Dept. NJIT
Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171
101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102
WWW: http://www.linkedin.com/in/yarik
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
