Your message dated Mon, 16 Jan 2006 14:49:51 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#334430: fixed in postgrey 1.24-1
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; 17 Oct 2005 20:30:20 +0000
>From [EMAIL PROTECTED] Mon Oct 17 13:30:20 2005
Return-path: <[EMAIL PROTECTED]>
Received: from frotz.zork.net [70.85.129.199]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1ERbch-0006YS-00; Mon, 17 Oct 2005 13:30:19 -0700
Received: by frotz.zork.net (Postfix, from userid 1000)
id F1E1E1175E; Mon, 17 Oct 2005 13:30:16 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Nick Moffitt <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: postgrey runs away with CPU in mad spin if ancillary database files are
corrupted
X-Mailer: reportbug 3.8
Date: Mon, 17 Oct 2005 13:30:15 -0700
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: postgrey
Version: 1.21-1
Severity: normal
Lately my system has noticed runaway postgrey processes. The symptoms
are that on startup, the lone postgrey process consumes 80-95% of the
CPU. Strace ends with the following:
open("/var/lib/postgrey/__db.001", O_RDWR|O_LARGEFILE) = 6
fcntl64(6, F_SETFD, FD_CLOEXEC) = 0
mmap2(NULL, 16384, PROT_READ|PROT_WRITE, MAP_SHARED, 6, 0) = 0x4056e000
close(6) = 0
When I ran the strace of postgrey as above, but with --dbdir=/tmp/ it
started just fine. Moving all files but the postgrey.db out of
/var/lib/postgrey also solves the problem.
What appears to have happened is that an emergency reboot caused some of
the ancillary database files (the log or the __db.00? files) to become
corrupted in some maner that confused postgrey on startup.
A friend of mine noticed that he used to see this behavior in slapd
(which is not in Perl) suggesting that this was a berkeleydb problem.
Poking in his slapd init scripts he found the following:
12:14 <npmr> i noticed that as of sarge, the openldap initscript runs
db4.2-recover before starting the daeon
12:15 <npmr> looks like there's a try_fix_db bash function in there
12:15 <npmr> about a page of code
12:15 <npmr> very tidy looking
12:15 <npmr> and then this in the start) clause:
12:15 <npmr> if [ "$TRY_BDB_RECOVERY" = "yes" ]; then
12:15 <npmr> try_fix_db
12:15 <npmr> fi
It may be helpful to try this technique in postgrey's init scripts.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.12.3-linode14
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages postgrey depends on:
ii debconf 1.4.30.13 Debian configuration management sy
ii libberkeleydb-perl 0.26-3 use Berkeley DB 4 databases from P
ii libnet-dns-perl 0.48-1 Perform DNS queries from a Perl sc
ii libnet-server-perl 0.87-3 An extensible, general perl server
ii perl 5.8.4-8 Larry Wall's Practical Extraction
ii ucf 1.17 Update Configuration File: preserv
-- debconf information:
postgrey/1.13-5_move-db:
postgrey/1.14-1_lookup-by-subnet:
postgrey/1.13-5_old-config:
---------------------------------------
Received: (at 334430-close) by bugs.debian.org; 16 Jan 2006 22:57:01 +0000
>From [EMAIL PROTECTED] Mon Jan 16 14:57:00 2006
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
id 1EydAd-00014m-Oj; Mon, 16 Jan 2006 14:49:51 -0800
From: Adrian von Bidder <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.65 $
Subject: Bug#334430: fixed in postgrey 1.24-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Mon, 16 Jan 2006 14:49:51 -0800
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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 3
Source: postgrey
Source-Version: 1.24-1
We believe that the bug you reported is fixed in the latest version of
postgrey, which is due to be installed in the Debian FTP archive:
postgrey_1.24-1.diff.gz
to pool/main/p/postgrey/postgrey_1.24-1.diff.gz
postgrey_1.24-1.dsc
to pool/main/p/postgrey/postgrey_1.24-1.dsc
postgrey_1.24-1_all.deb
to pool/main/p/postgrey/postgrey_1.24-1_all.deb
postgrey_1.24.orig.tar.gz
to pool/main/p/postgrey/postgrey_1.24.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian von Bidder <[EMAIL PROTECTED]> (supplier of updated postgrey package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Mon, 16 Jan 2006 21:17:19 +0100
Source: postgrey
Binary: postgrey
Architecture: source all
Version: 1.24-1
Distribution: unstable
Urgency: low
Maintainer: Adrian von Bidder <[EMAIL PROTECTED]>
Changed-By: Adrian von Bidder <[EMAIL PROTECTED]>
Description:
postgrey - greylisting implementation for Postfix
Closes: 320487 334430 342464
Changes:
postgrey (1.24-1) unstable; urgency=low
.
* The "Let's Actually Do Something For Debian Today" Release
* new upstream version:
- don't use DB_TXN_NOSYNC (causes hangs - closes: #334430)
- --privacy option (closes: #320487)
- netsolmail was added to the whitelist (closes: #342464)
(thanks to David Schweikert for solving all my problems)
Files:
0bd6316849c8b488d33f9c8076db59d4 678 mail optional postgrey_1.24-1.dsc
db11f4da47ee28252cf2ddd160308d7e 27444 mail optional postgrey_1.24.orig.tar.gz
7535a98f402946a7cba7940d7eb742b8 9799 mail optional postgrey_1.24-1.diff.gz
4a4d6ba00efff3ab5cff78cdc762c5fe 40846 mail optional postgrey_1.24-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: get my key from http://fortytwo.ch/gpg/92082481
iEYEARECAAYFAkPMA/0ACgkQi6Qxi+Wn99Y/0wCgspR89m2hPEZ1kUcbwRpIOqA5
ahsAn0TZ0IBQVnS36H+TezesIU2P7fhw
=1sOP
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
