Re: [Dovecot] Lock file issues
On Sun, 2007-04-08 at 12:06 +0300, Timo Sirainen wrote: > On 3.4.2007, at 21.05, Paul Hamby wrote: > > > We are running 1.0.rc28 on three servers with 3 Horde/IMP boxes > > talking > > to Dovecot. The user's home dirs are located on an NFS server > > and the indexes are stored in their Maildirs. I have mmap_disable=yes > > and lock_method=dotlock in dovecot.conf. We have not implemented > > anything to direct users to the same server as is recommended per the > > Wiki. I have been trying to avoid this, as the best way I could see to > > do > > it would be to put in an IMAP proxy (Perdition?) and I just wanted to > > keep it as simple as possible if I could. > > And I guess you didn't disable attribute cache either? I was concerned about the performance hit it would take doing this. I will set actimeo=0 on the nfs mounts and monitor the logs for errors to see if this helps while not killing performance. > > > The problems we have been having are due to dovecot.*.lock files not > > being cleaned up. This issue presents itself as a user not being > > able to > > login via the webmail interface. The logfile will contain something > > similar to the following: > .. > > Apr 3 08:37:51 app02 dovecot: IMAP(user): Corrupted transaction log > > file /mail_home3/j/ji/user/Maildir/dovecot.index.log: end_offset > > (23440) > >> current sync_offset (23368) > > Apr 3 08:37:51 app02 dovecot: IMAP(user): file > > mail-index-sync-update.c: line 40 (mail_index_sync_update_log_offset): > > assertion failed: (prev_offset >= map->hdr.log_file_int_offset || > > prev_seq > map->hdr.log_file_seq) > > Hmm. I guess I should change this assert to instead just log an error > and return failure, because it's what leaves the lock files lying > around. > Will this change be in an upcoming RC? > But anyway I don't think it's a good idea to keep using this kind of > a configuration where things break all the time.. Understood, there are just some added complexities to consider in the IMAP proxy scenario, such as the changes needed for adding, editing and deleting user accounts and the necessary changes to our LDAP config. It is something I will have to give more thought/time to. Thanks for your reply. Paul
Re: [Dovecot] Lock file issues
On Mon, 2007-04-09 at 20:55 +0300, Timo Sirainen wrote: > On Mon, 2007-04-09 at 11:30 -0500, Paul Hamby wrote: > > > > Apr 3 08:37:51 app02 dovecot: IMAP(user): file > > > > mail-index-sync-update.c: line 40 (mail_index_sync_update_log_offset): > > > > assertion failed: (prev_offset >= map->hdr.log_file_int_offset || > > > > prev_seq > map->hdr.log_file_seq) > > > > > > Hmm. I guess I should change this assert to instead just log an error > > > and return failure, because it's what leaves the lock files lying > > > around. > > > > > > > Will this change be in an upcoming RC? > > I think I'll leave this unfixed for v1.0 and fix it one way or another > with v1.1. Fair enough. > > > > But anyway I don't think it's a good idea to keep using this kind of > > > a configuration where things break all the time.. > > > > Understood, there are just some added complexities to consider in the > > IMAP proxy scenario, such as the changes needed for adding, editing and > > deleting user accounts and the necessary changes to our LDAP config. It > > is something I will have to give more thought/time to. > > What about your load balancer, have you set it to redirect connections > from same IP to same Dovecot server? If not, I think doing just that > would help a lot. > We don't actually have a load balancer in front of these boxes, just using Round Robin DNS to spread requests for webmail to webmail1, webmail2, or webmail3. Paul
[Dovecot] Memory Errors
I just loaded 1.0.0 on a new box and am getting the following errors periodically. Apr 19 16:36:00 imap01 dovecot: auth(default): *** glibc detected *** free(): invalid pointer: 0xb7f45d14 *** Apr 19 16:36:00 imap01 dovecot: child 1943 (auth) killed with signal 6 Apr 19 16:36:00 imap01 dovecot: auth(default): *** glibc detected *** malloc(): memory corruption: 0x080920a0 *** Apr 19 16:37:31 imap01 dovecot: auth(default): *** glibc detected *** malloc(): memory corruption: 0x08091449 *** Apr 19 16:37:31 imap01 dovecot: auth(default): pam(user,ip): Child process died Apr 19 16:37:31 imap01 dovecot: auth(default): PAM: Child 13425 died with signal 6 Apr 19 16:38:09 imap01 dovecot: IMAP(user): UID larger than next_uid in file /mail_home1/c/ch/user/Maildir/dovecot-uidlist (1 >= 1) Apr 19 16:38:46 imap01 dovecot: auth(default): *** glibc detected *** free(): invalid pointer: 0xb7ea7d14 *** Apr 19 16:38:46 imap01 dovecot: child 12280 (auth) killed with signal 6 Apr 19 16:38:46 imap01 dovecot: auth(default): *** glibc detected *** malloc(): memory corruption: 0x0809143f *** Has anyone else seen something similar? What additional information can I provide? Dovecot Version=1.0.0 OS: Debian Etch CPU: x86 Maildirs are stored in NFS and only accessed via Horde/IMP webmail client. I have three other Dovecot boxes(1.0.rc28) running Sarge and haven't seen this error before. dovecot -n follows Thanks for any help. Paul imap01:/usr/local/src/dovecot-1.0.0# dovecot -n # /usr/local/etc/dovecot.conf protocols: imap listen: *:143 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_process_per_connection: no default_mail_env: maildir:~/Maildir mail_location: maildir:~/Maildir mmap_disable: yes lock_method: dotlock maildir_copy_with_hardlinks: yes mail_plugins: quota imap_quota namespace: type: private separator: . prefix: INBOX. inbox: yes auth default: passdb: driver: pam userdb: driver: passwd plugin: quota: maildir
