Re: Bayes R/O tie failed with SA 3.0

2004-10-03 Thread Asif Iqbal
On Sat, Oct 02, 2004 at 03:10:56PM, Bob Proulx wrote:
 Asif Iqbal wrote:
  I just upgraded my SA from 2.63 to 3.0. I did the sa-learn --sync after
  the upgrade and the restarted spamd. Now I am seeing this error in the
  log
  
  @4000415f15ec35d6286c Cannot open bayes databases 
  /etc/mail/spamassassin/bayes_* R/O: tie failed: Permission denied
 
 You probably ran sa-learn as root instead of as the user that normally
 runs spamassassin.  That changed the ownership of the files to root.
 Find them.  Change them back to whatever user you are using to run as

Well according to my following setup

qmailq is the owner of spamd processses and has read/write permission on
bayes_* files through the spam group

(root)@qmail:/etc/mail/spamassassin# ls -al bayes_*
-rw-rw-r--   1 root spam   24576 Oct  2 21:33 bayes_seen
-rw-rw   1 root spam   90112 Oct  2 21:33 bayes_toks

(root)@qmail:/etc/mail/spamassassin# cat /etc/group | grep spam
spam::2111:qmailq,qscand

(root)@qmail:/etc/mail/spamassassin# cat /service/spamd/run
#!/bin/sh
exec 21
exec /usr/local/bin/spamd -m 20 -s stderr --syslog-socket=inet -u qmailq

(root)@qmail:/etc/mail/spamassassin# ps -ef | grep spamd
[...]
qmailq 19869 19843  0 16:47:46 ?0:00 /usr/local/bin/perl -T
/usr/local/bin/spamd -m 20 -s stderr --syslog-socket=ine
[...]

Not sure what else to look for

Thanks for the suggestions

 so that it can access those files.
 
 Bob

-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
...it said: Install Windows XP or better...so I installed Solaris...


Re: Bayes R/O tie failed with SA 3.0

2004-10-03 Thread Alex S Moore
On Sat, 2004-10-02 at 21:40 -0400, Asif Iqbal wrote:
 On Sat, Oct 02, 2004 at 03:10:56PM, Bob Proulx wrote:
 qmailq is the owner of spamd processses and has read/write permission on
 bayes_* files through the spam group
 
 (root)@qmail:/etc/mail/spamassassin# ls -al bayes_*
 -rw-rw-r--   1 root spam   24576 Oct  2 21:33 bayes_seen
 -rw-rw   1 root spam   90112 Oct  2 21:33 bayes_toks
 
 (root)@qmail:/etc/mail/spamassassin# cat /etc/group | grep spam
 spam::2111:qmailq,qscand
 

What about `ls -ld /etc/mail/spamassasin`?

Alex




RE: Bayes R/O tie failed with SA 3.0

2004-10-03 Thread Ray
I had the exact same problem.  I ran the sa-learn --sync as root instead of
the user I have in the spamd startup script.  In my case I have spamd -u
spamduser   So I just simply went to the bayes folder as root and did a
chown to make spamduser the owner of all the bayes files again, and
restarted spamd.


Ray Dzek
Network Operations Supervisor
Specialized Bicycle Components

-Original Message-
From: Asif Iqbal [mailto:[EMAIL PROTECTED] 
Sent: Saturday, October 02, 2004 2:02 PM
To: [EMAIL PROTECTED]
Subject: Bayes R/O tie failed with SA 3.0


Hi All

I just upgraded my SA from 2.63 to 3.0. I did the sa-learn --sync after the
upgrade and the restarted spamd. Now I am seeing this error in the log

@4000415f15ec35d6286c Cannot open bayes databases
/etc/mail/spamassassin/bayes_* R/O: tie failed: Permission denied
@4000415f15f0255793f4 2004-10-02 20:56:06 [19857] i: clean message
(0.0/5.0) for [EMAIL PROTECTED]:7794 in 3.7 seconds, 2187 bytes.
@4000415f15f0255cfeac 2004-10-02 20:56:06 [19857] i: result: .  0 -
scantime=3.7,size=2187,mid=[EMAIL PROTECTED]
04.AD.QINTRA.COM,autolearn=failed

Has anyone else seen the same error?

Any help/suggestion to fix this issue is greatly appreciated


-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
...it said: Install Windows XP or better...so I installed Solaris...



Re: Bayes R/O tie failed with SA 3.0

2004-10-02 Thread Alex S Moore
On Sat, 2004-10-02 at 17:01 -0400, Asif Iqbal wrote:
 I just upgraded my SA from 2.63 to 3.0. I did the sa-learn --sync after
 the upgrade and the restarted spamd. Now I am seeing this error in the
 log
 
 @4000415f15ec35d6286c Cannot open bayes databases 
 /etc/mail/spamassassin/bayes_* R/O: tie failed: Permission denied

Whichever user you had owning the bayes_* files before the upgrade has
changed.  Actually, the `sa-learn --sync` probably changed the
permissions.  Correct the permissions to what is appropriate for your
environment.

Alex