Found nn messages in the processing-messages database

[Julian Field]

Please also try MailScanner 4.76.15 and let me know how you get on. I 
have neatened up the code quite a bit.

Jules.

On 21/4/09 18:04, Julian Field wrote:
> In /usr/lib/MailScanner/MailScanner/Message.pm, around line 1243, you 
> will find a line that says
> next if $message->{abandoned};
> Please try commenting out that line by putting a '#' at the start of it.
>
> Then restart MailScanner, and let me know if that solves the problem.
>
> Thanks for your patience in helping me resolve this issue!
>
> Jules.
>
> On 21/4/09 16:45, Mark Sapiro wrote:
>> On Mon, Apr 20, 2009 at 07:41:34PM -0700, Mark Sapiro wrote:
>>> Julian Field wrote:
>>>
>>>> Also, please try the latest beta 4.76.14. This may help with this
>>>> problem. I have worked out why it would end up with messages in there
>>>> when it shouldn't, but I can't see where it actually does it. It
>>>> shouldn't be able to happen. So I have added some more clauses to 
>>>> cause
>>>> it to ignore partially-delivered messages, which are what must be
>>>> causing the problem.
>>>
>>> OK. I have installed 4.76.14 and I removed the Processing.db file and
>>> let MailScanner recreate it when I restarted following the 4.76.14
>>> installation.
>>>
>>> I will report what I see after it runs for a while.
>>
>> There is essentially no change in what I'm seeing. I have attached
>> MailScanner_log.txt which is the result of grepping the maillog for
>> MailScanner and then keeping only those records beginning with the
>> restart following installation of 4.76.17 through the child dying
>> of old age and the new child finding 4 messages in the database.
>>
>> Also, here are the results of asking MailScanner to display the
>> database and inspecting it with sqlite.
>>
>> [root at sbh16 ~]# MailScanner --processing=0
>> Currently being processed:
>>
>> Number of messages: 6
>> Tries   Message Next Try At
>> =====   ======= ===========
>> 1       45449690408.056E4       Tue Apr 21 03:36:12 2009
>> 1       41105690407.04696       Tue Apr 21 03:35:27 2009
>> 1       18870690467.09282       Mon Apr 20 20:59:01 2009
>> 1       60362690438.064E1       Mon Apr 20 20:56:06 2009
>> 1       10663690435.057E8       Mon Apr 20 20:47:51 2009
>> 1       48118690444.05809       Mon Apr 20 20:46:20 2009
>> [root at sbh16 ~]# MailScanner --processing=1
>> [root at sbh16 ~]# sqlite3 /var/spool/MailScanner/incoming/Processing.db
>> SQLite version 3.3.6
>> Enter ".help" for instructions
>> sqlite>  .tables
>> archive     processing
>> sqlite>  select * from archive;
>> sqlite>  select * from processing;
>> 10663690435.057E8|1|1240285671
>> 48118690444.05809|1|1240285580
>> 60362690438.064E1|1|1240286166
>> 18870690467.09282|1|1240286341
>> 45449690408.056E4|1|1240310172
>> 41105690407.04696|1|1240310127
>> sqlite>  .exit
>> [root at sbh16 ~]#
>>
>>
>> Also, it is curious and possibly significant that all the queue ids
>> remaining in the database are all-decimal when in general, most are not.
>>
>
> Jules
>

Jules

-- 
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

MailScanner customisation, or any advanced system administration help?
Contact me at Jules at Jules.FM

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
PGP public key: http://www.jules.fm/julesfm.asc


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.