Hi, I'm using version 0.99.10.8 on debian 2.4.26 and am getting this problem, can someone please shed some light over this? Aug 31 13:58:58 xxx imap(someone): file_wait_lock() failed with modify log file /var/mail/someone_new/Maildir/.INBOX/.imap.index.log: Resource temporarily unavailable and then: Aug 31 14:00:58 xxx imap(someone): Couldn't lock modify log file /var/mail/someone_new/Maildir/.INBOX/.imap.index.log and finally: Aug 31 14:26:35 xxx imap(someone): Corrupted modify log file /var/mail/someone_new/Maildir/.INBOX/.imap.index.log: used_file_size larger than real file size (4096 vs 2576) MTA is qmail 1.03 (with procmail v3.22) TIA, Fredrick -- Systemadministration EsPresto AG ----------------------------------------------------------------- backman at espresto.com Breite Str. 30-31 Tel/Fax: +49.30.90 226.750/.760 10178 Berlin/Germany
On 31.8.2004, at 16:20, Fredrick Backman wrote:> Hi, I'm using version 0.99.10.8 on debian 2.4.26 and am getting this > problem, can someone please shed some light over this? > > Aug 31 13:58:58 xxx imap(someone): file_wait_lock() failed with modify > log file /var/mail/someone_new/Maildir/.INBOX/.imap.index.log: > Resource temporarily unavailable > > and then: > > Aug 31 14:00:58 xxx imap(someone): Couldn't lock modify log file > /var/mail/someone_new/Maildir/.INBOX/.imap.index.logMeans that someone else had been keeping the lock for a long time. Do you use multiple clients? Although that shouldn't really be a problem either unless one client is downloading mails for a long time and another client tries to access the mailbox.> and finally: > > Aug 31 14:26:35 xxx imap(someone): Corrupted modify log file > /var/mail/someone_new/Maildir/.INBOX/.imap.index.log: used_file_size > larger than real file size (4096 vs 2576)Well, that isn't very good. Anyway, 1.0-tests have all of this code rewritten. I don't want to spend much time wondering about 0.99 indexing bugs. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20040902/7fcdbd70/attachment-0001.bin>
Timo Sirainen wrote:> On 31.8.2004, at 16:20, Fredrick Backman wrote: > >> Hi, I'm using version 0.99.10.8 on debian 2.4.26 and am getting this >> problem, can someone please shed some light over this? >> >> Aug 31 13:58:58 xxx imap(someone): file_wait_lock() failed with modify >> log file /var/mail/someone_new/Maildir/.INBOX/.imap.index.log: >> Resource temporarily unavailable >> >> and then: >> >> Aug 31 14:00:58 xxx imap(someone): Couldn't lock modify log file >> /var/mail/someone_new/Maildir/.INBOX/.imap.index.log > > > Means that someone else had been keeping the lock for a long time. Do > you use multiple clients? Although that shouldn't really be a problem > either unless one client is downloading mails for a long time and > another client tries to access the mailbox.Yes, it turned out that this guy is checking his mails from two locations simultaneously.>> and finally: >> >> Aug 31 14:26:35 xxx imap(someone): Corrupted modify log file >> /var/mail/someone_new/Maildir/.INBOX/.imap.index.log: used_file_size >> larger than real file size (4096 vs 2576) > > > Well, that isn't very good. > > Anyway, 1.0-tests have all of this code rewritten. I don't want to spend > much time wondering about 0.99 indexing bugs.I will update our dovecot soon, so I'll just ignore these problems until then. Kiitos :) -- Systemadministration EsPresto AG ----------------------------------------------------------------- backman at espresto.com Breite Str. 30-31 Tel/Fax: +49.30.90 226.750/.760 10178 Berlin/Germany