Page 1 of 2

MailScanner starting loop?

Posted: 11 Dec 2006, 11:59
by flash7
I have a problem with MailScanner on RHEL x86_64
The Tail Maillog from ConfigServer MailScanner Front-End says

Code: Select all

Dec 11 12:33:28 sw2 MailScanner[9472]: MailScanner E-Mail Virus Scanner version 4.56.8 starting... 
Dec 11 12:33:28 sw2 MailScanner[9472]: Read 695 hostnames from the phishing whitelist 
Dec 11 12:33:28 sw2 MailScanner[9472]: Config: calling custom init function MailWatchLogging 
Dec 11 12:33:28 sw2 MailScanner[9472]: Started SQL Logging child 
Dec 11 12:33:28 sw2 MailScanner[9472]: Using SpamAssassin results cache 
Dec 11 12:33:28 sw2 MailScanner[9472]: Connected to SpamAssassin cache database 
Dec 11 12:33:39 sw2 MailScanner[9479]: MailScanner E-Mail Virus Scanner version 4.56.8 starting... 
Dec 11 12:33:39 sw2 MailScanner[9479]: Read 695 hostnames from the phishing whitelist 
Dec 11 12:33:39 sw2 MailScanner[9479]: Config: calling custom init function MailWatchLogging 
Dec 11 12:33:39 sw2 MailScanner[9479]: Started SQL Logging child 
Dec 11 12:33:39 sw2 MailScanner[9479]: Using SpamAssassin results cache 
Dec 11 12:33:39 sw2 MailScanner[9479]: Connected to SpamAssassin cache database 
Dec 11 12:33:50 sw2 MailScanner[9487]: MailScanner E-Mail Virus Scanner version 4.56.8 starting... 
Dec 11 12:33:50 sw2 MailScanner[9487]: Read 695 hostnames from the phishing whitelist 
Dec 11 12:33:50 sw2 MailScanner[9487]: Config: calling custom init function MailWatchLogging 
Dec 11 12:33:50 sw2 MailScanner[9487]: Started SQL Logging child 
Dec 11 12:33:50 sw2 MailScanner[9487]: Using SpamAssassin results cache 
Dec 11 12:33:50 sw2 MailScanner[9487]: Connected to SpamAssassin cache database 
Dec 11 12:34:01 sw2 MailScanner[9516]: MailScanner E-Mail Virus Scanner version 4.56.8 starting... 
Dec 11 12:34:01 sw2 MailScanner[9516]: Read 695 hostnames from the phishing whitelist 
Dec 11 12:34:01 sw2 MailScanner[9516]: Config: calling custom init function MailWatchLogging 
Dec 11 12:34:01 sw2 MailScanner[9516]: Started SQL Logging child 
Dec 11 12:34:01 sw2 MailScanner[9516]: Using SpamAssassin results cache 
Dec 11 12:34:01 sw2 MailScanner[9516]: Connected to SpamAssassin cache database 
Dec 11 12:34:08 sw2 MailScanner[9564]: MailScanner E-Mail Virus Scanner version 4.56.8 starting... 
Dec 11 12:34:08 sw2 MailScanner[9564]: Read 695 hostnames from the phishing whitelist 
Dec 11 12:34:08 sw2 MailScanner[9564]: Config: calling custom init function MailWatchLogging 
Dec 11 12:34:08 sw2 MailScanner[9564]: Started SQL Logging child 
Dec 11 12:34:08 sw2 MailScanner[9564]: Using SpamAssassin results cache 
Dec 11 12:34:08 sw2 MailScanner[9564]: Connected to SpamAssassin cache database 
Dec 11 12:34:19 sw2 MailScanner[9575]: MailScanner E-Mail Virus Scanner version 4.56.8 starting... 
Dec 11 12:34:19 sw2 MailScanner[9575]: Read 695 hostnames from the phishing whitelist 
Dec 11 12:34:19 sw2 MailScanner[9575]: Config: calling custom init function MailWatchLogging 
Dec 11 12:34:19 sw2 MailScanner[9575]: Started SQL Logging child 
Dec 11 12:34:19 sw2 MailScanner[9575]: Using SpamAssassin results cache 
Dec 11 12:34:19 sw2 MailScanner[9575]: Connected to SpamAssassin cache database 
Dec 11 12:34:30 sw2 MailScanner[9582]: MailScanner E-Mail Virus Scanner version 4.56.8 starting... 
Dec 11 12:34:30 sw2 MailScanner[9582]: Read 695 hostnames from the phishing whitelist 
Dec 11 12:34:30 sw2 MailScanner[9582]: Config: calling custom init function MailWatchLogging 
Dec 11 12:34:30 sw2 MailScanner[9582]: Started SQL Logging child 
Dec 11 12:34:30 sw2 MailScanner[9582]: Using SpamAssassin results cache 
Dec 11 12:34:30 sw2 MailScanner[9582]: Connected to SpamAssassin cache database 
Dec 11 12:34:41 sw2 MailScanner[9591]: MailScanner E-Mail Virus Scanner version 4.56.8 starting... 
Dec 11 12:34:41 sw2 MailScanner[9591]: Read 695 hostnames from the phishing whitelist 
Dec 11 12:34:41 sw2 MailScanner[9591]: Config: calling custom init function MailWatchLogging 
Dec 11 12:34:41 sw2 MailScanner[9591]: Started SQL Logging child 
Dec 11 12:34:41 sw2 MailScanner[9591]: Using SpamAssassin results cache 
Dec 11 12:34:41 sw2 MailScanner[9591]: Connected to SpamAssassin cache database 
Dec 11 12:34:52 sw2 MailScanner[9625]: MailScanner E-Mail Virus Scanner version 4.56.8 starting... 
Dec 11 12:34:52 sw2 MailScanner[9625]: Read 695 hostnames from the phishing whitelist 
Dec 11 12:34:52 sw2 MailScanner[9625]: Config: calling custom init function MailWatchLogging 
Dec 11 12:34:52 sw2 MailScanner[9625]: Started SQL Logging child 
Dec 11 12:34:52 sw2 MailScanner[9625]: Using SpamAssassin results cache 
Dec 11 12:34:52 sw2 MailScanner[9625]: Connected to SpamAssassin cache database 
Dec 11 12:35:03 sw2 MailScanner[9646]: MailScanner E-Mail Virus Scanner version 4.56.8 starting... 
Dec 11 12:35:03 sw2 MailScanner[9646]: Read 695 hostnames from the phishing whitelist 
Dec 11 12:35:03 sw2 MailScanner[9646]: Config: calling custom init function MailWatchLogging 
Dec 11 12:35:03 sw2 MailScanner[9646]: Started SQL Logging child 
Dec 11 12:35:03 sw2 MailScanner[9646]: Using SpamAssassin results cache 
Dec 11 12:35:03 sw2 MailScanner[9646]: Connected to SpamAssassin cache database 
Dec 11 12:35:14 sw2 MailScanner[9661]: MailScanner E-Mail Virus Scanner version 4.56.8 starting... 
Dec 11 12:35:14 sw2 MailScanner[9661]: Read 695 hostnames from the phishing whitelist 
Dec 11 12:35:14 sw2 MailScanner[9661]: Config: calling custom init function MailWatchLogging 
Dec 11 12:35:14 sw2 MailScanner[9661]: Started SQL Logging child 
Dec 11 12:35:14 sw2 MailScanner[9661]: Using SpamAssassin results cache 
Dec 11 12:35:14 sw2 MailScanner[9661]: Connected to SpamAssassin cache database 
Dec 11 12:35:25 sw2 MailScanner[9838]: MailScanner E-Mail Virus Scanner version 4.56.8 starting... 
Dec 11 12:35:25 sw2 MailScanner[9838]: Read 695 hostnames from the phishing whitelist 
Dec 11 12:35:25 sw2 MailScanner[9838]: Config: calling custom init function MailWatchLogging 
Dec 11 12:35:25 sw2 MailScanner[9838]: Started SQL Logging child 
Dec 11 12:35:25 sw2 MailScanner[9838]: Using SpamAssassin results cache 
Dec 11 12:35:25 sw2 MailScanner[9838]: Connected to SpamAssassin cache database 
Dec 11 12:35:36 sw2 MailScanner[9848]: MailScanner E-Mail Virus Scanner version 4.56.8 starting... 
Dec 11 12:35:36 sw2 MailScanner[9848]: Read 695 hostnames from the phishing whitelist 
Dec 11 12:35:36 sw2 MailScanner[9848]: Config: calling custom init function MailWatchLogging 
Dec 11 12:35:36 sw2 MailScanner[9848]: Started SQL Logging child 
Dec 11 12:35:36 sw2 MailScanner[9848]: Using SpamAssassin results cache 
Dec 11 12:35:36 sw2 MailScanner[9848]: Connected to SpamAssassin cache database 
What causing this loop?

