Aborting locker errors...
robm at fastmail.fm
Wed Dec 18 00:32:31 EST 2002
> This should be due to internal deadlocks in the berkeley db code. (This
> happen when two different processes are trying to upgrade read locks to
> write locks or split a page.) Generally the bigger the database is the
> likely this is to happen, which is why you might see it only on your less
> loaded server.
> It's one of those "if it isn't happening constantly, it isn't a problem"
Given that it's for the deliver.db, which is used for duplicate delivery
suppression and sieve, will an aborted locker result in sieve not correctly
processing an email?
More information about the Info-cyrus