Hi, > On 15. Jul 2019, at 10:59, Timo Sirainen <[email protected]> wrote: > > On 15 Jul 2019, at 10.58, Paul Hecker via dovecot <[email protected]> wrote: >> >> Hi, >> >> since upgrading to Dovecot 2.3.7 I get the following new errors: > > What was the old version? Did you upgrade your kernel as well?
It was 2.3.6. But you are true, this seems to be an issue related to AppArmor (in complain mode) that I enabled a day earlier. Have to investigate why AppArmor is given me this?! Sorry for the noise... > >> 2019-07-15 09:10:52 mail dovecot: >> imap([email protected])<32484><goWh8rKNSNZfqJ9R>: Error: file_lock_free(): >> Unexpectedly failed to retry locking >> /var/spool/mail/iwascoding/paul/mdbox/mailboxes/INBOX/dbox-Mails/dovecot-vsize.lock: >> >> fcntl(/var/spool/mail/iwascoding/paul/mdbox/mailboxes/INBOX/dbox-Mails/dovecot-vsize.lock, >> write-lock, F_SETLK) locking failed: No such file or directory > > What filesystem are you using for mdboxes? > > The lock fd is already open. Locking is not supposed to fail this way. Also I > can't think of any recent changes that could be related to this. v2.2.36 > already had the same locking code. >
smime.p7s
Description: S/MIME cryptographic signature
