Problem Messages

[Glenn Steen]

2009/6/16 Remco Barendse <mailscanner at barendse.to>:
> On Mon, 15 Jun 2009, Julian Field wrote:
>
>>
>>
>> On 15/06/2009 11:17, Remco Barendse wrote:
>>>
>>>  On Mon, 15 Jun 2009, Julian Field wrote:
>>>
>>> >  That's quite normal, it processed the message successfully (apart from
>>> > >  you needing to update your copy of ClamAV). So whatever was causing your
>>> > >  message to kill MailScanner has gone away and isn't doing it now.
>>>
>>>  Strange, another problem meBssage appeared over the weekend, i ran it
>>>  through MailScanner in the same way and also this message processed
>>> well.
>>>
>>>  I'm a bit puzzled why these "Problem Messages"  messages keep appearing
>>>  but at the same time the message gets quarantined and moved to the
>>>  quarantine properly. Is there maybe some bug in the thingy that controls
>>>  Processing.db ? I get a new mail message reporting the same problem
>>> every
>>>  hour or so, until i nuke Processing.db
>>>
>>>  Is there any way to increase the log level of "Problem Messages" to get
>>>  some more info from that?  (If these messages come up very rarely
>>> anyways,
>>>  why not be more verbose)
>>
>> What more info would you like? As all I know is that the message caused
>> MailScanner to crash somehow, there's almost no information to give you,
>> sorry.
>
> OK, i hoped it was possible to include some information on specifically what
> caused the crash.
>
> Strange, i have never seen this behaviour on any server running MailScanner,
> just the server that was newly installed. Maybe i did something wrong or
> some of the perl packages did not compile properly.
>
>> I should add some code to remove the problem message from the
>> Processing.db when it gets quarantined though.
>
> Would be neat :)
>
> Thanks!
> Remco
>
Don't rule out HW... If it is set up exactly the same way and has
problems, everything else being equal, RAM (or even a bad CPU) might
be "it".
Which would explain the somewhat erratic occurences.
Anyway, the processing DB, IMO, is there to help your system survive
the problem gracefully, while still alerting you that there is some
type of problem you need look further into... The rest is up top you
... Yeah, I know... We're all getting a bit too used to Jules solving
all the problems of the world (of MilScanner:), so that we tend to get
a bit ... lazy:-):-)

Cheers
-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se