search for: dotlock

I have to make dotlock work because this openwebmail thing only supports one of dotlock or flock, but procmail delivery does dotlock and fcntl. procmail correctly creates a dotlock file in /var/spool/mail/username.lock when delivering, I can watch this with `while :; do ls -la | grep lock; done`. It works fine when loc...

Hello, I'd like to make sure my understanding of the mbox locking strategy is correct : - "mbox_dotlock_change_timeout" directive : a process seeing that an already locked (by another process) mbox he want to access hasn't change for this amount of time, allows himself to override the lock ? If it's using fcntl, is it only possible to override ? - when a process abort...

As of late our four node dovecot 1.2.13 cluster has been experiencing a massive number of these dotlock errors: Created dotlock file's timestamp is different than current time (1295480202 vs 1295479784): /mail/user/Maildir/dovecot-uidlist These dotlock errors correspond with very high load averages, and eventually we have to turn off all but one server to stop them from occurring. We first ass...

...le system (gluster) and my indexes are stored on the local drive. I have a few issues: - My users mailboxes have issues where messages will be mixed up (you go to open a message and it gets a different message) - messages will dissappear - unable to open or delete messages - errors in log about dotlocks being overwritten Here is some of the log entries: Our dotlock file /mail/mydomain.com/webmaster/dovecot-uidlist.lock was overridden (kept it 0 secs) utime(/mail/mydomain.com/webmaster/dovecot-uidlist.lock) failed: No such file or directory Transaction log file /mailindex/mydomain.com/webmast...

Hello, Running dovecot 1.1.6 on centOS 5 and RHEL 5. With the settings: pop3_lock_session = yes mail_privileged_group = mail mail_location = mbox:~/:INBOX=/var/spool/mail/%u mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl and /var/spool/mail permissions: drwxrwx--x 2 root mail 4096 Nov 19 10:16 mail/ Trying to connect via POP3 results in this error: --- Nov 19 09:31:01 lexiconn2 dovecot: child 32127 (pop3) killed with signal 11 Nov 19 09:31:01 lexiconn2 dovecot: POP3(cerberus): file_lock_dotlock()...

Hello, is dotlock supposed to work with NFS? I noticed that the default-locking method causes problems even with nfslockd started. Regards Marten

If I read the code correctly, only dotlocks are supported for locking of dovecot-uidlist. And I don't see any settings in the config file for it. As it turns out, dotlocks are very slow on my system, due to their implementation via hardlinks. Would it be possible to support other locking mechanisms for locking of the uidlist f...

...ized out>, timeout_secs=timeout_secs at entry=60, > lock_r=lock_r at entry=0x7fff04501118) at file-lock.c:303 > error = 0x564540376490 "" > ret = <optimized out> > #3 0x00007f768a976c87 in squat_trie_lock (trie=0x564540376490, lock_type=0, file_lock_r=0x7fff04501118, dotlock_r=0x7fff04501120) at squat-trie.c:294 > ret = <optimized out> > dotlock_r = 0x7fff04501120 > file_lock_r = 0x7fff04501118 > trie = 0x564540376490 > ret = <optimized out> > __func__ = "squat_trie_lock" > lock_type = 0 > ret = <optimized out> > _...

...ized out>, timeout_secs=timeout_secs at entry=60, > lock_r=lock_r at entry=0x7fff04501118) at file-lock.c:303 > error = 0x564540376490 "" > ret = <optimized out> > #3 0x00007f768a976c87 in squat_trie_lock (trie=0x564540376490, lock_type=0, file_lock_r=0x7fff04501118, dotlock_r=0x7fff04501120) at squat-trie.c:294 > ret = <optimized out> > dotlock_r = 0x7fff04501120 > file_lock_r = 0x7fff04501118 > trie = 0x564540376490 > ret = <optimized out> > __func__ = "squat_trie_lock" > lock_type = 0 > ret = <optimized out> > _...

...at entry=60, > > > lock_r=lock_r at entry=0x7fff04501118) at file-lock.c:303 > > > error = 0x564540376490 "" > > > ret = <optimized out> > > > #3 0x00007f768a976c87 in squat_trie_lock (trie=0x564540376490, lock_type=0, file_lock_r=0x7fff04501118, dotlock_r=0x7fff04501120) at squat-trie.c:294 > > > ret = <optimized out> > > > dotlock_r = 0x7fff04501120 > > > file_lock_r = 0x7fff04501118 > > > trie = 0x564540376490 > > > ret = <optimized out> > > > __func__ = "squat_trie_lock&quot...

...can lock the INBOX. > > > > > imap should be the only one that needs to be setgid mail. > > Actually, I've looked at the dovecot source code. There is no way having > setgid on the executable will work. The source drops the privledges long > before it tries to do a dotlock. > > This is an upstream problem. > > For now, I've disable dotlock, and use fcntl instead, as that is what exim > uses anyways. Is dotlocking still a work in progress or are we missing something here? -- Jaldhar H. Vyas <jaldhar at debian.org> La Salle Debain - http://...

