On Tue, 2008-09-09 at 20:20 +0200, Cor Bosman wrote:
Now im seeing these:
Sep 9 19:28:25 userimap3 dovecot: IMAP(xxxxx): file_dotlock_create() failed with index cache file /var/spool/mail/dovecot-control/indexes/u/ul/xxxxx/.Collega Coaching/dovecot.index.cache: Resource temporarily unavailable
Is that any better?
Yes, although the error message could be changed to "locking timed out". But at least now the error shouldn't be visible to clients (other than small slowdowns due to the 2 second lock wait).
Anyway, the real problem is one of:
a) Dovecot is really locking dovecot.index.cache file for a long time for some reason and other processes are timing out because of it.
b) Some process is crashing and leaving stale dovecot.index.cache.lock files lying around. But that'd have to be a .lock from another server, because on the same server Dovecot checks to see if the PID exists and if not it'll just override the lock immediately.
c) NFS caching problems: the .lock file was deleted by server1 but server2 didn't see that, so it keeps assuming that the file exists long after it was really gone.