MS says running but not scanning incoming que

[compcreate]

Hi,
I have been using MS for a number of years without issue. Lately I notice that mail stops flowing. I login to my whm and the load is fine, everything looks ok, the services are all running and check out ok. I go to plugins msfe and it says its running and happy. I check the status its ok. I go to mail ques and the incoming que is piling up. I go back to msfe and restart mailscanner and the mail starts to flow again instantly. This happens 3-4 times per day.

I started to go through the troubleshooting found in the techfag:
techfaq/faqlist.php?catid=5&faqid=14&page=1

and in step 7 when I run this:
/usr/mscpanel/mscheck. pl

I get this:

Unable to initialise database connection: Access denied for user 'mailwatch'@'localhost' (using password: YES) at /usr/mailscanner/lib/MailScanner/MailWatch.pm line 83
Could not use Custom Function code MailScanner::CustomConfig::InitMailWatchLogging, it could not be "eval"ed. Make sure the module is correct with perl -wc (Error: Can't call method "prepare" on an undefined value at /usr/mailscanner/lib/MailScanner/MailWatch.pm line 86.
) at /usr/mailscanner/lib/MailScanner/Config.pm line 1061

I don't know if this is part of the issue or not. The rest of the diagnostics on that page seem to all pan out fine. This is the only thing I found to give me an error.

Appreciate any help.
Thanks

[Sarah]

and in step 7 when I run this:
/usr/mscpanel/mscheck. pl

I get this:

Unable to initialise database connection: Access denied for user 'mailwatch'@'localhost' (using password: YES) at /usr/mailscanner/lib/MailScanner/MailWatch.pm line 83
Could not use Custom Function code MailScanner::CustomConfig::InitMailWatchLogging, it could not be "eval"ed. Make sure the module is correct with perl -wc (Error: Can't call method "prepare" on an undefined value at /usr/mailscanner/lib/MailScanner/MailWatch.pm line 86.
) at /usr/mailscanner/lib/MailScanner/Config.pm line 1061

I don't know if this is part of the issue or not. The rest of the diagnostics on that page seem to all pan out fine. This is the only thing I found to give me an error.

No, this is not likely to be causing any problem with MailScanner itself, it just means that mailwatch will not be logging. I assume you see no errors when you run mailscanner in debug, or any errors whatsoever in the maillog?