Home > Cannot Open > Cannot Open Bayes Databases /root/.spamassassin/bayes_* R/w Lock Failed

Cannot Open Bayes Databases /root/.spamassassin/bayes_* R/w Lock Failed

expired old Bayes database entries in 661 seconds 145343 entries kept, 455855 deleted :-)) Best regards Martin -- Martin Schröder, ms [at] artcom-gmbh ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice at /Library/Perl/5.8.6/Mail/SpamAssassin/BayesStore/DBM.pm line 195.locker: safe_unlock: lock on /var/clamav/.spamassassin/bayes.lock was lost due to expiry at /Library/Perl/5.8.6/Mail/SpamAssassin/Locker/UnixNFSSafe.pm line 196.Learned new HAM (not junk mail)Syncing SpamAssassin DatabaseDisplaying SpamAssassin Database Stats0.000 0 7733 0 non-token SA, by default, uses a bayes directory in the home directory of whatever user invokes SA. However, your problem is not related to this setting. this contact form

Note: the warnings in the SA docs about not honoring bayes_path in user_prefs only seems to apply to spamd. Here are other services related to the installation I completed following the howtoforge tutorials mentioned before. Many years ago Matt wrote this post that describes it: http://lists.mailscanner.info/pipermail/mailscanner/2004-November/043067.html"In short, a mutex is a MUTual EXclusion. Please Note: this e-mail address is only for reporting problems with SA Bugzilla.

S 19:28 0:02 MailScanner: waiting for messages postfix 11246 0.1 0.5 77744 49316 ? Results 1 to 2 of 2 Thread: bayes: cannot open bayes databases Thread Tools Show Printable Version Email this Page… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode Comment 7 Andrey Melnikov 2010-04-20 06:52:00 UTC In my case - SHORTCIRCUIT plugin is involved. Comment 4 Bart Schaefer 2006-06-28 00:08:23 UTC This still happens with 3.0.6, though more rarely.

In this instance I would expect sa-learn to wait until spamd finished, then lock the database and proceed. We are using SA with spampd with maxchildren set to 25. Here's what > >/var/spool/spamassassin looked like a few minutes ago: > > opportunistic expiry. > > > mkettler at evi-inc May11,2004,1:55PM Post #4 of 19 (11483 views) Permalink Re: Bayes database [In reply Are you using Selinux or something similar?

is bayes_seen necessary ? (i seem to recall it is not and can be deleted) if bayes_seen is large, isnt that the file we can delete and it will not make Use this one instead: http://svn.apache.org/repos/asf/spamassassin/trunk/sql/bayes_mysql.sql I'm also having problems with the AWL instructions from that document. Usage instructions are included in the script. dig this How do I remove the database?

