You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Warren Togami <wt...@redhat.com> on 2009/12/18 20:37:55 UTC
pyzor error during spamd startup
Dec 18 14:23:46 localhost spamd[20766]: spamd: server killed by SIGTERM,
shutting down
Dec 18 14:23:50 localhost spamd[20799]: logger: removing stderr method
Dec 18 14:23:59 localhost spamd[20801]: pyzor: check failed: internal
error, python traceback seen in response
Dec 18 14:23:59 localhost spamd[20801]: spamd: server started on port
783/tcp (running version 3.3.0-beta1)
Dec 18 14:23:59 localhost spamd[20801]: spamd: server pid: 20801
Dec 18 14:23:59 localhost spamd[20801]: spamd: server successfully
spawned child process, pid 20804
Dec 18 14:23:59 localhost spamd[20801]: spamd: server successfully
spawned child process, pid 20805
Dec 18 14:23:59 localhost spamd[20801]: prefork: child states: IS
Dec 18 14:23:59 localhost spamd[20801]: prefork: child states: II
Any idea how to see contents of this traceback that spamd reports? This
apparently has been happening on Fedora 12 since before beta1 and
continues in svn trunk now. But I don't see this error on RHEL5.
pyzor does appear to work properly with spamc/spamd with no further
error messages in syslog. This initial error during spamd startup is
the only error that appears in the logs.
Warren Togami
wtogami@redhat.com
Re: pyzor error during spamd startup
Posted by Warren Togami <wt...@redhat.com>.
On 12/18/2009 04:10 PM, Kevin A. McGrail wrote:
> Why is pyzor running as root?
It isn't. This seems to be some self-tests during spamd startup. The
real pyzor launched by spamd runs as the spamc user.
Warren
Re: pyzor error during spamd startup
Posted by Benny Pedersen <me...@junc.org>.
On Fri 18 Dec 2009 10:10:31 PM CET, "Kevin A. McGrail" wrote
> Why is pyzor running as root?
spamd start up as root ?, and dropspriv to late before calling pyzor ?
spamassassin -t test.msg creates for root also here a dir in /.spamassassin
--
xpoint
Re: pyzor error during spamd startup
Posted by "Kevin A. McGrail" <km...@pccc.com>.
Why is pyzor running as root?
----- Original Message -----
From: Justin Mason
To: Warren Togami
Cc: Mark Martinec ; SpamAssassin Dev
Sent: Friday, December 18, 2009 4:07 PM
Subject: Re: pyzor error during spamd startup
it should be harmless, btw, since this is just the preloading-modules step. Ugly, though.
On Fri, Dec 18, 2009 at 20:53, Warren Togami <wt...@redhat.com> wrote:
On 12/18/2009 03:24 PM, Mark Martinec wrote:
There is no error running pyzor directly or via spamassassin -D. It is
only reporting an error during spamd startup.
Perhaps spamd is running under a different uid that your command-line tests?
Run tests under the same uid under which spamd will be running:
su vscan -c 'spamassassin -D -t<0.msg'
Mark
Dec 18 15:49:55 localhost spamd[5096]: pyzor: opening pipe: /usr/bin/pyzor check < /tmp/.spamassassin5096Y9v0nmtmp
Dec 18 15:49:55 localhost spamd[5097]: util: setuid: ruid=0 euid=0
Dec 18 15:49:55 localhost spamd[5096]: pyzor: [5097] finished: exit 1
Dec 18 15:49:55 localhost spamd[5096]: pyzor: got response: Traceback (most recent call last):\n File "/usr/bin/pyzor", line 8, in <module>\n pyzor.client.run()\n File "/usr/lib/python2.6/site-packages/pyzor
/client.py", line 1022, in run\n ExecCall().run()\n File "/usr/lib/python2.6/site-packages/pyzor/client.py", line 180, in run\n os.mkdir(homedir)\nOSError: [Errno 13] Permission denied: '/root/.pyzor'
Dec 18 15:49:55 localhost spamd[5096]: info: leaving helper-app run mode
Dec 18 15:49:55 localhost spamd[5096]: pyzor: check failed: internal error, python traceback seen in response
This is a pyzor + selinux bug, not spamassassin's fault. We have a go for spamassassin-3.3.0-rc1. Doing some further tests before cutting.
Warren
--
--j.
Re: pyzor error during spamd startup
Posted by Justin Mason <jm...@jmason.org>.
it should be harmless, btw, since this is just the preloading-modules step.
Ugly, though.
On Fri, Dec 18, 2009 at 20:53, Warren Togami <wt...@redhat.com> wrote:
> On 12/18/2009 03:24 PM, Mark Martinec wrote:
>
>> There is no error running pyzor directly or via spamassassin -D. It is
>>> only reporting an error during spamd startup.
>>>
>>
>> Perhaps spamd is running under a different uid that your command-line
>> tests?
>>
>> Run tests under the same uid under which spamd will be running:
>> su vscan -c 'spamassassin -D -t<0.msg'
>>
>>
>> Mark
>>
>
> Dec 18 15:49:55 localhost spamd[5096]: pyzor: opening pipe: /usr/bin/pyzor
> check < /tmp/.spamassassin5096Y9v0nmtmp
> Dec 18 15:49:55 localhost spamd[5097]: util: setuid: ruid=0 euid=0
> Dec 18 15:49:55 localhost spamd[5096]: pyzor: [5097] finished: exit 1
> Dec 18 15:49:55 localhost spamd[5096]: pyzor: got response: Traceback (most
> recent call last):\n File "/usr/bin/pyzor", line 8, in <module>\n
> pyzor.client.run()\n File "/usr/lib/python2.6/site-packages/pyzor
> /client.py", line 1022, in run\n ExecCall().run()\n File
> "/usr/lib/python2.6/site-packages/pyzor/client.py", line 180, in run\n
> os.mkdir(homedir)\nOSError: [Errno 13] Permission denied: '/root/.pyzor'
> Dec 18 15:49:55 localhost spamd[5096]: info: leaving helper-app run mode
> Dec 18 15:49:55 localhost spamd[5096]: pyzor: check failed: internal error,
> python traceback seen in response
>
> This is a pyzor + selinux bug, not spamassassin's fault. We have a go for
> spamassassin-3.3.0-rc1. Doing some further tests before cutting.
>
> Warren
>
>
--
--j.
Re: pyzor error during spamd startup
Posted by Warren Togami <wt...@redhat.com>.
On 12/18/2009 03:24 PM, Mark Martinec wrote:
>> There is no error running pyzor directly or via spamassassin -D. It is
>> only reporting an error during spamd startup.
>
> Perhaps spamd is running under a different uid that your command-line tests?
>
> Run tests under the same uid under which spamd will be running:
> su vscan -c 'spamassassin -D -t<0.msg'
>
>
> Mark
Dec 18 15:49:55 localhost spamd[5096]: pyzor: opening pipe:
/usr/bin/pyzor check < /tmp/.spamassassin5096Y9v0nmtmp
Dec 18 15:49:55 localhost spamd[5097]: util: setuid: ruid=0 euid=0
Dec 18 15:49:55 localhost spamd[5096]: pyzor: [5097] finished: exit 1
Dec 18 15:49:55 localhost spamd[5096]: pyzor: got response: Traceback
(most recent call last):\n File "/usr/bin/pyzor", line 8, in <module>\n
pyzor.client.run()\n File "/usr/lib/python2.6/site-packages/pyzor
/client.py", line 1022, in run\n ExecCall().run()\n File
"/usr/lib/python2.6/site-packages/pyzor/client.py", line 180, in run\n
os.mkdir(homedir)\nOSError: [Errno 13] Permission denied: '/root/.pyzor'
Dec 18 15:49:55 localhost spamd[5096]: info: leaving helper-app run mode
Dec 18 15:49:55 localhost spamd[5096]: pyzor: check failed: internal
error, python traceback seen in response
This is a pyzor + selinux bug, not spamassassin's fault. We have a go
for spamassassin-3.3.0-rc1. Doing some further tests before cutting.
Warren
Re: pyzor error during spamd startup
Posted by Mark Martinec <Ma...@ijs.si>.
> There is no error running pyzor directly or via spamassassin -D. It is
> only reporting an error during spamd startup.
Perhaps spamd is running under a different uid that your command-line tests?
Run tests under the same uid under which spamd will be running:
su vscan -c 'spamassassin -D -t <0.msg'
Mark
Re: pyzor error during spamd startup
Posted by Warren Togami <wt...@redhat.com>.
On 12/18/2009 02:57 PM, Mark Martinec wrote:
> Try it from a command line: spamassasssin -D -t<0.msg
> which may be able to show more information of a failure.
>
> Also, try it directly: $ pyzor check<0.msg
>
> Mark
There is no error running pyzor directly or via spamassassin -D. It is
only reporting an error during spamd startup.
Warren
Re: pyzor error during spamd startup
Posted by Mark Martinec <Ma...@ijs.si>.
> Dec 18 14:23:59 localhost spamd[20801]: pyzor: check failed: internal
> error, python traceback seen in response
>
> Any idea how to see contents of this traceback that spamd reports? This
> apparently has been happening on Fedora 12 since before beta1 and
> continues in svn trunk now. But I don't see this error on RHEL5.
>
> pyzor does appear to work properly with spamc/spamd with no further
> error messages in syslog. This initial error during spamd startup is
> the only error that appears in the logs.
Try it from a command line: spamassasssin -D -t <0.msg
which may be able to show more information of a failure.
Also, try it directly: $ pyzor check <0.msg
Mark