Page 1 of 1
Updated, MS won't start.
Posted: 01 Jul 2009, 03:45
by bear
Just updated MailScanner - v4.77.10 installed
ConfigServer MailScanner Script - v2.75 installed and up to date.
Now it won't start.
I'm getting these errors, and I'm not sure what to do now. Suggestions welcome.
root@*** [~]# service MailScanner restart && tail -f /var/log/maillog
Shutting down MailScanner daemons:
MailScanner: [FAILED]
Waiting for MailScanner to stop..
Starting MailScanner daemons:
MailScanner: Bareword "Cwd::getcwd" not allowed while "strict subs" in use at /usr/lib/perl5/site_perl/5.8.8/Archive/Zip.pm
line 552.
Compilation failed in require at /usr/mailscanner/lib/MailScanner/Message.pm line 48.
BEGIN failed--compilation aborted at /usr/mailscanner/lib/MailScanner/Message.pm line 48.
Compilation failed in require at /usr/mailscanner/bin/MailScanner line 107.
BEGIN failed--compilation aborted at /usr/mailscanner/bin/MailScanner line 107.
Posted: 01 Jul 2009, 03:49
by bear
Disregard.
As usual, after posting to ask, one finds the answer.
configserver.com/blog/index.php?itemid=419
Why
Posted: 01 Jul 2009, 04:47
by hostmart
Why on earth does mailscanner update to a perl mod that cant be used
This has caused me a lot of problems on a busy server and have had to switch mailscanner off because of it
I paid for program install and it has worked fine til latest upgrade.
It should be able to update without loosing my clients email and the program stopping
functioning when is something going to be done about this.
Posted: 01 Jul 2009, 07:48
by Sarah
hostmart wrote:Why on earth does mailscanner update to a perl mod that cant be used
This has caused me a lot of problems on a busy server and have had to switch mailscanner off because of it
I paid for program install and it has worked fine til latest upgrade.
It should be able to update without loosing my clients email and the program stopping
functioning when is something going to be done about this.
It is the fault of the perl module that has the bug, not MailScanner. Also it's not just a MailScanner update that triggers this problem, cPanel updates this perl module as well, so people who have not updated MailScanner but have updated cPanel have the same problem. There is no way for MailScanner or cPanel to know if a new version of a perl module has a bug.
Posted: 01 Jul 2009, 12:59
by bear
I'm definitely not placing blame on anyone here. These things happen, and in every case so far a solution has been available once you find the right thing to search on. Appreciate this resource being available.
Posted: 01 Jul 2009, 16:48
by ysizzle
I ran the update but im still getting an error and MS still shows itself as "stopped" Any advice?
service MailScanner restart && tail -f /var/log/maillog
Shutting down MailScanner daemons:
MailScanner:[FAILED]
Waiting for MailScanner to stop..
Starting MailScanner daemons:
MailScanner: [ OK ]
and its showing active connections to mail server but no one can get mail.
Posted: 01 Jul 2009, 17:19
by sawbuck
Check this blog entry:
http://www.configserver.com/blog/index.php?itemid=419
The perl installer --force option still picked up ver 1.29 for us so had to use the wget/make/install which worked.