Hello everybody,

I've the same problem with the same configuration (RH 7.2 - syslog 1.4.14 -
SpamAssassin 2.20 - Postfix 1.1.8).

>1) verify spamd is running
Yes
>2) restart syslog-ng
Ok
>3) verify spamd is running
Yes
>4) send a test message through spamc
Ok
>5) verify spamd is running
Yes, but messages are not processed until I restart spamd.

I'm using content filtering with postfix; when the problem occurred spamd,
spamc AND my bash script who call spamc, are still loaded and visible with
ps -aux.

This problem happened each time syslog is restarted; I've tried to use the
watchdog script from the list : (e.g: echo quit | telnet localhost 783 2>&1
| grep "refused"), but because spamd is running it return nothing.

Here's a log session of an incoming spam :

May 13 11:35:42 john postfix/master[1688]: reload configuration
May 13 11:36:16 john postfix/smtpd[10917]: connect from
unknown[193.9.yy.xxx]
May 13 11:36:16 john postfix/smtpd[10917]: 341A8F032B:
client=unknown[193.9.yy.xxx]
May 13 11:36:16 john postfix/cleanup[10918]: 341A8F032B:
message-id=<[EMAIL PROTECTED]>
May 13 11:36:16 john postfix/qmgr[10858]: 341A8F032B:
from=<[EMAIL PROTECTED]>, size=17421, nrcpt=1 (queue active)
May 13 11:36:16 john amavis[10061]: SMTP-in
/var/amavis/amavis-20020513T093901-10061: <[EMAIL PROTECTED]> ->
<[EMAIL PROTECTED]>
May 13 11:36:16 john amavis[10061]: Checking: <[EMAIL PROTECTED]> ->
<[EMAIL PROTECTED]>
May 13 11:36:16 john amavis[10061]: body hash:
2755231aedbd9a3c771b65386824e133
May 13 11:36:16 john amavis[10061]: Using Sophie
May 13 11:36:16 john amavis[10061]: Re-connecting to Sophie, attempt #1
May 13 11:36:16 john amavis[10061]: Result from Sophie: 0
May 13 11:36:16 john amavis[10061]: Using /usr/local/bin/sweep
May 13 11:36:17 john amavis[10061]: fwd via smtp: <[EMAIL PROTECTED]> ->
<[EMAIL PROTECTED]>
May 13 11:36:17 john postfix/smtpd[10925]: connect from
localhost.localdomain[127.0.0.1]
May 13 11:36:17 john postfix/smtpd[10925]: 55970F032C:
client=localhost.localdomain[127.0.0.1]
May 13 11:36:17 john postfix/cleanup[10918]: 55970F032C:
message-id=<[EMAIL PROTECTED]>
May 13 11:36:17 john postfix/smtpd[10925]: disconnect from
localhost.localdomain[127.0.0.1]
May 13 11:36:17 john amavis[10061]: mail checking ended: DELIVERED
May 13 11:36:17 john postfix/smtp[10920]: 341A8F032B: to=<[EMAIL PROTECTED]>,
relay=localhost[127.0.0.1], delay=1, status=sent (250 Ok, id=10061-09, from
MTA: Ok: queued as 55970F032C)
May 13 11:36:17 john postfix/qmgr[10858]: 55970F032C:
from=<[EMAIL PROTECTED]>, size=17652, nrcpt=1 (queue active)
May 13 11:36:17 john amavis[10061]: TIMING [total 1083 ms] - SMTP DATA: 39
(4%), body hash: 1 (0%), mime parse: 127 (12%), get-file-type: 6 (1%),
unpacker: 0 (0%), get-file-type: 42 (4%), unpacker: 0 (0%), parts: 0 (0%),
AV-scan: 601 (56%), fwd-connect: 48 (4%), fwd-mail-from: 22 (2%),
fwd-rcpt-to: 2 (0%), output-header: 4 (0%), fwd-body: 12 (1%), fwd-rundown:
103 (9%), unlink-2-files: 1 (0%), rundown: 73 (7%)
May 13 11:36:18 john postfix/smtpd[10917]: disconnect from
unknown[193.9.yy.xxx]

And then nothing... At this point, Postfix normally send the incoming email
to the bash script for content filtering.
Here's what happened when I restart spamd :

May 13 11:36:54 john postfix/pipe[10926]: 55970F032C: to=<[EMAIL PROTECTED]>,
relay=spamd, delay=37, status=bounced (service unavailable)
May 13 11:36:54 john postfix/cleanup[10918]: B5C28F032B:
message-id=<[EMAIL PROTECTED]>
May 13 11:36:54 john postfix/qmgr[10858]: B5C28F032B: from=<>, size=19177,
nrcpt=1 (queue active)
May 13 11:36:55 john postfix/smtp[10966]: B5C28F032B: to=<[EMAIL PROTECTED]>,
relay=realy.something.be[212.67.fff.ggg], delay=1, status=sent (250 Ok:
queued as B9466521D)
May 13 11:36:58 john spamd[10981]: server started on port 783
May 13 11:37:46 john sophie[10923]: Sophie child has timed-out (no data
received in 90 seconds) - process killed

Nothing about spamd in the log, but when I'm looking into my quarantine
folder, the spam is there and marked, so it has been correctly processed by
the SpamAssassin.

Hope that there is a fix for that :)

Gilles.

-----Original Message-----
From: Michael Stenner [mailto:[EMAIL PROTECTED]] 
Sent: dimanche 12 mai 2002 21:03
To: [EMAIL PROTECTED]
Subject: Re: [SAtalk] spamd dying


On Sun, May 12, 2002 at 12:24:40PM -0500, Richie Laager wrote:
> On Sunday 12 May 2002 11:57 am, Michael Stenner wrote:
> >  The only times I KNOW it died were at sunday morning log rotation.  
> > Granted, some other things happen then, but I think the log rotation 
> > is the best bet.
> 
> I would recommend that you start experimenting. For example,
> try restarting the syslog daemon with; /etc/init.d/syslog-ng 
> restart >>/dev/null

All good suggestions (snipped).  A little background, then my findings.

This is a semi-serious machine.  It's the mail/nfs/nis/dns/log server for
the Duke Univ. Linux Users Group.  Several (maybe 25) do their primary mail
through it, so I don't want to muck with it a lot.  Only 1 real person is
using spamd on it though.  It's being tested there to see if we want to use
it in Duke Physics.

So, I suspected that it was not dying because logs were rotated _WHILE_ a
message was being processed.  (There's just not that much... odds were very
small it would happen two weeks in a row.)

Here's what I did:
1) verify spamd is running (yes)
2) restart syslog-ng
3) verify spamd is running (yes)
4) send a test message through spamc
5) verify spamd is running (NO!!!)

The message arrived, slthough it was not processed (no SA headers). There
was nothing in the logs from spamd or spamc (presumably because spamc
connected successfully, but but spamd died before finishing).

> No matter what you find out, make sure to file a bugzilla
> report with as much detail as possible.

I will most certainly do that.  At this point, I think we're close enough
that I think I'll just try and nail it down so I can send you a patch along
with the bug report.  If you have any further insight as to where I should
start looking, though, it would be much appreciated.

I think I'll probably try and grab the (maybe 50 lines of) code that does
the logging, and see if I can recreate the problem on my home server, which
I'm considerably more willing to futz with.

                                        -Michael

-- 
  Michael Stenner                       Office Phone: 919-660-2513
  Duke University, Dept. of Physics       [EMAIL PROTECTED]
  Box 90305, Durham N.C. 27708-0305

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Spamassassin-talk mailing list [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to