Home > Cannot Open > Cannot Open Bayes Databases /root/.spamassassin/bayes_* R/o Tie Failed

Cannot Open Bayes Databases /root/.spamassassin/bayes_* R/o Tie Failed

I have a cronjob monitoring this. 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 decrease it. Futurama56 commented Aug 29, 2015 +1 fixed with cd /home/user-data/mail/spamassassin/ chown spampd:spampd bayes_toks service spampd restart 0xFelix commented Aug 29, 2015 That did the trick! this contact form

Dump / reload? if you have out of control growth, 1) blow away your bayes DBs (aka: restart), 2) learn fewer messages. > 0.000 0 1735776000 0 non-token data: newest atime that's your problem, The inspection was prompted by a log entry, "warn: bayes: cannot open bayes databases /var/spool/spamd/.spamassassin/bayes_* R/W: tie failed: Permission denied". For cp command, you would need the '-p' option. news

Comment 3 Jean-Philippe Pialasse 2016-04-13 18:37:49 CEST (In reply to Mark Phillips from comment #2) > No, this log message appears in logs as far back as 23 February, and I what does the output of sa-learn --force-expire -D look like? >Emails now take nearly 30 seconds to process through spamassassin, see the >maillog below. for providing its computer software that facilitates the management and configuration of Internet web servers. Log In Spampd: Bayes DB permission denied Maintenance tkorves 2015-10-25 12:06:56 UTC #1 Hi there, Are there any tools available for fixing >an SA 2.60 database or should I get rid of the database completely and >start over again?

S 19:59 0:00 smtpd -n smtp -t inet -u
postfix 12400 0.0 0.0 6844 1816 ? Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. Thanks for your help Theo, it pointed me on my way very nicely. Running spamd with the -D option I get this: [email protected]:~$ sudo -s -H [email protected]:/home/andy# /usr/sbin/spamd -D 2>&1 | grep bayes [9395] dbg: config: read file /usr/share/spamassassin/23_bayes.cf [9395] dbg: bayes: tie-ing to

Note that no tokens have expired even though the last expiry ran >today and there are over 4 million tokens in the db. Format For Printing -XML -Clone This Bug -Top of page This is SA Bugzilla: the Apache SpamAssassin bug system. Autolearn might cause problems, especially when too low scores. https://www.howtoforge.com/community/threads/mailscanner-sa-bayes-permissions.32621/ I have an SME 9 system up and running.

but the errors still kept appearing in maillog. S 20:03 0:00 bounce -z -n defer -t unix -u
postfix 12638 0.0 0.0 7336 3216 ? S 11:14 1:31 /usr/sbin/httpd postfix 8542 0.0 0.6 78700 49924 ? you found the right workaround so this happens too in SME8.

I guess correct training should fix/prevent the problem. I read that by removing all bayes_* files from the /usr/local/share/spamassassin/run would work to reset the database. Description Mark Phillips 2016-04-13 18:01:37 CEST File permissions on bayes_toks appear to be incorrect. However, your problem is not related to this setting.

Same for scp or rcp. weblink Here's what >/var/spool/spamassassin looked like a few minutes ago: opportunistic expiry. newcomer at dickinson May11,2004,1:35PM Post #3 of 19 (11469 views) Permalink Re: Bayes database [In reply to] Okay, I'll buy that. Unfortunately Any_DBM doesn't do that kind of thing. :( This is why we've switched to DB_File only in 2.60 since there are too many issues with the billion different DBM libs Comment 5 Theo Van Dinter 2004-01-25 21:01:16 UTC in 2.6x, it's DB_File only, so this should be moot now.

Thanks for all you effort. 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:27 0:00 anvil -l -t unix -u postfix 10872 0.1 0.6 78804 50384 ? navigate here attachment0 (196 bytes) Download Attachment Andy Balaam Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: BAYES_ tags not appearing,

klausengelmann New Member Hello everybody !!! Comment 4 Theo Van Dinter 2003-10-01 07:40:10 UTC Subject: Re: [SAdev] Cannot open bayes databases /home/spamc/.spamassassin/bayes_* R/O: tie failed On Wed, Oct 01, 2003 at 07:39:43AM -0700, bugzilla-daemon@bugzilla.spamassassin.org wrote: > Proper Thanks, Zoe Aug 17 00:05:02 mail-in-1 spamd[82829]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File exists Aug 17 00:05:03 mail-in-1 spamd[82832]: Cannot open bayes databases /usr/local/share/spamassassin/run/bayes_* R/W: lock failed: File

Contribs Bug9446 - warn: bayes: cannot open bayes databases Summary: warn: bayes: cannot open bayes databases Status: CLOSED FIXED Alias: None Product: SME Contribs Classification: Contribs Component: smeserver-learn (show other bugs)

The above line is causing your problems, and it's fundamentally not needed when using MailScanner. I > read that by removing all bayes_* files from the > /usr/local/share/spamassassin/run would work to reset the database. > Does spamassassin then recreate the database files? > > Dont do Terms Privacy Security Status Help You can't perform that action at this time. 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

Help | Matrix . 8.x . 9.x . 10.x . They can only give answers. (Pablo Picasso) gary at primeexalia Dec18,2004,3:00PM Post #16 of 19 (11498 views) Permalink RE: Bayes Database [In reply to] It's in the archives. For further information contact email-integrity [at] dns felicity at kluge Aug17,2004,8:41AM Post #7 of 19 (11485 views) Permalink Re: Bayes database [In reply to] On Tue, Aug 17, 2004 at 04:10:25PM +0100, "Rogers, http://ecoflashapps.com/cannot-open/cannot-open-bayes-databases-r-w-lock-failed.html Aug 17 00:05:28 mail-in-1 spamd[81959]: connection from localhost [127.0.0.1] at port 3997 Aug 17 00:05:28 mail-in-1 spamd[82878]: processing message <2352774.1092695757739.JavaMail.oracle [at] app-6> for exim:99.

S 19:41 0:00 MailWatch SQL postfix 11687 0.0 0.0 6804 1764 ? debug: Initialising learner debug: bayes: 14631 tie-ing to DB file R/O /etc/mail/spamassassin/bayes_toks debug: bayes: 14631 tie-ing to DB file R/O /etc/mail/spamassassin/bayes_seen debug: bayes: found bayes db version 2 debug: bayes: Not I'd strongly suggest that you NEVER force a global bayes in local.cf unless you use mode 666. It's related to the timestamps on your tokens being corrupt. --------------------------------------------------- This email from dns has been validated by dnsMSS Managed Email Security and is free from all known viruses.

Don Newcomer Senior Manager, Systems Infrastructure Systems Department Library and Information Services Dickinson College P.O. Permissions are correct, any ideas? You signed in with another tab or window. SA, by default, uses a bayes directory in the home directory of whatever user invokes SA.

M$ Win's are shit, do not use it ! felicity at apache May6,2008,8:51AM Post #19 of 19 (10990 views) Permalink Re: Bayes database [In reply to] On Tue, May 06, 2008 at 04:16:06PM By doing it in local.cf you've fundamentally forced SA to only ever be invoked as one user without breaking the whole system. Tue Aug 12 15:13:36 2008 [6247] warn: bayes: cannot open bayes databases /etc/mail/spamassassin/spamdb/bayes_* R/O: tie failed: Permission denied Tue Aug 12 15:13:36 2008 [6247] warn: bayes: cannot open bayes databases /etc/mail/spamassassin/spamdb/bayes_* S 19:59 0:00 pipe -n dovecot -t unix flags=DRhu user=vmail vmail argv=/usr/libexec/dovecot/deliver -f ${se
postfix 12414 0.0 0.0 6796 1712 ?

I am giving that a go. S 04:13 0:01 qmgr -l -t fifo -u
postfix 17164 0.0 0.0 6804 1824 ? I'd appreciate any help you can give me. Aug 17 00:05:13 mail-in-1 spamd[81959]: connection from localhost [127.0.0.1] at port 3987 Aug 17 00:05:13 mail-in-1 spamd[82862]: processing message <20040816-14325817-bd0 [at] nem> for exim:99.

Home Categories FAQ/Guidelines Terms of Service Privacy Policy Powered by Discourse, best viewed with JavaScript enabled