Before I resolved to reinstall MailScanner, but now is very frequently issue...

Thanks

Posted: 11 Dec 2006, 14:04
by flash7
Well, I reinstalled MailScanner because the server can't send e-mail.

Now I am confused if the problem is related to MailScanner or Exim

Code: Select all

Dec 11 12:05:23 sw2 mailnull: Process did not exit cleanly, returned 1 with signal 0 
Dec 11 12:05:56 sw2 last message repeated 3 times
Dec 11 12:07:02 sw2 last message repeated 6 times
Dec 11 12:08:08 sw2 last message repeated 6 times
Dec 11 12:09:14 sw2 last message repeated 6 times
Dec 11 12:10:21 sw2 last message repeated 6 times
Dec 11 12:11:27 sw2 last message repeated 6 times
Dec 11 12:12:33 sw2 last message repeated 6 times
Dec 11 12:13:39 sw2 last message repeated 6 times
Dec 11 12:13:50 sw2 mailnull: Process did not exit cleanly, returned 1 with signal 0 
Dec 11 12:14:23 sw2 last message repeated 3 times
Dec 11 12:15:29 sw2 last message repeated 6 times
Dec 11 12:16:35 sw2 last message repeated 6 times
Dec 11 12:17:41 sw2 last message repeated 6 times
Dec 11 12:18:47 sw2 last message repeated 6 times
Dec 11 12:19:53 sw2 last message repeated 6 times
Dec 11 12:20:59 sw2 last message repeated 6 times
Dec 11 12:21:54 sw2 last message repeated 5 times

