Problems after upgrade from 4.85 to 5.03

[Thom van der Boon]

Mark, 

I think I had the same problem in the past. Try following: 

Stop MailScanner 

Open two console windows. In console window one start "top" (the program you can use to monitor various system values) 

Start mailscanner in your second window 

I think you will see the following: 

Under CPU: 
%id(le) goes to zero 
%wa(it) is going nuts 

Swap memory is being filled up rapidly. 

If that is the case: Most easy solution: Expand your RAM. 

I noted that a virtual machine with 2 GB with two MailScanner childs gives this behaviour. After moving to a server with 4 GB RAM all problems went away. 

Met vriendelijke groet, Best regards, 


Thom van der Boon 
E-Mail: thom at vdb.nl 



===== 



Thom.H. van der Boon b.v. 
Transito 4 
6909 DA Babberich 
Tel.: +31 (0)88 4272727 
Fax: +31 (0)88 4272789 
Home Page: http://www.vdb.nl/ 


Van: "Mark Sapiro" <mark at msapiro.net> 
Aan: mailscanner at lists.mailscanner.info 
Verzonden: Dinsdag 11 oktober 2016 18:30:09 
Onderwerp: Re: Problems after upgrade from 4.85 to 5.03 

On 10/11/2016 01:12 AM, Daniel Malmgren wrote: 

> Now it seems though that MailScanner 
> processes the same messages again and again, like it's stuck in a loop, 
> see log snippet below. The messages seem to stay in postfix's hold queue. 


Messages staying in the Postfix hold queue is a side effect of the problem. 

The issue you see in the log messages is a MailScanner child starts and 
attempts to process the 2 messages in the Processing Attempts Database. 
The first of these (9CC2E45321.A7F02) causes the child to die before it 
does anything else including processing the Postfix hold queue. 


See OP at 
<http://lists.mailscanner.info/pipermail/mailscanner/2016-October/103861.html> 
for log messages. 


> Since I don't get any errors I don't really where to continue looking. 
> Anyone see anything obvious? 

I don't know why you aren't seeing some kind of error message in some 
log, but you could try stopping MailScanner and then running 

sudo MailScanner --processing 

or 

sudo MailScanner --processing=0 

That probably won't say much. Then move 
/var/spool/MailScanner/incoming/Processing.db aside and start 
MailScanner and see if that helps. 

-- 
Mark Sapiro <mark at msapiro.net> The highway is for gamblers, 
San Francisco Bay Area, California better use your sense - B. Dylan 


-- 
MailScanner mailing list 
mailscanner at lists.mailscanner.info 
http://lists.mailscanner.info/mailman/listinfo/mailscanner 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mailscanner.info/pipermail/mailscanner/attachments/20161011/5155ca55/attachment.html>