Date: Mon, 27 Aug 2001 09:38:26 -0400
From: Scott Adkins <[EMAIL PROTECTED]>
[ ... many duplicate deliverdb errors deleted ... ]
[ And so on, and so forth... hitting all the delivery databases ]
[ there is a mixture of duplicate_check and duplicate-mark entries also ]
You definitely need to run recovery on your duplicate delivery
database. I might just delete the database entirely; since the
duplicate delivery database isn't transactional, it can't guarantee
consistency, and there's no critical database in it.
To run recover, you must kill at lmtpd's (and any other processes that
might have the database open) and run ctl_deliver -r. Just stopping
(and waiting) and starting the master process should do this.
We now get the DBERROR stuff all the time, and I don't believe the duplicate
delivery database is doing anything at all now. It doesn't seem to be
affecting email delivery any, so my guess is that the LMTP daemon will first
check to see if a message is in the database and if it can't connect to the
database, it just doesn't use it and delivers the email normally. Is that
correct?
I believe this is true.
Any idea what would have caused these errors to begin with?
Possibly a system crash or a process crash/being killed at just the
wrong time, due to the lack of transactions.
Larry
