Bug#554162: fail2ban: sometimes(frequently) fails to load ..

External Since: Mar 27, 2006 Posts: 2

Package: fail2ban
Version: 0.8.4-1
Severity: important

Hi,
I have problems with using several jails. It was there before, but didn't hit so hard as today, when i was unable to restart fail2ban cleanly , i was trying it for maybe 50 times (changing configs, installing python2.4 ...etc).
I seems to fail to execute iptables in correct orderd leading to something like this in its output

-----
iptables: Resource temporarily unavailable.
iptables: No chain/target/match by that name.
iptables v1.4.4: Couldn't load target `fail2ban-proftpd':/lib/xtables/libipt_fail2ban-proftpd.so: cannot open shared object file: No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
2009-11-03 14:29:14,591 fail2ban.actions.action: ERROR iptables -N fail2ban-proftpd
iptables -A fail2ban-proftpd -j RETURN
iptables -I INPUT -p tcp -m multiport --dports ftp,ftp-data,ftps,ftps-data -j fail2ban-proftpd returned 200
-----
Seems like last rule is executed when chain is not ready

This problem is reported upstream, i think
http://sourceforge.net/tracker/?func=detail&aid=2870788&group_id=12103...tid=689

With patch
http://sourceforge.net/tracker/?func=detail&aid=2857096&group_id=12103...tid=689

Patch applies fine and seems to help, but I have to use
action = %(action_)s

instead of action_m
action_m = %(banaction)s[name=%(__name__)s, port="%(port)s", protocol="%(protocol)s]
%(mta)s[name=%(__name__)s, dest="%(destemail)s", protocol="%(protocol)s]
action = %(action_m)s

or provided
action = %(action_mw)s

With regards
Libor

-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.29-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF- Cool

Shell: /bin/sh linked to /bin/bash

Versions of packages fail2ban depends on:
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
ii python 2.5.4-2 An interactive high-level object-o
ii python-central 0.6.11 register and build utility for Pyt

Versions of packages fail2ban recommends:
ii iptables 1.4.4-2 administration tools for packet fi
ii whois 4.7.32 an intelligent whois client

Versions of packages fail2ban suggests:
ii bsd-mailx [mailx] 8.1.2-0.20081101cvs-2 A simple mail user agent
pn python-gamin <none> (no description available)

-- no debconf information

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST.TakeThisOut@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster.TakeThisOut@lists.debian.org

External Since: Nov 22, 2006 Posts: 81

brr... are you sure you just have some problem with iptables? what if
whenever there is no fail2ban running you run those commands while being
root

iptables -N fail2ban-proftpd
iptables -A fail2ban-proftpd -j RETURN
iptables -I INPUT -p tcp -m multiport --dports ftp,ftp-data,ftps,ftps-data -j fail2ban-proftpd

will you get at some point that
iptables v1.4.4: Couldn't load target `fail2ban-proftpd':/lib/xtables/libipt_fail2ban-proftpd.so: cannot open shared object file: No such file or directory

or would be there any other error reported?

On Tue, 03 Nov 2009, Libor Klepac wrote:

> Package: fail2ban
> Version: 0.8.4-1
> Severity: important

> Hi,
> I have problems with using several jails. It was there before, but didn't hit so hard as today, when i was unable to restart fail2ban cleanly , i was trying it for maybe 50 times (changing configs, installing python2.4 ...etc).
> I seems to fail to execute iptables in correct orderd leading to something like this in its output

--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]

--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST RemoveThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster RemoveThis @lists.debian.org