spamassassin causing Mailscanner defunct {Scanned}
Chris Wilber
chris at WILBER.ME.UK
Mon Oct 13 11:24:28 IST 2003
Thanks for quick response.
I have already tried this and it doesn't give me any clues except that the
last line is a bit strange. There were no errors in var/spool/maillog. Here
is the output with UseSpamAssassin= yes
/usr/sbin/check_mailscanner
Starting MailScanner...
In Debugging mode, not forking...
debug: Score set 0 chosen.
debug: running in taint mode? no
debug: ignore: test message to precompile patterns and load modules
debug: using "/usr/share/spamassassin" for default rules dir
debug: using "/etc/mail/spamassassin" for site rules dir
debug: using "/etc/MailScanner/spam.assassin.prefs.conf" for user prefs file
debug: bayes: 6062 tie-ing to DB file R/O /var/spool/spamassassin/bayes_toks
debug: bayes: 6062 tie-ing to DB file R/O /var/spool/spamassassin/bayes_seen
debug: bayes: found bayes db version 2
debug: bayes: Not available for scanning, only 8 spam(s) in Bayes DB < 200
debug: bayes: 6062 untie-ing
debug: bayes: 6062 untie-ing db_toks
debug: bayes: 6062 untie-ing db_seen
debug: Score set 1 chosen.
debug: Initialising learner
debug: bayes: 6062 tie-ing to DB file R/O /var/spool/spamassassin/bayes_toks
debug: bayes: 6062 tie-ing to DB file R/O /var/spool/spamassassin/bayes_seen
debug: bayes: found bayes db version 2
debug: bayes: Not available for scanning, only 8 spam(s) in Bayes DB < 200
debug: bayes: 6062 untie-ing
debug: bayes: 6062 untie-ing db_toks
debug: bayes: 6062 untie-ing db_seen
debug: running header regexp tests; score so far=0
debug: running body-text per-line regexp tests; score so far=1.27
debug: Razor2 is available
debug: entering helper-app run mode
Razor-Log: Computed razorhome from env: /root/.razor
Razor-Log: Found razorhome: /root/.razor
Razor-Log: No /root/.razor/razor-agent.conf found, skipping.
Razor-Log: No razor-agent.conf found, using defaults.
Oct 13 11:14:23.033708 check[6062]: [ 1] [bootup] Logging initiated
LogDebugLevel=9 to stdout
Oct 13 11:14:23.036209 check[6062]: [ 5] computed razorhome=/root/.razor,
conf=, ident=/root/.razor/identity
Oct 13 11:14:23.038200 check[6062]: [ 8] Client supported_engines: 1 2 3 4
Oct 13 11:14:23.040682 check[6062]: [ 8] prep_mail done: mail 1 headers=102,
mime0=1376
Oct 13 11:14:23.042954 check[6062]: [ 5] read_file: 1 items read from
/root/.razor/servers.discovery.lst
Oct 13 11:14:23.045123 check[6062]: [ 5] read_file: 2 items read from
/root/.razor/servers.nomination.lst
Oct 13 11:14:23.047254 check[6062]: [ 5] read_file: 2 items read from
/root/.razor/servers.catalogue.lst
Oct 13 11:14:23.049714 check[6062]: [ 9] Assigning defaults to
joy.cloudmark.com
Oct 13 11:14:23.051276 check[6062]: [ 9] Assigning defaults to
folly.cloudmark.com
Oct 13 11:14:23.052804 check[6062]: [ 9] Assigning defaults to
stress.cloudmark.com
Oct 13 11:14:23.054304 check[6062]: [ 9] Assigning defaults to
truth.cloudmark.com
Oct 13 11:14:23.057303 check[6062]: [ 5] read_file: 12 items read from
/root/.razor/server.truth.cloudmark.com.conf
Oct 13 11:14:23.059285 check[6062]: [ 5] 54359 seconds before closest server
discovery
Oct 13 11:14:23.060877 check[6062]: [ 6] stress.cloudmark.com is a
Unknown-Type: Server srl -1; computed min_cf=0, Server se: 0F
Oct 13 11:14:23.062878 check[6062]: [ 8] Computed supported_engines: 1 2 3 4
Oct 13 11:14:23.064300 check[6062]: [ 8] Using next closest server
stress.cloudmark.com:2703, cached info srl -1
Oct 13 11:14:23.065853 check[6062]: [ 8] mail 1 has no subject
Oct 13 11:14:23.072316 check[6062]: [ 6] preproc: mail 1.0 went from 1376
bytes to 1339
Oct 13 11:14:23.073888 check[6062]: [ 6] computing sigs for mail 1.0, len 1339
/usr/sbin/check_mailscanner: line 118: 6062 Illegal instruction $process
$config
Here is the output with UseSpamAssassin= no
/usr/sbin/check_mailscanner
Starting MailScanner...
In Debugging mode, not forking...
Stopping now as you are debugging me.
On Monday 13 October 2003 10:52, you wrote:
> In MailScanner.conf, set
> Debug = yes
> then stop MailScanner. Put 1 message into the incoming queue and run
> check_mailscanner. This will process just that 1 message and print out any
> error messages you get. That will probably explain what's wrong. Also,
> check your maillog for any error messages from MailScanner.
>
> At 10:25 13/10/2003, you wrote:
> >First of all, let me say that when it works it works well, and I am very
> >pleased with the performance and features of MailScanner.
> >
> >I am having problems with MailScanner failing to start correctly when I
> > have it configured to use SpamAssassin . The first process starts and
> > appears to be OK, but never actually processes mail. Further instances of
> > MailScanner fail to start up correctly - ps shows [MailScanner <defunct>]
> > and top shows bursts of very high cpu usage.
> >
> >I have seen various references to this in the archives, but no explanation
> > of what causes it and therefore how to resolve the problem. I am coming
> > to the opinion that it is file permissions somewhere, but I don't know
> > where.
> >
> >I have had this situation twice now. The first time I fiddled around and
> >changed various settings and eventually it went away. I think that I
> > removed the RBL lists from the spam.assassin.prefs.conf file. On the
> > other hand I changed lots of things in increasing desperation, including
> > re-installing both MailScanner and spamassassin ;-)
> >
> >MailScanner then worked fine with SpamAssassin for a couple of weeks
> > before the same thing started happening.
> >
> >Thinking back to what was common to each situation, I had been trying to
> >manually learn the bayesian engine - set up scripts to run under cron, and
> >ran them maually as root to test them. It was after this that things
> > stopped working.
> >
> >This time, reinstalling SpamAssassin didn't improve things.
> >
> >For the record, I am running:
> >MailScanner from MailScanner-4.23-11.rpm.tar.gz
> >F-Prot as the anti-virus engine
> >SpamAssassin Mail-SpamAssassin-2.60.tar.gz
> >I also have:
> >razor-agents-2.36.tar.gz
> >razor-agents-sdk-2.03.tar.gz
> >
> >Any help that can be provided would be much appreciated. Anything that I
> > can provide by checking permissions, or by sending off
> > spam.assassin.prefs.conf files or MailScanner.conf file, or by running
> > traces I will be more than happy to do.
> >
> >Regards
> >Chris Wilber
--
If at first you don't succeed, destroy all the evidence that you tried.
More information about the MailScanner
mailing list