...cut over to a new mail server running Dovecot 1.0.5. The underlying OS is RHEL 5. User mailboxes are stored in Unix mbox format on a local ext3 file system. The MTA on the system is the default RedHat version of Sendmail 8.13.8 with procmail for local delivery. We're using a combination of dotlock and fcntl style locking. The output of "dovecot -n" for this system appears below my signature. Periodically we see errors like the following in our logs: Oct 21 19:36:01 postoffice1 dovecot: POP3(someuser): file mbox-sync.c: line 1433 (mbox_sync_handle_eof_updates): assertion failed: (...

I've recently upgraded to 1.0.10 in hopes that this problem would go away but no luck. I've got some users at my company with large inboxes on maildir (say 22,000 messages). Their mailboxes are hosted on nfs and dovecot is configured to do dotlocking. Still I see messages like this continually in the logs (sometimes every hour or so): server dovecot: IMAP(user): dotlock /home/user/Maildir/dovecot.index.log.lock was immediately recreated under us server dovecot: IMAP(user): file_dotlock_create() failed with file /home/user/Maildir/dovecot.i...

I am using dovecot 1.0.rc15 (a similar problem occurred in rc10) on Solaris 9 (sparc). When working with a user who's home dir is on a local disk everything seems fine. But when that home is on an NFS-mounted disk things are very badly awry. Both the indices and the subscriptions file are being destroyed and what is left behind are files with names of the form .nfs72C034 etc. These files are

...t_secs=timeout_secs at entry=60, > > lock_r=lock_r at entry=0x7fff04501118) at file-lock.c:303 > > error = 0x564540376490 "" > > ret = <optimized out> > > #3 0x00007f768a976c87 in squat_trie_lock (trie=0x564540376490, lock_type=0, file_lock_r=0x7fff04501118, dotlock_r=0x7fff04501120) at squat-trie.c:294 > > ret = <optimized out> > > dotlock_r = 0x7fff04501120 > > file_lock_r = 0x7fff04501118 > > trie = 0x564540376490 > > ret = <optimized out> > > __func__ = "squat_trie_lock" > > lock_type = 0 >...

...t_secs=timeout_secs at entry=60, > > lock_r=lock_r at entry=0x7fff04501118) at file-lock.c:303 > > error = 0x564540376490 "" > > ret = <optimized out> > > #3 0x00007f768a976c87 in squat_trie_lock (trie=0x564540376490, lock_type=0, file_lock_r=0x7fff04501118, dotlock_r=0x7fff04501120) at squat-trie.c:294 > > ret = <optimized out> > > dotlock_r = 0x7fff04501120 > > file_lock_r = 0x7fff04501118 > > trie = 0x564540376490 > > ret = <optimized out> > > __func__ = "squat_trie_lock" > > lock_type = 0 >...

...and recover. Something I need to reboot the nfs server to recover. Let me give a run down of the particulars: All the mail is in mbox format. everybody runs linux with kernel 2.6.24.2 (any known nfs locking issues there?). delivery is done via procmail, its locking and dovecot's are both dotlock, fcntl. The nfs mount options are actimeo=3,hard,noatime,rsize=32768,wsize=32768,nfsvers=3 The clocks are in sync. Dovecot.conf: protocols = imap imaps pop3 pop3s login_greeting = imap ready. mail_location = mbox:~/:INBOX=/var/mail/%u mmap_disable = yes mail_nfs_storage = yes mail_nfs_index = yes...

Folks - Some time ago as I migrated to dovecot 1.0, I ran into all sorts of problems with file locks, and I tried various solutions. Apparently, in the process, I got a bit careless and removed all my dovecot-uidlist files. They're gone. My understanding, however, is that they should come back, but this doesn't happen. I've been forced to run with index=MEMORY in 1.0 for

...ized out>, timeout_secs=timeout_secs at entry=60, > lock_r=lock_r at entry=0x7fff04501118) at file-lock.c:303 > error = 0x564540376490 "" > ret = <optimized out> > #3 0x00007f768a976c87 in squat_trie_lock (trie=0x564540376490, lock_type=0, file_lock_r=0x7fff04501118, dotlock_r=0x7fff04501120) at squat-trie.c:294 > ret = <optimized out> > dotlock_r = 0x7fff04501120 > file_lock_r = 0x7fff04501118 > trie = 0x564540376490 > ret = <optimized out> > __func__ = "squat_trie_lock" > lock_type = 0 > ret = <optimized out> > _...

...lboxes and control files are all on NFS) and I'm using procmail instead of deliver as the LDA. 1. Documentation says : "Dovecot locks the maildir while doing modifications to it or while looking for new messages in it" and then mention the "dovecot-uidlist.lock" dotlock file. a) if that file fcntl'ed in addition (i.e. dotlocked + fcntled or just dotlocked) ? b) is that file THE way to lock the Maildir mentionned above or is it just something else used only for updating that particular file (i.e. is Maildir locked in some way + dov...