Hy!
On 04-Sep-2001 Scott Adkins wrote:
>> 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.
>
> We stopped the server and nuked the delivery files altogether. This only
> worked for 2 days, however, and now we are back to where we were. We see
> a constant stream of duplicate delivery database errors...
I know the following isn't a really nice solution, but if you need to
"stabilize" your system fast, you could disable the code that does duplicate
delivery checking. I remember it's in one C file, and it's fairly easy to do
(just delete or comment out a few dozen lines). Maybe there's even a config
option for this now?
I repeat, this isn't good for two reasons:
- the bug won't be tracked down this way (but bug-hunting shouldn't really be
done on production systems anyway)
- the duplicate delivery-check feature will be absent of the server
(I think you can live with this.)
So is this elegant? No! But it _will_ work...
| Noll Janos <[EMAIL PROTECTED]> | http://www.johnzero.hu |
| "Expect the unexpected!" | ICQ# 4547866 | Linux rulez! |
