ConfigServer Community Forum

Yes but we've always used CentOS 5 in fact it was the OS in place when cPanel & ConfigServer scripts were installed. So perhaps a recent update with CentOS perl modules may be at fault?


Anywhere that seems to have fixed it.

MailScanner Status: Running "In/Out" Scanning

I am sending test e-mails to confirm.

Yes its working again and the stuck mail was delivered so that is really good.

Thanks for all your help Sarah.

Apparently after a cpanel update this morning, we are also having this same issue. First time in many, many months that something like this has stopped up the mail on the server.

At first I got:

Aug 26 22:10:21 serenity MailScanner: succeeded
Aug 26 22:10:24 serenity MailScanner: MailScanner shutdown failed
Aug 26 22:10:26 serenity runuser: Starting MailScanner...
Aug 26 22:10:26 serenity runuser: File::Temp version 0.18 required--this is only version 0.16 at /usr/lib/perl5/site_perl/5.8.8/MIME/Tools.pm line 14.
Aug 26 22:10:26 serenity runuser: BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.8.8/MIME/Tools.pm line 14.
Aug 26 22:10:26 serenity runuser: Compilation failed in require at /usr/lib/perl5/site_perl/5.8.8/MIME/Parser.pm line 142.
Aug 26 22:10:26 serenity runuser: BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.8.8/MIME/Parser.pm line 142.
Aug 26 22:10:26 serenity runuser: Compilation failed in require at /usr/mailscanner/lib/MailScanner/MCPMessage.pm line 41.
Aug 26 22:10:26 serenity runuser: BEGIN failed--compilation aborted at /usr/mailscanner/lib/MailScanner/MCPMessage.pm line 41.
Aug 26 22:10:26 serenity runuser: Compilation failed in require at /usr/mailscanner/bin/MailScanner line 106.
Aug 26 22:10:26 serenity runuser: BEGIN failed--compilation aborted at /usr/mailscanner/bin/MailScanner line 106.
Aug 26 22:10:26 serenity runuser: Failed.
Aug 26 22:10:26 serenity MailScanner: check_mailscanner startup succeeded
Aug 26 22:10:26 serenity MailScanner: succeeded
Aug 26 22:14:40 serenity MailScanner: MailScanner shutdown failed

I ran /scripts/checkperlmodules and forced an update to MailScanner from MSFE

Then it was saying:

Aug 26 22:29:44 serenity runuser: Failed.
Aug 26 22:29:44 serenity MailScanner: check_mailscanner startup succeeded
Aug 26 22:29:44 serenity MailScanner: succeeded
Aug 26 22:34:44 serenity MailScanner: MailScanner shutdown failed
Aug 26 22:34:44 serenity runuser: stdin: is not a tty
Aug 26 22:34:44 serenity runuser: Starting MailScanner...
Aug 26 22:34:45 serenity runuser: dualvar is only available with the XS version of Scalar::Util at /usr/lib/perl5/site_perl/5.8.8/Compress/Zlib.pm line 9
Aug 26 22:34:45 serenity runuser: BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.8.8/Compress/Zlib.pm line 9.
Aug 26 22:34:45 serenity runuser: Compilation failed in require at /usr/mailscanner/lib/MailScanner/SA.pm line 42.
Aug 26 22:34:45 serenity runuser: BEGIN failed--compilation aborted at /usr/mailscanner/lib/MailScanner/SA.pm line 42.
Aug 26 22:34:45 serenity runuser: Compilation failed in require at /usr/mailscanner/bin/MailScanner line 109.
Aug 26 22:34:45 serenity runuser: BEGIN failed--compilation aborted at /usr/mailscanner/bin/MailScanner line 109.
Aug 26 22:34:45 serenity runuser: Failed.
Aug 26 22:34:45 serenity MailScanner: check_mailscanner startup succeeded
Aug 26 22:34:45 serenity MailScanner: succeeded


But, succeeded in this case means absolutely nothing. I assume the 'did it succeed' check doesn't check much.

I ran the /scripts/checkperlmodules again, and added /scripts/perlinstaller --force Scalar::Util

That did not work itself, however, forcing another update of MailScanner from the MSFE made it work.


I'm currently listening to my iPhone sms bleeping off the hilt at the moment, and a brief look at the queued mail is showing alerts of other things failing (not just MailScanner) due to perl problems.

I'm not sure why I wasn't alerted to the MailScanner outage by direct sms (ie. not from the email->sms notices I also get, which obviously would be stuck in the queue..but from the internal cpanel sms alerter daemon). I'm looking into that, as obviously one of the most important services being down, mail, its not very useful to mail an alert

Does anything below look improper at a glance?



cPanel 11.24.5-C38506 - WHM 11.24.2 - X 3.9
CENTOS 4.8 i686 standard on serenity

