SA Bugzilla – Bug 303
[Debian 143321] Database locking problems?
Last modified: 2002-05-10 10:39:55 UTC
From: Radim Kolar <hsn@cybermail.net> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: spamassassin: problems with reliability and auto-whitelist Date: Wed, 17 Apr 2002 19:01:05 +0200 Package: spamassassin Version: 2.11-4 Severity: normal We are running spamd -a -d here and we are experience constant problems with auto-whitelisting feature. It looks like some locking problem (all filesystems mounted are local). After use auto-white list grows to some bigger size - about 200-300 KB per user. spamd in better case ignores all autowhitelist entries or locks up. Deleting user-whitelist helps. So problem is that ndbm files which are in use as db hash by Perl default gets corrupted. My wish item is to change spamassassin code to use db2 or db3 which should be more reliable. -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux home 2.4.18 #1 Wed Apr 10 14:43:06 CEST 2002 i586 Locale: LANG=C, LC_CTYPE=C Versions of packages spamassassin depends on: ii dpkg 1.9.19 Package maintenance system for Deb ii perl 5.6.1-7 Larry Wall's Practical Extraction ii perl-modules 5.6.1-7 Core Perl modules.
bash2.05 craig@balam ~/.spamassassin % file auto-whitelist.db auto-whitelist.db: Berkeley DB Hash file (Version 2, Big Endian, Bucket Size 4096, Bucket Shift 12, Directory Size 256, Segment Size 256, Segment Shift 8, Overflow Point 1, Last Freed 2, Max Bucket 1, High Mask 0x3, Low Mask 0x1, Fill Factor 40, Number of Keys 4) Perhaps you should just make your Perl use the DB system you want as its default for AnyDB_File?