[Dovecot] Mailbox is locked?
Hello,
I recently upgraded from Dovecot 1.1.8 to 1.1.14, and I've started to get errors I never got before. Specifically, I'm getting "Mailbox is locked, will abort in xx seconds" errors. My mail client (mutt) will just sit there in the background (presumably in IDLE) and randomly will show this error (I THINK it has something to do with delivering new messages to the folder; I use the dovecot LDA).
Nothing else about my configuration has changed, just the version of dovecot. Does anyone know what could be causing these? I assume it has something to do with the index files, but... Nothing interesting shows up in the log files. How do I get rid of these error messages? Or even begin tracking them down?
For what it's worth, mail is stored on the server in Maildirs, and the lock_method is fcntl, the mbox_write_locks is fcntl (I don't set mbox_read_locks).
~Kyle
For to accuse, requires less eloquence, such is man's nature, than to excuse; and condemnation, than absolution more resembles justice. -- Hobbes, Leviathan
On Apr 23, 2009, at 12:53 AM, Kyle Wheeler wrote:
I recently upgraded from Dovecot 1.1.8 to 1.1.14, and I've started
to get errors I never got before. Specifically, I'm getting "Mailbox
is locked, will abort in xx seconds" errors. My mail client (mutt)
will just sit there in the background (presumably in IDLE) and
randomly will show this error (I THINK it has something to do with
delivering new messages to the folder; I use the dovecot LDA).Nothing else about my configuration has changed, just the version of
dovecot. Does anyone know what could be causing these? I assume it
has something to do with the index files, but... Nothing interesting
shows up in the log files. How do I get rid of these error messages?
Or even begin tracking them down?
Do you actually notice something being broken/hanging or is it just
that it gives those messages? Do the xx seconds ever reach below 119?
I added those notifications only recently and I guess it's possible
that sometimes it gives them way too early (and actually I remember
seeing one myself once). Hmm. Yeah, looks like the code doesn't really
even try to prevent that. I'll add some check to make it hide them
until at least 15 seconds has passed.
On Thursday, April 23 at 01:18 AM, quoth Timo Sirainen:
Do you actually notice something being broken/hanging or is it just that it gives those messages?
Nope - Dovecot's behavior is otherwise exemplary.
Do the xx seconds ever reach below 119?
I haven't been keeping track, but I generally only see them once at a time, with relatively high timeout values.
I added those notifications only recently and I guess it's possible that sometimes it gives them way too early (and actually I remember seeing one myself once). Hmm. Yeah, looks like the code doesn't really even try to prevent that. I'll add some check to make it hide them until at least 15 seconds has passed.
Cool!
~Kyle
If Jack Valenti had been around at the time of Gutenberg he would have organized the monks to come and burn down the printing press. -- ITAA president Harris Miller
participants (2)
-
Kyle Wheeler
-
Timo Sirainen