On 11/29/2013 11:13 PM, Gino Semseo wrote:
Hello:
I need some support here, since I am getting crazy.... not always, but
often, SA childs die without advise during proccesing of an email...
Exim then just receive something like:
2013-11-29 20:29:01 1VmTkL-0002F8-5Q spam acl condition: cannot parse
spamd output
These are some logs...
/usr/local/cpanel/3rdparty/perl/514/bin/spamassassin -V
SpamAssassin version 3.3.2
running on Perl version 5.14.3
I have started spamd with -D for debugging:
Then...
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: ordered 38942 to accept
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: sysread(7) not ready,
wait max 300 secs
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: child 38942: entering
state 2
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: new lowest idle kid:
38944
Nov 29 16:00:55 hyperserver spamd[38942]: spamd: connection from
localhost [127.0.0.1] at port 44846
Nov 29 16:00:55 hyperserver spamd[38942]: spamd: setuid to diversia
succeeded
Nov 29 16:00:55 hyperserver spamd[38942]: config: read_scoreonly_config:
cannot open "/home/diversia/.spamassassin/user_prefs": No such file or
directory
Nov 29 16:00:55 hyperserver spamd[38942]: info: user has changed
Nov 29 16:00:55 hyperserver spamd[38942]: bayes: learner_new
self=Mail::SpamAssassin::Plugin::Bayes=HASH(0x3ac68d0),
bayes_store_module=Mail::SpamAssassin::$
Nov 29 16:00:55 hyperserver spamd[38942]: bayes: learner_new: got
store=Mail::SpamAssassin::BayesStore::DBM=HASH(0x5765450)
Nov 29 16:00:55 hyperserver spamd[38942]: bayes: tie-ing to DB file R/O
/etc/mail/spamassassin/bayes/bayes_toks
Nov 29 16:00:55 hyperserver spamd[38942]: bayes: tie-ing to DB file R/O
/etc/mail/spamassassin/bayes/bayes_seen
Nov 29 16:00:55 hyperserver spamd[38942]: bayes: found bayes db version 3
Nov 29 16:00:55 hyperserver spamd[38942]: bayes: DB journal sync: last
sync: 1385736975
Nov 29 16:00:55 hyperserver spamd[38942]: config: score set 3 chosen.
Nov 29 16:00:55 hyperserver spamd[38942]: spamd: running as uid 574
Nov 29 16:00:55 hyperserver spamd[38942]: config: time limit 300.0 s
Nov 29 16:00:55 hyperserver spamd[38942]: message: main message type:
multipart/mixed
...
...
...
...
etc
...
...
...
...
etc
...
...
...
Nov 29 16:00:55 hyperserver spamd[38942]: FreeMail: RULE (FREEMAIL_FROM)
check_freemail_from
Nov 29 16:00:55 hyperserver spamd[38942]: FreeMail: all from-addresses:
rcop...@vivagym.es
Nov 29 16:00:55 hyperserver spamd[38942]: spf: checking to see if the
message has a Received-SPF header that we can use
Nov 29 16:00:55 hyperserver spamd[38942]: spf: checking HELO
(helo=mail-vb0-f48.google.com, ip=209.85.212.48)
Nov 29 16:00:55 hyperserver spamd[38942]: dns: providing a callback for
id: 34562/mail-vb0-f48.google.com/SPF/IN
Nov 29 16:00:55 hyperserver spamd[38942]: dns: providing a callback for
id: 8678/mail-vb0-f48.google.com/TXT/IN
Nov 29 16:00:55 hyperserver spamd[38942]: spf: query for
/209.85.212.48/mail-vb0-f48.google.com: result: none, comment: , text:
No applicable sender policy available
Nov 29 16:00:55 hyperserver spamd[38942]: spf: already checked for
Received-SPF headers, proceeding with DNS based checks
Nov 29 16:00:55 hyperserver spamd[38942]: spf: found Envelope-From in
first external Received header
Nov 29 16:00:55 hyperserver spamd[38942]: spf: checking EnvelopeFrom
(helo=mail-vb0-f48.google.com, ip=209.85.212.48,
envfrom=rcop...@vivagym.es)
Nov 29 16:00:55 hyperserver spamd[38942]: dns: providing a callback for
id: 21188/vivagym.es/SPF/IN
Nov 29 16:00:55 hyperserver spamd[38942]: dns: providing a callback for
id: 44168/vivagym.es/TXT/IN
Nov 29 16:00:55 hyperserver spamd[38942]: spf: query for
rcop...@vivagym.es/209.85.212.48/mail-vb0-f48.google.com: result: none,
comment: , text: No applicable sender policy available
Nov 29 16:00:55 hyperserver spamd[38942]: FreeMail: RULE
(__freemail_reply) check_freemail_replyto
Nov 29 16:00:55 hyperserver spamd[38942]: FreeMail: From address:
rcop...@vivagym.es
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: child closed connection
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: child states: BIIIII
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: child 38942: just exited
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: child 38942: entering
state 4
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: new lowest idle kid:
38944
Nov 29 16:00:55 hyperserver spamd[38925]: spamd: handled cleanup of
child pid [38942] due to SIGCHLD: exit 1
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: new lowest idle kid:
38944
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: select returned err
Interrupted system call, probably signalled
Nov 29 16:00:55 hyperserver spamd[38925]: spamd: server successfully
spawned child process, pid 39240
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: child 39240: entering
state 0
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: new lowest idle kid:
38944
Nov 29 16:00:55 hyperserver spamd[39240]: plugin:
Mail::SpamAssassin::Plugin::ResourceLimits=HASH(0x3f9b328) implements
'spamd_child_init', priority 0
Nov 29 16:00:55 hyperserver spamd[39240]: resourcelimitplugin: In
spamd_child_init
Nov 29 16:00:55 hyperserver spamd[39240]: resourcelimitplugin: cpu limit: 0
Nov 29 16:00:55 hyperserver spamd[39240]: resourcelimitplugin: mem
limit: 268435456
Nov 29 16:00:55 hyperserver spamd[39240]: prefork: sysread(12) not
ready, wait max 300 secs
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: child 39240: entering
state 1
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: new lowest idle kid:
38944
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: child reports idle
Nov 29 16:00:55 hyperserver spamd[38925]: prefork: child states: IIIIII
Bang! As you may see, the child just went out directly, as "prefork:
child closed connection" and "prefork: child 38942: just exited"...
Not always at the same point... by example, other one:
Nov 29 15:52:28 hyperserver spamd[34429]: rules: running rawbody tests;
score so far=-100
Nov 29 15:52:28 hyperserver spamd[34429]: rules: running full tests;
score so far=-100
Nov 29 15:52:28 hyperserver spamd[34429]: rules: running meta tests;
score so far=-100
Nov 29 15:52:28 hyperserver spamd[34429]: check: running tests for
priority: -900
Nov 29 15:52:28 hyperserver spamd[34429]: rules: running one_line_body
tests; score so far=-100
Nov 29 15:52:28 hyperserver spamd[34429]: rules: running head tests;
score so far=-100
Nov 29 15:52:28 hyperserver spamd[34429]: rules: running head_eval
tests; score so far=-100
Nov 29 15:52:28 hyperserver spamd[34429]: rules: run_eval_tests -
compiling eval code: 9, priority -900
Nov 29 15:52:28 hyperserver spamd[34429]: rules: running body tests;
score so far=-100
Nov 29 15:52:28 hyperserver spamd[34429]: rules: running uri tests;
score so far=-100
Nov 29 15:52:28 hyperserver spamd[34429]: rules: running body_eval
tests; score so far=-100
Nov 29 15:52:28 hyperserver spamd[34429]: rules: run_eval_tests -
compiling eval code: 11, priority -900
Nov 29 15:52:28 hyperserver spamd[34429]: rules: running rawbody tests;
score so far=-100
Nov 29 15:52:28 hyperserver spamd[34429]: rules: running full tests;
score so far=-100
Nov 29 15:52:28 hyperserver spamd[34429]: rules: running meta tests;
score so far=-100
Nov 29 15:52:28 hyperserver spamd[34429]: check: running tests for
priority: -400
Nov 29 15:52:28 hyperserver spamd[34416]: prefork: child closed connection
Nov 29 15:52:28 hyperserver spamd[34416]: prefork: child states: BIIIII
Nov 29 15:52:28 hyperserver spamd[34416]: prefork: child 34429: just exited
Nov 29 15:52:28 hyperserver spamd[34416]: prefork: child 34429: entering
state 4
Nov 29 15:52:28 hyperserver spamd[34416]: prefork: new lowest idle kid:
34430
Nov 29 15:52:28 hyperserver spamd[34416]: spamd: handled cleanup of
child pid [34429] due to SIGCHLD: exit 1
I do not know what to do...
If I just execute spamassassin -t -D from shell, most times there is no
error and the message is fully scanned...
Could someone help me?
As you haven't provided much info as to what parameters you use to run
spamd, what glue is being used by Exim, OS, resources, etc. and assuming
this is a Cpanel box provided by your hoster, for fast "support" you may
be better off contacting your hosting support or a Cpanel forum.
