Hi there, I'm getting a lot of this message in production log: Created dotlock file's timestamp is different than current time (1232468644 vs 1232468524): /path/to/dovecot.index.log The IT guy swears the clocks are sincronized. Whe even have made a test in the machine running dovecot, inside the user's mailbox: # > foo; ls -l --time-style=full-iso foo; date -rw-r--r-- 1 root root 0 2009-01-19 17:40:55.000850000 +0000 foo Mon Jan 19 17:40:55 UTC 2009 The timestamps seems to match. I'm using dovecot 1.1.6 over NFS. Any thoughts? Thanks in advance, gpg
On Tue, 2009-01-20 at 14:36 -0200, Giorgenes Gelatti wrote:> Created dotlock file's timestamp is different than current time (1232468644 > vs 1232468524): /path/to/dovecot.index.log > > The IT guy swears the clocks are sincronized.the difference in the above message is exactly 120 seconds. Are they all 120 seconds?> I'm using dovecot 1.1.6 over NFS. > Any thoughts?What OS are you using on the NFS clients? Perhaps this is a caching issue, have you tried changing/disabling attribute cache timeouts? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20090120/0d59a6b6/attachment-0002.bin>
Dovecot is running on a linux machine (2.6 kernel). The nfs was mounted as: nfs rw,vers=3,proto=tcp,intr,nolock,noexec,rsize=8192,wsize=8192 0 0 After your hint we added the "noac" flag: nfs rw,vers=3,proto=tcp,intr,nolock,noexec,noac,rsize=8192,wsize=8192 0 0 But the error continues with differences of 120 and 60 seconds. Thanks for the reply, gpg 2009/1/20 Timo Sirainen <tss at iki.fi>> On Tue, 2009-01-20 at 14:36 -0200, Giorgenes Gelatti wrote: > > Created dotlock file's timestamp is different than current time > (1232468644 > > vs 1232468524): /path/to/dovecot.index.log > > > > The IT guy swears the clocks are sincronized. > > the difference in the above message is exactly 120 seconds. Are they all > 120 seconds? > > > I'm using dovecot 1.1.6 over NFS. > > Any thoughts? > > What OS are you using on the NFS clients? Perhaps this is a caching > issue, have you tried changing/disabling attribute cache timeouts? >