Description of problem:

startup and shutdown showed up errors in logs.

Version-Release number of selected component (if applicable):

fail2ban-0.8.3-19.fc11.noarch
iptables-1.4.3.1-1.fc11.x86_64
iptables-ipv6-1.4.3.1-1.fc11.x86_64

How reproducible:

Always

Steps to Reproduce:

1. install fail2ban
2. start/stop fail2ban
3. tail -f /var/log/fail2ban.log
  
Actual results:

on start:

==> fail2ban.log <==
2009-06-25 23:06:06,265 fail2ban.server : INFO   Changed logging target to /var/log/fail2ban.log for Fail2ban v0.8.3
2009-06-25 23:06:06,266 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,267 fail2ban.jail   : INFO   Creating new jail 'ssh-iptables'
2009-06-25 23:06:06,269 fail2ban.jail   : INFO   Jail 'ssh-iptables' uses Gamin
2009-06-25 23:06:06,290 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,291 fail2ban.filter : INFO   Added logfile = /var/log/secure
2009-06-25 23:06:06,292 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,292 fail2ban.filter : INFO   Set maxRetry = 5
2009-06-25 23:06:06,293 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,294 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,295 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,295 fail2ban.filter : INFO   Set findtime = 600
2009-06-25 23:06:06,296 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,296 fail2ban.actions: INFO   Set banTime = 86400
2009-06-25 23:06:06,297 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,302 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,308 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,313 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,320 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,327 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,335 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,344 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,352 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,353 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,353 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,354 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,354 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,355 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,356 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,356 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,357 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,357 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,358 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,359 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,359 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,360 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,360 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,361 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,361 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,362 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,362 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:06,363 fail2ban.jail   : INFO   Jail 'ssh-iptables' started
2009-06-25 23:06:06,376 fail2ban.server : ERROR  Unexpected communication error
2009-06-25 23:06:07,401 fail2ban.filter : WARNING Unable to find a corresponding IP address for 2001:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX
2009-06-25 23:06:07,431 fail2ban.filter : WARNING Unable to find a corresponding IP address for 2001:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX
2009-06-25 23:06:07,809 fail2ban.filter : WARNING Unable to find a corresponding IP address for 2001:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX
2009-06-25 23:06:07,812 fail2ban.filter : WARNING Unable to find a corresponding IP address for 2001:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX
2009-06-25 23:06:07,813 fail2ban.filter : WARNING Unable to find a corresponding IP address for 2001:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX

on stop:

2009-06-25 23:06:14,895 fail2ban.jail   : INFO   Jail 'ssh-iptables' stopped
Exiting Fail2ban
cannot release un-aquired lock
Traceback (most recent call last):
  File "/usr/bin/fail2ban-server", line 126, in start
    self.__server.start(self.__conf["socket"], self.__conf["force"])
  File "/usr/share/fail2ban/server/server.py", line 98, in start
    logSys.info("Exiting Fail2ban")
  File "/usr/lib64/python2.6/logging/__init__.py", line 1033, in info
    self._log(INFO, msg, args, **kwargs)
  File "/usr/lib64/python2.6/logging/__init__.py", line 1141, in _log
    self.handle(record)
  File "/usr/lib64/python2.6/logging/__init__.py", line 1151, in handle
    self.callHandlers(record)
  File "/usr/lib64/python2.6/logging/__init__.py", line 1188, in callHandlers
    hdlr.handle(record)
  File "/usr/lib64/python2.6/logging/__init__.py", line 664, in handle
    self.release()
  File "/usr/lib64/python2.6/logging/__init__.py", line 618, in release
    self.lock.release()
  File "/usr/lib64/python2.6/threading.py", line 136, in release
    raise RuntimeError("cannot release un-aquired lock")
RuntimeError: cannot release un-aquired lock

Expected results:

no erros in log. Maybe ignore ipv6 addresses and a hint, that ipv6 is currently not supported.

Additional info:

none.