One exception is if you use spamd, it will NEVER scan mail as root, and if it finds spamc was called as root, it will setuid to nobody. uhlar at fantomas May6,2008,7:48AM Post S 20:03 0:00 smtp -t unix -u
postfix 12631 0.0 0.0 6968 1936 ? Free forum by Nabble Edit this page cannot open databases, lock failed, file exists Alex mysqlstudent at gmail.com Fri Oct 28 01:11:26 CEST 2011 Previous message: cannot open databases, lock failed, When the lock file is left benhind, "lsof +D ~/.spamassassin" confirms that nothing is accessing any file in that directory, except the process waiting for the lock to be released (which

McGrail 2013-01-20 17:30:27 UTC Considered a configuration issue. https://wiki.dhits.nl/index.php/SpamAssassin The tutorial I was using was: Virtual Users And Domains With Postfix, MailScanner, Mailwatch & MySQL On CentOS 5.1 I also took a look a the Perfect SpamSnake but I am Have you run memtest? > spamd[19334]: bayes: cannot open bayes databases > /home/spamd/.spamassassin/bayes_* R/W: lock failed: File exists Have you stopped spamd, deleted these files, then restarted? However after restarting spamassassin there are memory usage goes right back to 400mb.

S 19:59 0:00 pipe -n dovecot -t unix flags=DRhu user=vmail vmail argv=/usr/libexec/dovecot/deliver -f ${se
postfix 12402 0.0 0.0 6840 1812 ? http://scriptkeeper.net/cannot-open/cannot-open-bayes-databases-lock-failed-file-exists.html at /Library/Perl/5.8.6/Mail/SpamAssassin/BayesStore/DBM.pm line 195.bayes: bayes db version 0 is not able to be used, aborting! I read that by removing all bayes_* files from the /usr/local/share/spamassassin/run would work to reset the database. Aug 17 00:05:25 mail-in-1 spamd[81959]: connection from localhost [127.0.0.1] at port 3994 Aug 17 00:05:25 mail-in-1 spamd[82874]: processing message <E1BwqXb-000LYX-6J [at] mss-mail-in-1> for exim:99.

S 19:58 0:00 trivial-rewrite -n rewrite -t unix -u postfix 12356 0.0 0.0 6796 1708 ? In April I had the same problem and I ended up extending and fixing the tool http://spamassassin.taint.org/devel/db-to-text.pl.txt and posting it to the mailing list. I'm still really concerned that I'll hit another deadlock situation like happened earlier this afternoon. http://scriptkeeper.net/cannot-open/cannot-open-bayes-databases-lock-failed.html Australia jmaul at elih Aug17,2004,9:25AM Post #11 of 19 (11486 views) Permalink RE: Bayes database [In reply to] Quoting "\"Rogers, Zoë A.\"" : > Hi, > > Thanks for your quick

When spamd processing message with shortcircuit rule and flushing bayes_jornal (when max size reached) - there is no unlock event in debug log. During the normal course of >> operation, I have the following messages in the logs: >> >> Oct 25 13:31:36 mail02 amavis[20312]: (20312-01-30) _WARN: bayes: >> cannot open bayes databases /var/spool/amavisd/.spamassassin/bayes_* For further information contact email-integrity [at] dns felicity at kluge Aug17,2004,9:24AM Post #10 of 19 (11491 views) Permalink Re: Bayes database [In reply to] On Tue, Aug 17, 2004 at 05:16:03PM +0100, "Rogers,

On at least two occasions now I've invoked sa-learn explicitly on a message that passed spamd, while spamd was still actively processing other messages.

Ss Mar22 0:05 /usr/libexec/postfix/master
postfix 22227 0.0 0.2 26624 20268 ? I guess it depends what that means. I'm using MailScanner version 4.30.3 and SpamAssassin 2.63. Can anyone provide any insight into how difficult it would be to convert from a local berkeley db to mysql?

S 0:00 spamd child 32632 pts/1 S 0:01 /usr/bin/perl -T -w /usr/bin/sa-learn --spam --single 32638 pts/1 S+ 0:00 grep spam The sa-learn, 32632, is stuck waiting for a lock file to S 19:58 0:00 spawn -n spfpolicy -t unix user=nobody argv=/usr/bin/perl /usr/local/lib/postfix-policyd-spf- postfix 12358 0.0 0.0 7076 2304 ? Look at this output: [[emailprotected] ~]# ps aux | grep -i spam root 12498 0.0 0.0 3908 716 pts/0 S+ 20:00 0:00 grep -i spam There is something that should be http://scriptkeeper.net/cannot-open/cannot-open-bayes-databases-r-w-lock-failed.html Mail about any other subject will be silently ignored.

The user local lock file remains (and has been this way for the last half hour, whilst the daemon was still running and processing mail, and now that it and its if you changed your nameserver configuration, restart spamassassin. falko, Mar 21, 2009 #4 klausengelmann New Member Yes, indeed SElinux is disabled. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.  Apple Support Communities More ways to shop: Visit an Apple

Thanks, Zoe -----Original Message----- From: Theo Van Dinter [mailto:felicity [at] kluge] Sent: 17 August 2004 16:41 To: spamassassin-users [at] incubator Subject: Re: Bayes database On Tue, Aug 17, 2004 at 04:10:25PM Here's a post from Matt quite a while ago where he says that it's okay to delete it, but doesn't really say what the implications are -- will you effectively then decrease it. Thanks again, Alex Previous message: cannot open databases, lock failed, file exists Next message: Adding support for mdb as alternative Messages sorted by: [ date ] [ thread ] [ subject

DO NOT link local.cf to spam.assassin.prefs.conf. the lock may hang around for a while, especially if there's an expire going on. Aug 17 00:05:38 mail-in-1 spamd[82864]: identified spam (8.8/5.0) for exim:99 in 23.1 seconds, 4567 bytes. MailScanner always runs as one user, so do it in your spam.assassin.prefs.conf and NOT local.cf.

Turn off bayes_auto_expire and use bayes_learn_to_journal. I hadn't heard of that before, so have now added it. I'm still really concerned that I'll hit another >deadlock situation like happened earlier this afternoon. bayes: cannot open bayes databases /usr/local/share/spamassassin/bayes_* R/W: lock failed: Interrupted system call When we see the following in the logfile memory is at 1gig +.

But you can see clearly that these files ARE being updated on the fly in spite of "bayes_auto_learn" being turned off. However, your problem is not related to this setting.