Thanks Steffen for the valuable knowledge. Need to know futher that, how could this lead to mails to get re-downloaded. ??
Regards, Kavish Karkera ________________________________ From: Steffen Kaiser <skdove...@smail.inf.fh-brs.de> To: Kavish Karkera <kavish.kark...@yahoo.com> Cc: "dovecot@dovecot.org" <dovecot@dovecot.org> Sent: Thursday, 25 July 2013 5:54 PM Subject: Re: [Dovecot] Duplicate Mails downloding issue -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 25 Jul 2013, Kavish Karkera wrote: > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > Jul 23 15:34:51 popserver dovecot: pop3(14949_kavish): Warning: Locking > transaction log file > /indexes//mail/v3store/example.com/14949_kavish/.INBOX/dovecot.index.log took > 133 seconds some process keeps the INBOX locked, but does not touch the file, so it looks like a stale lock. > Jul 23 15:34:51 popserver dovecot: pop3(kav...@example.com): Error: Broken > file /indexes//mail/v3store/example.com/14949_kavish/.INBOX/dovecot-uidlist > line 180: UIDs not ordered (10156 >= 10156) Therefore some other process had broken the lock and had appended a message. > Jul 23 15:35:01 popserver dovecot: pop3(kav...@example.com): Error: > utime(/indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock) > failed: No such file or directory > > Jul 23 15:35:11 popserver dovecot: pop3(kav...@example.com): Error: > utime(/indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock) > failed: No such file or directory then the former process(es) finish and try to clean up, but the "some other process" already deleted the lock file. > Jul 23 15:35:21 popserver dovecot: pop3(kav...@example.com): Warning: Our > dotlock file > /indexes//mail/v3store/example.com/kavish/.INBOX/dovecot-uidlist.lock was > deleted (kept it 30 secs) > --------------------------------------------------------------------------------------------------------------------------------------------------------- So you have to check your system why a process, that as locked INBOX, is stalled for more than 120min. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUfEY6F3r2wJMiz2NAQICHwf9HJG66UAHGJp1nT8Ql31n1Bk1KWb+wAhA p2nReYZVSbzZOJM84Dkw8xLu3WoHzFxFEIS+CJc7xGtaeWGrwrTik6d7LKjwI9gf HCun1rq9VzfS85sHvn1owVJxMnUrA3YcY90aQZ6SWHNwvrdmmqqIPhQdGx7xc3En N1jJ0wPEd9hbJyi+2MScZt0WxKuRR+Wpkl14gO6ZPcX95uONGzLcSTs071rAXT+c 6RWLxn2jhruk4qUIm+PGnHkwXTnKL2Dqfladj4/ybxTRn2hgNldK8w4piUwwPWIn HW/hN+sDM/hlRtyu0zHVfiFC7MES6s0JonzwDlOKAFt9dUUG4Mcr9Q== =mar+ -----END PGP SIGNATURE-----
