Re: [exim] Bug#360696: Bug#360696: Failed to get write lock …

Top Page
Delete this message
Reply to this message
Author: Philip Hazel
Date:  
To: Michel Meyers
CC: exim-users, 360696-quiet, Andreas Metzler
Subject: Re: [exim] Bug#360696: Bug#360696: Failed to get write lock for /var/spool/exim4/db/retry.lockfile:timedout
On Fri, 28 Apr 2006, Michel Meyers wrote:

> So there you have it: deleting one silly little file fixed my months old
> issue (if only I had tried that before!).


If only I'd thought to suggest it before! We have had crashes in the
past, but not, I think, CPU loops. There are two possible causes:

(1) The retry data file was somehow corrupted, and this caused something
in the db library to go loopy.

(2) The version of Berkeley DB you are using was updated and the data
file that was created by the previous version was not compatible - BDB
does have a habit of changing things - again provoking a loop.

I would argue that there is a bug in BDB in that it shouldn't loop,
whatever data file you throw at it.

Anyway, I'm glad this is sorted without my having to do anything.

-- 
Philip Hazel            University of Cambridge Computing Service
Get the Exim 4 book:    http://www.uit.co.uk/exim-book