(some output from the MS recompile)
...
Expanding new distribution...
Done
Installing/Upgrading Perl Modules (this could take a while)...
Method: Perl Expect
commit: wrote '/usr/lib/perl5/5.8.8/CPAN/Config.pm'
CPAN: Storable loaded ok (v2.21)
Going to read '/home/.cpan/Metadata'
Database was generated on Wed, 26 Aug 2009 06:27:11 GMT
ExtUtils::MakeMaker is up to date (6.54).
Net::CIDR is up to date (0.13).
MIME::Base64 is up to date (3.08).
Pod::Escapes is up to date (1.04).
Pod::Simple is up to date (3.08).
Test::Pod is up to date (1.40).
Test::Harness is up to date (3.17).
Test::Simple is up to date (0.92).
cPCPAN: Module (File::Spec) holdback (3.30 held back to 3.25)
File::Spec is up to date (3.25).
File::Temp is up to date (0.22).
HTML::Tagset is up to date (3.20).
HTML::Parser is up to date (3.62).
Convert::TNEF is up to date (0.17).
cPCPAN: Module (Compress::Zlib) holdback (2.020 held back to 2.019)
Compress::Zlib is up to date (2.019).
Archive::Zip is up to date (1.30).
Convert::BinHex is up to date (1.119).
Scalar::Util is up to date (1.21).
Storable is up to date (2.21).
DBI is up to date (1.609).
DBD::SQLite is up to date (1.25).
Getopt::Long is up to date (2.38).
Time::HiRes is up to date (1.9719).
Filesys::Df is up to date (0.92).
Math::BigInt is up to date (1.89).
Math::BigRat is up to date (0.22).
bignum is up to date (0.23).
Net::IP is up to date (1.25).
Sys::Hostname::Long is up to date (1.4).
Sys::Syslog is up to date (0.27).
cPCPAN: Module (Digest::MD5) holdback (2.39 held back to 2.36)
Digest::MD5 is up to date (2.36).
MIME::Tools is up to date (5.427).
Mail::Header is up to date (2.04).
Date::Format is up to date (2.22).
IO::Stringy is up to date (2.110).
cPCPAN: Module (Mail::SpamAssassin) holdback (3.002005 held back to 3.2.4)
Mail::SpamAssassin is up to date (3.002004).
Mail::SPF::Query is up to date (1.999.1).
Net::Ident is up to date (1.20).
IO::Socket::INET6 is up to date (2.56).
IO is up to date (1.25).
IO::Socket::SSL is up to date (1.30).
IP::Country::Fast is up to date (604.001).
DB_File is up to date (1.820).
perlmod--Install done
Done
....
Detected spam handling in acls, disabling spamassassin in routers & transports!.
SpamAssassin method remains unchanged
Configured options list is: queue_only_override|log_selector
Provided options list is: hostlist senderverifybypass_hosts|hostlist skipsmtpcheck_hosts|hostlist spammeripblocks|hostlist backupmx_hosts|hostlist trustedmailhosts|domainlist user_domains|smtp_receive_timeout|ignore_bounce_errors_after|timeout_frozen_after|auto_thaw|callout_domain_negative_expire|callout_negative_expire|tls_require_ciphers|acl_smtp_connect|acl_smtp_mail|acl_smtp_notquit|spamd_address
Exim Insert Regex is: virtual_userdelivery|virtual_aliases|lookuphost|virtual_user|address_pipe|localuser
Exim Replace Regex is: virtual_sa_user|sa_localuser|virtual_sa_userdelivery|local_sa_delivery|central_filter|central_user_filter|democheck|fail_remote_domains|fixed_login|fixed_plain|has_alias_but_no_mailbox_discarded_to_prevent_loop|literal|local_delivery|local_delivery_spam|localuser|localuser_spam|lookuphost|remote_smtp|userforward|virtual_aliases|virtual_aliases_nostar|virtual_user|virtual_user_spam|virtual_userdelivery|virtual_userdelivery_spam
Exim Match Insert Regex is: quota_directory|maildir_format
Skipping lookuphost insert as it requires boxtrapper and it is disabled or unavailable.
Skipping virtual_user insert as it requires boxtrapper and it is disabled or unavailable.
Skipping localuser insert as it requires boxtrapper and it is disabled or unavailable.
Skipping virtual_userdelivery insert as it requires boxtrapper and it is disabled or unavailable.
Exim version 4.69 #1 built 16-Mar-2009 14:44:43
...

Sarah wrote:Our MailScanner install/configuration is certainly compatible with the version of WHM/cPanel you are running. However, we cannot cater for every possible issue introduced by a cPanel upgrade or an OS upgrade (often due to poor configuration of the OS update system). We do our best to help clients fix problems as soon as we are aware of them. As you are the first person to report this problem at this time, it doesn't look like it is a widespread issue so it's not something we can provide a blanket fix for. Obviously MailScanner requires this perl module since it is reporting the problem in the error message.

To force install this perl module do this in ssh (logged in as root):

/scripts/perlinstaller --force File::Temp

Then restart MailScanner.

