Re[2]: [vps-mail] Question

[Abigail Marshall <webmaster@xxxxxxxxxxxx>]

SW> On Mon, Sep 15, 2003 at 10:08:23PM -0700, Abigail Marshall wrote:

SW> The DB_File that comes with your VPS should be adequate. When did you
SW> begin to get locking problems?

Consistently.  It seems to particularly get to be a problem
when the bayes_toks file grows to 5k or more.  I've lost
Bayes database at least 4 times. (Usually able to restore
with getback - however the point is that the database
regularly becomes corrupted and needs to be replaced).

SW> You may want to try serializing your pipe through spamassassin if
SW> you're not already:

SW>     :0 fw: spamassassin.lock
SW>     |/usr/local/bin/spamassassin

Running spamd:


:0fw
|/usr/local/bin/spamc -p 1783 -s 75000


Should this be changed to:

:0fw spamassassin.lock
|/usr/local/bin/spamc -p 1783 -s 75000

(I thought with the daemon, the messages would be queued in
any event, since there is only one instance running)


SW> If things work
SW> after doing this, then you're definitely getting contention in the DB
SW> and the SA locking mechanism is not adequate. I noticed an interesting
SW> comment in the SA code:

SW>   if ($main->{learn_wait_for_lock}) {
SW>     $tout = 300;        # TODO: Dan to write better lock code
SW>   } else {
SW>     $tout = 10;
SW>   }

LOL. It definitely is an sa-learn issue - actually I
reported it as a bug to Spamassassin, because I can tell
already from debugging that if sa-learn encounters an error
(inability to access file, time out or out of memory), it
will go right ahead and continue it's processes, overwriting
data - whereas it really should create a temporary copy of
files and simply abort and restore the temp file if any sort
of error is encountered.

-Abigail

SW> Right after this chunk is one of two possible places your error might
SW> be occuring. Apparently it's a known issue (we call that a tell-tale
SW> comment) and may be fixed in the next stable release. Cross your
SW> fingers.

SW> Scott

======================================================================
Technical questions regarding this list may be sent to
<vps-mail-owner@xxxxxxxxxxxx>. You may request an automated help
response by sending an email with the word 'help' (w/o quotes) in the
BODY of the message (subject is ignored) to <vps-mail-request@xxxxxxxxxxxx>.
======================================================================