Posted: 11 Dec 2006, 15:18
by Sarah
I'm not sure what is causing this problem. Is MailScanner running? You could try running it in debug mode. Edit /usr/mailscanner/etc/MailScanner.conf and set Debug to yes. Save the file and then do the following:

Code: Select all

service MailScanner stop
killall -9 MailScanner
/usr/mailscanner/bin/MailScanner
This should give you some clues as to what the problem is, if it is a problem with MailScanner.

Remember to set Debug back to no in the conf file afterwards.

Posted: 11 Dec 2006, 15:34
by flash7
MailScanner is running, however all e-mails of all accounts (root also) are frozen.
Then I reinstall MailScanner and all work great.

Next time I set the debug mode so I can post here the output.

Thank you

Posted: 11 Dec 2006, 16:55
by Sarah
One thing that we've seen cause repetitive problems with MailScanner, i.e. after every cpanel update, is perl module problems if you are running a 64-bit OS. We've seen problems with 64-bit OS's and perl module conflicts on a number of servers. If this is the case, then there's not much we can suggest, I'm afraid.

Posted: 13 Dec 2006, 04:02
by mattpark
Dec 13 03:56:13 alpha MailScanner[5347]: Config: calling custom init function MailWatchLogging
Dec 13 03:56:13 alpha MailScanner[5347]: Started SQL Logging child
Dec 13 03:56:13 alpha MailScanner[5347]: Using SpamAssassin results cache
Dec 13 03:56:13 alpha MailScanner[5347]: Connected to SpamAssassin cache database
Dec 13 03:56:24 alpha MailScanner[5354]: MailScanner E-Mail Virus Scanner version 4.56.8 starting...
Dec 13 03:56:24 alpha MailScanner[5354]: Read 695 hostnames from the phishing whitelist
Dec 13 03:56:24 alpha MailScanner[5354]: Config: calling custom init function MailWatchLogging
Dec 13 03:56:24 alpha MailScanner[5354]: Started SQL Logging child
Dec 13 03:56:24 alpha MailScanner[5354]: Using SpamAssassin results cache
Dec 13 03:56:24 alpha MailScanner[5354]: Connected to SpamAssassin cache database
Dec 13 03:56:35 alpha MailScanner[5362]: MailScanner E-Mail Virus Scanner version 4.56.8 starting...
Dec 13 03:56:35 alpha MailScanner[5362]: Read 695 hostnames from the phishing whitelist
Dec 13 03:56:35 alpha MailScanner[5362]: Config: calling custom init function MailWatchLogging
Dec 13 03:56:35 alpha MailScanner[5362]: Started SQL Logging child
Dec 13 03:56:35 alpha MailScanner[5362]: Using SpamAssassin results cache
Dec 13 03:56:35 alpha MailScanner[5362]: Connected to SpamAssassin cache database
Dec 13 03:56:46 alpha MailScanner[5501]: MailScanner E-Mail Virus Scanner version 4.56.8 starting...
Dec 13 03:56:46 alpha MailScanner[5501]: Read 695 hostnames from the phishing whitelist
Dec 13 03:56:46 alpha MailScanner[5501]: Config: calling custom init function MailWatchLogging
Yeah im getting this too on my server. Just been through and upgraded everything to latest build (MSFE, MS, CLAMAV), and converted to maildir. Mail comes in to the server fine and just sits pending mail scanner.

