| View previous topic :: View next topic |
| Author |
Message |
rjreb
n00b
Joined: 19 Aug 2003
Posts: 40
|
 Posted: Tue Sep 09, 2003 3:04 am Post subject: SpamAssassin 2.6 upgrade fails to start |
 |
|
I just upgraded my mail server to SpamAssassin to 2.6 from 2.55 and now when I try to start it I get the following message
| Quote: | * Starting spamd...
Undefined subroutine &Mail::SpamAssassin::Util::untaint_var called at /usr/bin/spamd line 94.
* Failed to start spamd |
Any suggestions? |
|
| Back to top |
|
 |
Coucou13
n00b
Joined: 16 Sep 2003
Posts: 3
|
| Posted: Tue Sep 16, 2003 10:09 am Post subject: |
|
|
Hello
I had the same problem, here is how I solved it :
perl -V says :
[...]
@INC:
/etc/perl
/usr/lib/perl5/site_perl/5.8.0/powerpc-linux
/usr/lib/perl5/site_perl/5.8.0
/usr/lib/perl5/site_perl/5.6.1
/usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.0/powerpc-linux
/usr/lib/perl5/vendor_perl/5.8.0
/usr/lib/perl5/vendor_perl
/usr/lib/perl5/5.8.0/powerpc-linux
/usr/lib/perl5/5.8.0
/usr/local/lib/site_perl
/usr/lib/perl5/site_perl/5.6.1
In fact, I once had SpamAssassin with perl 5.6.1 installed. Upgrading to perl 5.8.0 created a strange mess and I some old libs are not removed upgrading modules. Mail-SpamAssassin-2.60 is installed in /usr/lib/perl5/vendor_perl/5.8.0 but I still had on old version in /usr/lib/perl5/site_perl/5.6.1 , removing it solved the problem.
I hope this will help. |
|
| Back to top |
|
|
brain
Apprentice
Joined: 16 May 2002
Posts: 229
Location: Farmington Hills, MI
|
| Posted: Thu Oct 16, 2003 6:26 pm Post subject: |
|
|
Having the same problem here, but I don't seem to have the old perl install issues mentioned here.
Hmm...
_________________
--brain |
|
| Back to top |
|
|
daoist
n00b
Joined: 14 May 2003
Posts: 28
|
| Posted: Fri Oct 17, 2003 3:39 pm Post subject: |
|
|
i upgraded to spamassassin 2.6 too, and I think the ebuild must be a little screwy. checking the spamassassin script it's got some messed up options in it, such as
| Code: | my $PREFIX = '/var/tmp/portage/Mail-SpamAssassin-2.60-r1/image//usr'; # substituted at 'make' time
my $DEF_RULES_DIR = '/var/tmp/portage/Mail-SpamAssassin-2.60-r1/image//usr/share/spamassassin'; # substituted at 'make' time
my $LOCAL_RULES_DIR = '/var/tmp/portage/Mail-SpamAssassin-2.60-r1/image//usr/etc/mail/spamassassin'; # substituted at 'make' time
|
I'm not a spamassassin expert, but it looks like a goof up. spamassassin shouldn't be checking /var/tmp/portage/ for anything during run-time. there's a few other places in the spamassassin file where its got the path wrong too. I'm afraid the ebuild must have set these things incorrectly, i have no idea if spamc and spamd are affected as well.
modifying the messed up paths in spamassassin was easy. unfortunately i don't know how the ebuild system works so I don't know how to fix that. |
|
| Back to top |
|
|
|
Networking & Security
