similar to: Dovecot+NFS: Copying messages causes failures (possible SIGABRT)

The configuration files has settings that seem to address the issues of using indexes on NFS (i.e. locking and mmap fixes), but we are using Dovecot on NFS, and when the load gets high we start to see a lot of NFS stale file handle errors, particularly with MS clients like Outlook. I see the discussion about these errors from last year. Any updates on the state of the code? Should we be using

Hello, I am running Dovecot 1.0.5 and seem to have lots of errors in my Dovecot logs. The worst errors are things like: Oct 30 16:11:42 delta2 dovecot: IMAP(x): Corrupted transaction log file /home/spamcop-net2/deputies/dovecot.index.log: end_offset (392) > current sync_offset (388) Oct 30 16:11:42 delta2 dovecot: IMAP(x): file mail-index-sync-update.c: line 841

Anyone run into this one? I'm using test53... Dec 3 13:08:17 aurora dovecot: IMAP(doug): file mail-index-sync-update.c: line 1160 (mail_index_sync_update_index): assertion failed: (map->records_count == map->hdr.messages_count) Dec 3 13:08:17 aurora dovecot: child 65942 (imap) killed with signal 6 It doesn't seem to correlate with any particular action. The only change I make

We recently upgraded to dovecot v1.0.15 (from v1.0.0 + some local fixes), and after this upgrade we've started to get a couple of failures from deliver: Jan 12 20:34:34 smtp1.ulh.mydomain.net deliver(someuser at somedomain.net): Raw backtrace: /usr/local/dovecot/libexec/dovecot/deliver(i_syslog_panic_handler+0x1c) [0x45577c] -> /usr/local/dovecot/libexec/dovecot/deliver [0x45537c] ->

There is OBVIOUSLY something wrong somewhere. EITHER a WHOLE bunch of us are stupider than we thought, the documentation left off a step, or there is something SO blatently obvious that we are ALL staring it in the face and missing it inches in front of our faces. This is exactly what I've had, (BUT I *D*I*D* have it running ok ...) and I STILL havent figured it out yet,... Subject:

Kristyan (and all) I just searched the samba website, and I couldnt find any reference to spnego except for a slide show (samba-lwny.ag ) that I can't open. ANYWAY. since I can't find any reference to the spnego parameter, could someone explain what it is, what it does, and HOW it can help us "stupid" people? It doesnt seem to be a parameter I've come across before..

I use the above kernel, can i get a ext3 patch for this kernel,Or will ext3 work with this kernel. Cheers redhead

Hi, I've compiled the SAMBA 3.0 alpha18 with all default options and installed well. Then I would join my NT 4.0 machine using the following steps (manual, not On the fly): # useradd -g groupid -d /dev/null -c "comment" -s /bin/false -m machine_name$ # passwd -l machine_name$ # smbpasswd -a -m machine_name$ after that I tried to join my NT4.0 to the Samba PDC, but it failed

Hi, Dovecot 2.0.13 imap process segfaults in the following scenario on Debian GNU/Linux unstable (amd64) and Solaris 10 (amd64): $ telnet localhost imap Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN] Dovecot ready. 1 login username password 1 OK [CAPABILITY IMAP4rev1

Hi, I'm having trouble as of about noon today. I noticed I wasn't getting any new messages in Thunderbird. I restarted it and still nothing. I looked at the log, and found nothing from dovecot for a long time (since perhaps noon today). I restarted dovecot, but still it didn't get me new mail. I finally removed dovecot.* in my Maildir folder and restarted dovecot. I'm

Found an imap crash. I'm using the CVS copy from March 23. This is running under Linux, kernel 2.6.11.something. We use mbox over NFS, everything is on the NFS server. There is currently only one dovecot server accessing the mailbox. Here's the log messages: dovecot: Apr 05 13:11:20 Error: 27911 IMAP(support): UIDVALIDITY changed (1112720886 -> 1112721068) in mbox file

One of the mbox files on my server causes dovecot to assert. I've caught the assert in gdb and have attached the backtrace. Unfortunatly my binary isn't built with debugging symbols, so I'm not sure how helpful it will be. smtp:/var$ uname -a Linux smtp 2.6.14-2-686-smp #1 SMP Sat Nov 26 13:37:07 UTC 2005 i686 GNU/Linux smtp:/var$ cat /etc/debian_version 3.1 smtp:/var$ dpkg -p

Greetings - I've just built Dovecot 1.0beta8 and find it refuses to start. This under Solaris 10 on an Intel-based Sun system. The error message Dovecot displays (on standard error) in response to /usr/local/sbin/dovecot is Fatal: Protocol imaps given more than once I've checked through my configuration file and the only mention of "imaps" is here: # Protocols

Hi folks! I have set up dsync replication with SSH according to http://wiki2.dovecot.org/Replication with the exception of having system users and calling doveadm dsync-server directly from authorized_keys, because the wrapper script posted on the above site is needless (at least in 2.2.10). However, while the two instances connect well to each other, no synchronisation is performed at all, the

I've seen this was mentioned before but remains unsolved. I upgraded Dovecot from 0.99 to v1.0.alpha4 yesterday and it rendered my inbox inaccessible: Dec 15 00:09:07 sand dovecot: imap(willers): Corrupted index file /home/willers/mail/.imap/INBOX/dovecot.index: messages_count too large (1121 > 1115) I've since moved that inbox away so I can view my new mail again. The error has

Here's a couple of assertion failures from CVS version as of Oct. 6. There's also a segfault but the core file was empty so I don't know if the log entries are much help. BTW, the searching speed using pine has dramatically improved, nice work! Todd ----------------------------------------- dovecot: Oct 12 12:04:28 Error: 20278 imap(username): file mail-index-sync-ext.c: line 155

Part of our migration plan takes our users from one endianness to another (big to little). Will the index and mail cache files survive? I'm seeing some new core dumps as the first test user is migrated, which makes me think... not. What about if we want to build dovecot 64 bit in the future? Will that cause problems too? Stack trace is below the log messages. I've edited the

Hi Timo, Awhile back I'd written about making changes to some of the log levels that dovecot writes to to stop the process from writing these to monitor. I wanted to run a few changes by you for this, just to make sure these won't cause problems somewhere else. And to send this to the list, in case anyone else wants to make similar changes in the future. In the file

Hi, I have the following code: Message, belongs_to :topic, :counter_cache => true topic = Topic.find_from_permalink(params[:id]) topic.messages.create(params[:message]) When the message gets created, then AR issues a supplemental SELECT to retrieve the message''s topic and then updates its messages_count. Why is that happening? If I do it manually: if

First off, just want to say Dovecot is great! We have been using it for several months now in a fairly large installation with only a few problems. 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.