ConfigServer Community Forum

Mailscanner apparently failed during the night, resulting in a large pending email queue. I have tried to re-install Mailscanner, with all Perl modules, but the installation fails with the following error messages:

Starting MailScanner daemons:
MailScanner: Can't locate Sys/SigAction.pm in @INC (@INC contains: /usr/mailscanner/lib /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 /usr/mailscanner/lib) at /usr/mailscanner/lib/MailScanner/ConfigSQL.pm line 38.
BEGIN failed--compilation aborted at /usr/mailscanner/lib/MailScanner/ConfigSQL.pm line 38.
Compilation failed in require at /usr/mailscanner/lib/MailScanner/Config.pm line 47.
Compilation failed in require at /usr/mailscanner/bin/MailScanner line 96.
BEGIN failed--compilation aborted at /usr/mailscanner/bin/MailScanner line 96.

Can anyone provide any thoughts on how to proceed with troubleshooting this? Thanks so much in advance!

RESOLVED

I should remember to run /scripts/checkperlmodules *whenever* I receive any notice of a missing or out-of-date perl module ... even after I've addressed that particular module.

Thanks ConfigServer for a *wonderful* product!

I have the exact same error so ran /scripts/checkperlmodules once and then tried to restart MailScanner but it still produced the exact same error.

How many times did you run it before this worked?

I have found mention that one should continue to run the script it it "runs clean"... whatever that means. Any further advise would be greatly appreciated.

You often do have to run /scripts/checkperlmodules multiple times. I ran it three times on a server I was looking at recently and it still didn't run clean (that means that it does not install any more modules, just reports that they are all up to date). I gave up and simply updated MailScanner, which fixed the problem.

You should force reinstall MailScanner (you can do this via the WHM front-end) because it will update/install any other perl modules it needs that may not be included in checkperlmodules.

Regards,
Sarah

Thanks Sarah, I've tried the /scripts/checkperlmodules more than 6 times now and still no luck. I was at an earlier version of the mailscanner and a few other CSF tools so did the upgrades to the latest versions and that hasn't helped. As there is no "force reinstall" in WHM I assume you mean click the "Force MailScanner Update" button in WHM -> Plugins -> ConfigServer Mailscanner FE?

So tried "force mailscanner update" and still no luck... Interesting results from the install process:

"Checking for multi-threaded Perl... (warning)

Using Signals in a multi-thread perl application is unsupported
by Sys::SigAction.

Sys::SigAction is not Supported on multi-threaded perls.

Read the following from perldoc perlthrtut:

...mixing signals and threads should not be attempted.
Implementations are platform-dependent, and even the
POSIX semantics may not be what you expect (and Perl
doesn't even give you the full POSIX API).

You are on your own...

Lincoln"

...and...

Writing Makefile for Sys::SigAction
cp lib/Sys/SigAction.pm blib/lib/Sys/SigAction.pm
Manifying blib/man3/Sys::SigAction.3pm
LBAXTER/Sys-SigAction-0.11.tar.gz
/usr/bin/make -- OK
Running make install
Installing /usr/lib/perl5/site_perl/5.8.8/Sys/SigAction.pm
Installing /usr/share/man/man3/Sys::SigAction.3pm
Appending installation info to /usr/lib/perl5/5.8.8/i386-linux-thread-multi/perllocal.pod
LBAXTER/Sys-SigAction-0.11.tar.gz
/usr/bin/make install UNINST=1 -- OK
perlmod--Install done
Done

That looks normal. When you run MailScanner in debug mode what errors do you see?

Ran the "Force Mailscanner Update" a second time and it finally worked. So Mailscanner is working again. Unfortunately still no idea why it failed in the first place or how to properly fix the problem. If any of the above methods were the proper solution one would expect them to work the first time not after running them multiple times.

If you have this problem these steps might work or they may not - there is no way to know it seems.