I recently attempted to upgrade on of my systems using the CPAN install
feature. Since I was running 2.20 and CPAN pulled down 2.42, I ran into
some very bad things. As soon as 2.42 was installed, the system locked
up. No errors, just complete system lock up. At the console, I came up
with the following:
1. Calling spamc/spamd without the MySQL daemon running resulted in
system lockup.
2. Calling spamc without spamd running resulted in system lockup.
3. Starting everything properly staved off system lockup for 3-5
minutes, but it would still lock up.
So I figured the 2.42 release just wasn't gonna cut it and copied the
2.20 spamc/spamd back into place. Something in the 2.42 upgrade process
caused this:
Failed to run MSG_ID_ADDED_BY_MTA_3 SpamAssassin test, skipping:
(Can't locate object method "check_for_mta_message_id_first" via
package "Mail::SpamAssassin::PerMsgStatus" (perhaps you forgot to load
"Mail::SpamAssassin::PerMsgStatus"?) at
../lib/Mail/SpamAssassin/PerMsgStatus.pm line 1529.
)
Failed to run SUSPECT_LIST_HEADERS SpamAssassin test, skipping:
(Can't locate object method "suspect_list_headers" via package
"Mail::SpamAssassin::PerMsgStatus" (perhaps you forgot to load
"Mail::SpamAssassin::PerMsgStatus"?) at
../lib/Mail/SpamAssassin/PerMsgStatus.pm line 1529.
)
Failed to run USERNAME_IN_SUBJECT SpamAssassin test, skipping:
(Can't locate object method "check_for_to_in_subject" via
package "Mail::SpamAssassin::PerMsgStatus" (perhaps you forgot to load
"Mail::SpamAssassin::PerMsgStatus"?) at
../lib/Mail/SpamAssassin/PerMsgStatus.pm line 1529.
)
There appears to be a failure notification for every test failing on the
same module (I snipped most of them out). I also attempted a 'make
install' to ensure that wasn't part of the problem, but it didn't change
anything.
End result was I simply removed the calls to spamc/spamd since the
machine was in production and I needed to get it back in service.
I seem to remember something on the list regarding critical failures on
upgrades from 2.20 to 2.4x, but couldn't google it out of the archives.
If I remember correctly, I need to install 2.3x, then upgrade to 2.42.
Can anyone offer more suggestions or assurances that I'm not on a path
to more system lockups? I'd also like a roll-back procedure. Anyone
know what I need to do to make PerMsgStatus.pm work right again?
And if anyone wants to tinker with the bugs some more, I'm running
Sendmail 8.11.6, procmail 3.15 and mysql 3.23.49 on RedHat Linux 6.2.
I'm planning a system wipe and reinstall of RH 7.3 and current versions
of the other software next week, but would like to implement spam
filtering sooner if it's safe.
Thanks,
--
Kip Turk, RHCE [EMAIL PROTECTED]
Systems Administrator/Killer of Spam/Writer of Code/Penguin Proponent
West Central Net - tel: 915.234.5678 / 800.695.9016 fax: 915.656.0071
-.-. --- -.. . / -- --- -. -.- . -.-- --..-- / .... .- -.-. -.- . .-.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