The only way to unfreeze the mail is by:

Code: Select all

service MailScanner stop
killall -9 MailScanner
/usr/mailscanner/bin/MailScanner
Could do with a little advice on this one as im running out of ideas.....

Oh yeah im 64bit too.

Thanks

Matt

Posted: 13 Dec 2006, 10:41
by Sarah
Matt, have you tried running it in debug mode? As we said, 64-bit OS's do often cause problems with perl module dependencies. You may be able to see in debug mode exactly what is causing it to trip up.

Posted: 13 Dec 2006, 14:27
by mattpark
Sarah,
Debug at the command line give back:
In Debugging mode, not forking...
Ignore errors about failing to find EOCD signature
Stopping now as you are debugging me.
commit ineffective with AutoCommit enabled at /usr/mailscanner/lib/MailScanner/MailWatch.pm line 94, <CLIENT> line 93.
Commmit ineffective while AutoCommit is on at /usr/mailscanner/lib/MailScanner/MailWatch.pm line 94, <CLIENT> line 93.

All works fine until the cPanel update, then mail just sits in the pending queue.

If i stop and killall, back to normal again...
Dec 13 14:19:20 alpha MailScanner[2784]: MailScanner E-Mail Virus Scanner version 4.56.8 starting...
Dec 13 14:19:20 alpha MailScanner[2784]: Read 695 hostnames from the phishing whitelist
Dec 13 14:19:20 alpha MailScanner[2784]: Config: calling custom init function MailWatchLogging
Dec 13 14:19:20 alpha MailScanner[2784]: Started SQL Logging child
Dec 13 14:19:21 alpha MailScanner[2784]: Using SpamAssassin results cache
Dec 13 14:19:21 alpha MailScanner[2784]: Connected to SpamAssassin cache database
Dec 13 14:19:25 alpha MailScanner[2784]: Using locktype = posix
Dec 13 14:19:25 alpha MailScanner[2784]: Creating hardcoded struct_flock subroutine for linux (Linux-type)

Posted: 13 Dec 2006, 16:43
by Sarah
The only thing I can suggest is to modify /scripts/postupcp to add the commands that you have found will fix the problem, so that it does it after every cpanel update. Don't know if that will work, as postupcp should already contain perl /usr/mscpanel/mscheck.pl which I think restarts MailScanner, but it might be worth a try.

it is a bit of a pain...

Posted: 15 Dec 2006, 05:27
by xisn
We also have this same issue, the only way I know to reolve this (currently) is to run the installer and choose option #2. For some reason this fixes it for us. We have automated this process a little bit and will be making a custom script to fully automate this process soon.