Your message dated Wed, 26 Oct 2005 12:29:30 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closed in the recent dupload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 16 Oct 2005 18:15:51 +0000
>From [EMAIL PROTECTED] Sun Oct 16 11:15:51 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp02.mrf.mail.rcn.net [207.172.4.62]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1ERD31-0001jD-00; Sun, 16 Oct 2005 11:15:51 -0700
Received: from 65-78-16-168.c3-0.nwt-ubr2.sbo-nwt.ma.cable.rcn.com (HELO spike)
([65.78.16.168])
by smtp02.mrf.mail.rcn.net with ESMTP; 16 Oct 2005 14:15:50 -0400
X-IronPort-AV: i="3.97,220,1125892800";
d="scan'208"; a="133065846:sNHT21583968"
Received: from ralph by spike with local (Exim 4.50)
id 1ERD30-0000ru-EE; Sun, 16 Oct 2005 14:15:50 -0400
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Ralph Katz <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: fail2ban: returned ERROR 256 from iptables
X-Mailer: reportbug 3.12
Date: Sun, 16 Oct 2005 14:15:50 -0400
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: fail2ban
Version: 0.5.4-5
Severity: normal
Sometimes on start, this error appears in /var/log/fail2ban:
2005-10-16 11:37:03,376 WARNING: Verbose level is 1
2005-10-16 11:37:03,387 INFO: Fail2Ban v0.5.4 is running
2005-10-16 11:37:03,408 INFO: Enabled sections: ['SSH']
2005-10-16 11:37:03,584 ERROR: 'iptables -N fail2ban-ssh
iptables -I INPUT -p tcp --dport ssh -j fail2ban-ssh
iptables -A fail2ban-ssh -j RETURN' returned 256
And:
/etc/init.d/fail2ban status
Status of fail2ban: fail2ban is running.
But:
iptables -L of course shows the absence of the fail2ban lines.
Or on exit:
2005-10-15 23:11:05,258 WARNING: Restoring firewall rules...
2005-10-15 23:11:05,355 ERROR: 'iptables -D INPUT -p tcp --dport ssh -j
fail2ban-ssh
iptables -D fail2ban-ssh -j RETURN
iptables -X fail2ban-ssh' returned 256
2005-10-15 23:11:05,356 INFO: Exiting...
Firestarter firewall is also installed.
This is on sarge. No change from v0.5.3.
Regards,
Ralph
-- System Information:
Debian Release: 3.1
APT prefers stable
APT policy: (800, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-2-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages fail2ban depends on:
ii iptables 1.2.11-10 Linux kernel 2.4+ iptables adminis
ii python 2.3.5-2 An interactive high-level object-o
-- no debconf information
---------------------------------------
Received: (at 334272-done) by bugs.debian.org; 26 Oct 2005 16:30:01 +0000
>From [EMAIL PROTECTED] Wed Oct 26 09:30:01 2005
Return-path: <[EMAIL PROTECTED]>
Received: from washoe.rutgers.edu [165.230.95.67]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EUoA5-0007yE-00; Wed, 26 Oct 2005 09:30:01 -0700
Received: from yoh by washoe.rutgers.edu with local (Exim 4.52)
id 1EUo9a-0005Xp-5S
for [EMAIL PROTECTED]; Wed, 26 Oct 2005 12:29:30 -0400
Date: Wed, 26 Oct 2005 12:29:30 -0400
From: Yaroslav Halchenko <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: closed in the recent dupload
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="HAv5+T9jbwMPl6Kw"
Content-Disposition: inline
X-URL: http://www.onerussian.com
X-Image-Url: http://www.onerussian.com/img/yoh.png
X-PGP-Key: http://www.onerussian.com/gpg-yoh.asc
X-fingerprint: 3BB6 E124 0643 A615 6F00 6854 8D11 4563 75C0 24C8
User-Agent: mutt-ng/devel-r472 (Debian)
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
--HAv5+T9jbwMPl6Kw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Bug was closed in the recent upload, changes of which didn't make it to
close the bug:
fail2ban (0.5.4-7) unstable; urgency=3Dlow
* Adjusted init.d script so it is resistant to delayed shutdowns of
fail2ban and in general more stable
-- Yaroslav Halchenko <[EMAIL PROTECTED]> Thu, 20 Oct 2005 21:22:03 -=
0400
fail2ban (0.5.4-6.2) unstable; urgency=3Dlow
* Fixed typos (thanx to Ross Boylan).
* Robust startup: if iptables module gets fully initialized after
startup of fail2ban, fail2ban will do "maxreinit" attempts to
initialize its own firewall. It will sleep between attempts for
"polltime" number of seconds (closes: #334272).
* To overcome possible conflict with other firewall solutions and as a
secondary solution for the bug 334272, fail2ban startup is moved
during bootup to the latest (S99) sequenece position. That should not
cause any discomfort I believe.
-- Yaroslav Halchenko <[EMAIL PROTECTED]> Tue, 18 Oct 2005 15:54:38 -=
0400
--=20
.-.
=3D------------------------------ /v\ ----------------------------=3D
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
--HAv5+T9jbwMPl6Kw
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFDX67pjRFFY3XAJMgRAiBIAJ9eMFK6qhJswVObzEX6/CHR15cINACeJATg
jSpPCspIg0Pc9qoBvQUC8D8=
=Kesg
-----END PGP SIGNATURE-----
--HAv5+T9jbwMPl6Kw--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