If that doesn't fix it, in ssh do:

/scripts/checkperlmodules

And then restart MailScanner. You might also need to manually upgrade MailScanner using the full perl module check (the upgrade in the WHM front-end does not do the full perl module check). This is how to do it:

rm -Rfv msinstall*
wget .................
tar -xzf msinstall.tar.gz
cd msinstall/
sh install.sh

Select option 1 for full perl module installation.

whitewlf, I'm not really sure what you're asking since you got MailScanner working and the cPanel sms alert system is nothing to do with MailScanner. The output from the MailScanner update looks fine. Obviously force installing any perl modules that are generating errors is what normally must be done to resolve perl issues like this. Also I assume at some point you did a manual MailScanner update and took option 1 to do the full perl module update. Otherwise, is there anything else that is still causing problems?

Regards,
Sarah

Was simply adding things to the reply as they appeared, and, posted it as it resolved simply to add input and clarification to others who may hit this snag, as it was update/cpanel generated. I found this thread by simple search myself.

I was only hoping someone may look over the output, which you did, and give it a tertiary nod that none of the versions, especially the cpanel holdbacks, looked ok.

I did not use the manual option you described, however.. that output was from my MSFE force update. It is working ok, so far to my knowledge, just using the MSFE default.

For clarity, I will note, the second MS update included warnings about SSLeay (which is version 1.30, and it recommended 1.33 I believe, and something else about international certificates.. which suggested adding Net::libIDN ... which I also did. Before I could check for anything else, however.. I accidentally reloaded the page, which re-did the update.. and came out with no warnings at all, even the SSLeay. MS was running fine, however, before the double-update.

/scripts/perlinstaller --force Net::LibIDN

Thank you for your quick reply, all seems good. I just wish I had gotten to the queue quicker to delete all the trapped sms alerts... a good many went through. ding.ding. ;P

Hi,

For what it's worth, this has happened with my server, also. According to my NOC's tech (ServInt), there was a problem with a cPanel upgrade a couple of days ago. I only noticed something odd while checking another problem....and I saw the installed perl version was 5.8.5.

I upgraded Perl back to where it was....and MailScanner was running fine. Then I think the NOC tech did something (he said he applied a fix) and suddenly MailScanner is dead.

So I appreciate this post. It's been at least 2 years since mailScanner has refused to start....I forgot what to do!


OK....I spoke too soon. I've done EVERYTHING suggested in this thread. Nothing is working. And to top it off, the tech at ServInt is claiming they "don't support MailScanner", and it's "use at your own risk" software and "no recommended" (even though I've seen ServInt employees recommend it - and your services - in the forums). I've never had a problem with it for the last several years (since 2005-2006?). Suddenly now it's just dead.

It claims to restart, but it's not.

I'm Googling like crazy, I've uninstalled/done a full reinstall twice now of MS....everything suggested to do when this happens...anyone that could help, I'd appreciate it.

I'm on CentOS 4.8 (was just upgraded to 4.8 a few days ago), the lastest MailScanner, etc, and now again on Perl5.8.8.

Just an update...running MailScanner in debug mode helped (other suggestions in that FAQ don't seem to be compatible with cP11.24).

http://www.configserver.com/techfaq/faq ... =14&page=1

I get "Can't locate Digest/MD5.pm", so I'm trying to find out why/how to install as "/scripts/perlinstaller --force Digest/MD5.pm" doesn't work.
I was able to install Digest::MD5, or so I thought, from CPAN:
It said Digest::HMAC_MD5 is up to date. The problem is, when I run MS in debug mode again, I get exactly the same error, that it can't locate Digest::MD5.pm.

Hi Mara,

From reading your forum post it appears you haven't installed the Digest/MD5 module correctly. Here's how you should install it:

/scripts/perlinstaller --force Digest::MD5

In general, if you want to install a perl module, replace the / with :: and drop the .pm from the end when you use the perlinstaller command.

Let me know if that works. It's possible you'll get some new errors about other perl modules once the Digest::MD5 module is installed.

Regards,
Sarah

Also, Mara, you state that some items in the FAQ are not compatible with WHM 11.24.x, could you please tell me specifically which items? Thanks.
http://www.configserver.com/techfaq/index.php?faqid=14

Regards,
Sarah

Sarah wrote:Hi Mara,

From reading your forum post it appears you haven't installed the Digest/MD5 module correctly. Here's how you should install it:

/scripts/perlinstaller --force Digest::MD5

In general, if you want to install a perl module, replace the / with :: and drop the .pm from the end when you use the perlinstaller command.

Let me know if that works. It's possible you'll get some new errors about other perl modules once the Digest::MD5 module is installed.

Regards,
Sarah

Thank you so much! Yes, that worked...although in the meantime I rebuilt the RPMs and reinstalled Perl5.8.8. Seems to have gone well...all except for the fact cPanel's now dead. Once I get cPanel back up, I'll try reinstalling MS.

Thank you for your help!