You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2007/08/14 16:53:01 UTC
[Bug 5596] New: no loaded plugin implements 'check_main'
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5596
Summary: no loaded plugin implements 'check_main'
Product: Spamassassin
Version: 3.2.3
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: spamassassin
AssignedTo: dev@spamassassin.apache.org
ReportedBy: spamassassin@spam.monkeydyne.com
I've been getting occasional errors which only seem to be triggering every once
in a while, not all the time. (See procmail-log.txt)
What's more frustrating is that I can't seem to reproduce this error
interactively. If I take the same spam and run "spamassassin --lint -D" locally
to check for errors it analyzes the spam correctly. (See sa-output.txt)
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5596] no loaded plugin implements 'check_main'
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5596
------- Additional Comments From bubba@bubba.org 2007-08-15 18:48 -------
FYI, the server in your example (spunkymail-mx9.g.dreamhost.com) was having
issues with homefs at least since last Thursday (what actually maps your home
directory to /home/<user> on their system). I submitted a ticket earlier this
week and they said that they had it resolved. So, if you were using your own
version of spamassassin, installed in /home/<user>, then it's likely that you
wouldn't be able to find all of the required perl libs. I tried using whatever
HOME var was passed on the mail server (/mnt/polisher/vol/boot/...) so that even
if homefs wasn't working, things would still work, but wasn't able to
successfully change where spamassassin looks for libs.
If it still isn't working for you, I'd submit a ticket and explain what mail
server the message came from and say that your home directory is most likely not
being properly mapped with homefs. They should fix it up.
If you do find a good long-term solution, please let me know about it.
-Brian
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5596] no loaded plugin implements 'check_main'
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5596
------- Additional Comments From jm@jmason.org 2007-08-15 04:56 -------
(In reply to comment #5)
> > is that possible?
>
> It's dreamhost. Their servers and filers are oversold and constantly running at
> more than full capacity so it's entirely possible.
ah, yep. on my DH account, references to /vol/boot/ are all NFS volumes, so
I'll bet it's NFS problems.
> > If you could capture -D output from one of these failing cases, that'd probably
> > help, too. (-D output goes to stderr, whereas filtered text goes to stdout, so
> > it's possible to log -D output to a separate file from the procmailrc.)
>
> I'd love to do this but I don't know how. Can you give me a pointer?
sure -- lemme see if I can get some time together to do that RSN.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5596] no loaded plugin implements 'check_main'
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5596
------- Additional Comments From spamassassin@spam.monkeydyne.com 2007-08-14 07:56 -------
Created an attachment (id=4086)
--> (http://issues.apache.org/SpamAssassin/attachment.cgi?id=4086&action=view)
spamassassin -D --lint output from a message that produced errors via procmail
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5596] no loaded plugin implements 'check_main'
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5596
------- Additional Comments From spamassassin@spam.monkeydyne.com 2007-08-14 18:48 -------
> is that possible?
It's dreamhost. Their servers and filers are oversold and constantly running at
more than full capacity so it's entirely possible.
> If you could capture -D output from one of these failing cases, that'd probably
> help, too. (-D output goes to stderr, whereas filtered text goes to stdout, so
> it's possible to log -D output to a separate file from the procmailrc.)
I'd love to do this but I don't know how. Can you give me a pointer?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5596] no loaded plugin implements 'check_main'
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5596
------- Additional Comments From jm@jmason.org 2007-08-14 08:10 -------
hey mrneutron!
this looks a lot like an NFS problem, namely intermittent failure to load files:
Can't locate Mail/SpamAssassin/Util/Progress.pm in @INC (@INC contains:
/home/mailfilter/local/share/perl/5.8.4 /etc/perl /usr/local/lib/perl/5.8.4
/usr/local/share/perl/5.8.4 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8
/usr/share/perl/5.8 /usr/local/lib/site_perl) at
/mnt/slammer/vol/boot/spunky/hopei/mailfilter/local/bin/spamassassin line 81.
BEGIN failed--compilation aborted at
/mnt/slammer/vol/boot/spunky/hopei/mailfilter/local/bin/spamassassin line 81.
procmail: Program failure (2) of
"/mnt/slammer/vol/boot/spunky/hopei/mailfilter/local/bin/spamassassin"
check: no loaded plugin implements 'check_main': cannot scan! at
/mnt/slammer/vol/boot/spunky/hopei/mailfilter/local/share/perl/5.8.4/Mail/SpamAssassin/PerMsgStatus.pm
line 164.
procmail: Program failure (2) of
"/mnt/slammer/vol/boot/spunky/hopei/mailfilter/local/bin/spamassassin"
is that possible?
If you could capture -D output from one of these failing cases, that'd probably
help, too. (-D output goes to stderr, whereas filtered text goes to stdout, so
it's possible to log -D output to a separate file from the procmailrc.)
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5596] no loaded plugin implements 'check_main'
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5596
------- Additional Comments From spamassassin@spam.monkeydyne.com 2007-08-14 07:58 -------
Created an attachment (id=4087)
--> (http://issues.apache.org/SpamAssassin/attachment.cgi?id=4087&action=view)
Spam message used in the test run.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5596] no loaded plugin implements 'check_main'
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5596
------- Additional Comments From jm@jmason.org 2007-08-15 08:31 -------
ok, replace the "| spamassassin" stanza in your .procmailrc with something like
this:
:0fw: spamassassin.lock
* < 512000
| spamassassin -D 2>>spamassassin.log
that should write a debug logfile to "spamassassin.log". the thing to look out
for, then, is cases of files being there in some scans (in the "dbg: config:
read file" part of the log), and not appearing in others.
Here's another idea; would it be possible to copy the spamassassin lib dirs
(${HOME}/local/share/spamassassin, etc.) to /tmp ? /tmp is probably always a
local disk, therefore immune to NFS nastiness. (may be best to confirm that
it's caused by NFS first though.)
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 5596] no loaded plugin implements 'check_main'
Posted by bu...@bugzilla.spamassassin.org.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5596
------- Additional Comments From spamassassin@spam.monkeydyne.com 2007-08-14 07:53 -------
Created an attachment (id=4085)
--> (http://issues.apache.org/SpamAssassin/attachment.cgi?id=4085&action=view)
Procmail logfile showing errors
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.