Bug#443287: amavisd-new: BDB bugs will stop amavis mail delivery
Package: amavisd-new Version: 1:2.4.2-6.1 Severity: normal Berkeley DB often has problems with lockers. This will stop the mail deliver on systems with amavisd-new enabled. The bug will only appear if db_enabled is set to a true value, which is the default setting at the debian package. After disabling the berkeley db with $enable_db = 0; $enable_global_cache = 0; the errors disappeared. The performance will not decrease appreciably. Thus I would recommend to disable this settings in the package default. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages amavisd-new depends on: ii adduser 3.102 Add and remove users and groups ii debconf [debconf-2.0]1.5.11 Debian configuration management sy ii file 4.17-5etch2 Determines file type using magic ii libarchive-tar-perl 1.30-2 Archive::Tar - manipulate tar file ii libarchive-zip-perl 1.16-1 Module for manipulation of ZIP arc ii libberkeleydb-perl 0.31-1 use Berkeley DB 4 databases from P ii libcompress-zlib-perl1.42-2 Perl module for creation and manip ii libconvert-tnef-perl 0.17-5 Perl module to read TNEF files ii libconvert-uulib-perl1.06-1 Perl interface to the uulib librar pn libdigest-md5-perl none (no description available) ii libio-stringy-perl 2.110-2 Perl5 modules for IO from scalars ii libmailtools-perl1.74-1 Manipulate email in perl programs pn libmime-base64-perl none (no description available) ii libmime-perl 5.420-0.1 Perl5 modules for MIME-compliant m ii libnet-server-perl 0.94-1 An extensible, general perl server ii libunix-syslog-perl 0.100-5 Perl interface to the UNIX syslog( ii perl [libtime-hires-perl]5.8.8-7 Larry Wall's Practical Extraction ii perl-modules [libnet-perl] 5.8.8-7 Core Perl modules ii postfix [mail-transport-agen 2.3.8-2+b1 A high-performance mail transport amavisd-new recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443287: amavisd-new: BDB bugs will stop amavis mail delivery
Martin Werthmoeller schrieb am Donnerstag, den 20. September 2007: Package: amavisd-new Version: 1:2.4.2-6.1 Severity: normal Berkeley DB often has problems with lockers. This will stop the mail deliver on systems with amavisd-new enabled. The bug will only appear if db_enabled is set to a true value, which is the default setting at the debian package. After disabling the berkeley db with $enable_db = 0; $enable_global_cache = 0; the errors disappeared. The performance will not decrease appreciably. Thus I would recommend to disable this settings in the package default. I don't this that this qualifys as a bug, so I will lower the severity to wishlist for this bug. Alex P.S.: in fact switching off bdb makes amavis significant faster, so I will think about it. On the other hand is changing the default behaviour of a server a serious thing where all pros and cons should be calculated carefully. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443287: amavisd-new: BDB bugs will stop amavis mail delivery
On Thu, 20 Sep 2007, Alexander Wirt wrote: P.S.: in fact switching off bdb makes amavis significant faster, so I will think about it. On the other hand is changing the default behaviour of a server a serious thing where all pros and cons should be calculated carefully. bdb requires that we properly configure its environment. I think amavis kills the bdb environment and re-creates it at every start, so it *must* configure the environment... So, yes, there might be a real misfeature in there. Are we setting the cache and locker region size to our real needs? Something to ask upstream, I suppose. Note that this depends on the number of maximum threads, but since we *do* know that number, we should tweak the bdb environment as needed. Notes about bdb environments: - changes only take effect on initial creation and db_recover - OpenLDAP seems to have the very best description of how to configure, so a search on openldap lists and docs will find some good stuff. a bdb environment. BDB documentation is... of poor quality here. - a DB_CONFIG file is the usual way to configure environments, but the BDB API has a set of calls you could use *before creating the environment* to set the parameters, as well. - the above is just some knowlege I gathered from maintaining cyrus imapd for so long, and keeping a close eye on openldap. Unfortunately, I don't know how to *really* properly program for BDB :) -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
