MailScanner oddly inactive for two weeks

[misteride]

MailScanner became oddly inactive on March 4. No more quarantine folders, no incoming, no scanning. All messages glide to the inbox.
I have run in debug mode. Here is the result:

In Debugging mode, not forking...
Trying to setlogsock(unix)
Argument "0.70_01" isn't numeric in numeric lt (<) at /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Dns.pm line 645.
Building a message batch to scan...
[No Further Activity}
*****************
Here is the output in maillog:
Mar 14 13:02:08 server MailScanner[31651]: MailScanner E-Mail Virus Scanner version 4.84.5 starting...
Mar 14 13:02:08 server MailScanner[31651]: Reading configuration file /usr/mailscanner/etc/MailScanner.conf
Mar 14 13:02:08 server MailScanner[31651]: Reading configuration file /usr/mailscanner/etc/conf.d/README
Mar 14 13:02:08 server MailScanner[31651]: Read 869 hostnames from the phishing whitelist
Mar 14 13:02:08 server MailScanner[31651]: Read 5414 hostnames from the phishing blacklists
Mar 14 13:02:09 server MailScanner[31651]: Using SpamAssassin results cache
Mar 14 13:02:09 server MailScanner[31651]: Connected to SpamAssassin cache database
Mar 14 13:02:11 server MailScanner[31651]: Connected to Processing Attempts Database
Mar 14 13:02:11 server MailScanner[31651]: Found 3 messages in the Processing Attempts Database
Mar 14 13:02:11 server MailScanner[31651]: Using locktype = posix
[No Further Activity]
************************
On March 4, WHM upgraded to 11.36.0.11, but I don't see anything in the changelog that might apply, but that may just be me.
I am not using MailScanner front end.


When I start the service, the above maillog block of entries occurs 3 times as each instance initializes, but nothing further occurs.

I'm wondering whether something is the Processing Attempts Database is causing things to stall out, but I haven't any idea how to work with that. Some advice in that regard would be helpful.

Thanks for any advice.

Roger Ide

[misteride]

MailScanner is running properly now, after I upgraded and chased down a couple of settings in WHM, which I either caused while sleep-computing or for another reason. Upgrading is a seriously compassionate process. No pain. All gain.

[screege]

Could you please tell us which settings you modified in WHM?

Regards