similar to: Assertion failure in mail-index-view-sync.c

Hi all, I have seen this in log: dovecot: Dec 03 06:12:57 Error: IMAP(maurirrr): file mail-index-view-sync.c: line 666 (mail_index_view_sync_end): asser tion failed: (view->log_file_offset >= view->map->hdr.log_file_int_offset) dovecot: Dec 03 06:12:57 Error: IMAP(maurirrr): Raw backtrace: /usr/libexec/dovecot/imap [0x461d5e] -> /usr/libexec/dov ecot/imap [0x461acc] ->

I've been having a problem with a crashing Dovecot the last couple of months where it crashes after a couple of weeks of uptime. Been a bit difficult to diagnose. Anyway, we're now running 1.0.9 on a Sun Fire T1000 running Solaris 10. Any good ideas on how to pin-point the problem? - Peter Here's the output from syslog when the last crash happened: May 14 11:46:50 ifm.liu.se

Hi, We are using dovecot for some times (a little before 1.0), for IMAP and (a little for the moment) deliver. We have ~20000 logins/day, Maildirs are over NFS (with indexes too, for the moment...) Up to 1.0.5, we sometime have this error in maillog: ________________________________________________________________________ Nov 1 13:55:41 tic dovecot: IMAP(login): file mail-index-view-sync.c:

I'm running beta7 on two machines, with maildir on NFS. I have lockd running on all machines. I've found that Dovecot is highly unstable with NFS when accessing a mailbox on more than one machine at the same time. Both dovecot machines have: mmap_disable = yes lock_method = fcntl NFS is version 3, exported from a third linux machine. All machines are running 2.6.9 kernel. Any ideas

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.

Timo, Output of gdb session on the core file attached. This one only produced the following syslog: IMAP(user): UIDs broken with partial sync in mbox file /var/mail/r/user with no assert. Setup: Solaris 9, gcc 4.0.1 for dovecot build. Jeff Earickson Colby College -------------- next part -------------- Script started on Thu Sep 08 10:05:53 2005 %gdb imap core.rtohara GNU gdb 6.3 Copyright

Greetings - Now that users are beginning to pile up more on our new Dovecot-based IMAP service I'm seeing a small number of entries like this in the logfiles: Corrupted index cache file /mailstore/index/o/ozw100/.INBOX/ dovecot.index.cache : invalid record size We are using Dovecot 1.0.3 with Maildir folders served over NFS from NetApp filers, but the index files are stored on local

Timo, I saw a couple of these cores over the weekend. The syslog says: May 21 19:04:48 emerald dovecot: [ID 107833 mail.error] IMAP(user): Corrupted index cache file /home/students/s/user/.imap/sent-mail-apr-2004/dovecot.index.cache: indexid changed With a resulting core file from imap at this time. I also discovered a remaining lock file on the person's imap file: -rw------- 1 user

Just installed the latest (Dec. 12) CVS version and one user keeps getting this assertion failure. Todd dovecot: Dec 13 15:53:01 Error: 29718 imap(username): mbox sync: UID inserted in the middle of mailbox /mailhome/new/o/h/username/mbox (4863 > 3417, seq=780, idx_msgs=1913) dovecot: Dec 13 15:53:06 Error: 29718 imap(username): file mail-index-transaction.c: line 129

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

When attempting to save a message from the INBOX to a folder in a collection (like, .projects.dovecot), I get behavior like this (in GDB). Any clue what might be going wrong? Here's where a SIGABRT happens: 280 return array->buffer->used / array->element_size; This is the stack trace: (gdb) where #0 mail_index_map_get_ext_idx (map=0x1200c0db0, ext_id=0,

Hello, in addition to our mail system, we have some other systems which needs to know how many messages, and how many unread messages, a user has in his/her inbox (maildir). Currently, we have a mod_perl script which takes a mail address as input, and then traverses the maildir, and outputs the number of unread messages. Our challenge is that the maildirs are located on a SAN, and traversing a

On 24.01.2017 11:31, Tom Sommer wrote: > On 2017-01-24 10:25, Aki Tuomi wrote: >> On 24.01.2017 11:13, Tom Sommer wrote: >>> On 2017-01-18 15:27, mkliewe at gmx.de wrote: >>> >>>> dovecot crashes when I switch the quota tracking from dict to count. >>> >>> I have the same problem, but I use 'dict:file' as quota backend - >>>

These two are from CVS version as of 2005-11-03. There have only been these two asserts and we've had over 45000 logins. ---------------------------------------------------------------------- dovecot: Nov 16 13:35:34 Error: 18439 imap(username): Corrupted transaction log file /mailhome/new/c/h/username/.imap/INBOX/dovecot.index.log: Append with UID 53103, but next_uid = 53104 dovecot: Nov

Hi, I got all excited about IMAP NOTIFY support and tried enabling mailbox_list_index on my server. Unfortunately, I rather quickly ran into trouble of the segfault variety. This prevented me from doing basic things like seeing the contents of some of my folders. Disabling mailbox_list_index got me back up and running, but... darnit, that's annoying. The only message I got in my log file

We had to move our dovecot from one server to another and used rsync to move the mail but it took us some time.. In our log at the new server, we are getting a lot of these..: 2010/10/08 23:28:23 imap(emailadr): Error: Index /opt/vmail/ba-avis.no/bpe/mail/.Nettforum/dovecot.index: Lost log for seq=22 offset=25248 2010/10/08 23:28:23 imap(emailadr): Warning: fscking index file

I wrote a mostly-working CONDSTORE support for Dovecot today. You can try it with: hg clone http://hg.dovecot.org/dovecot-condstore/ There are a few problems left: - STORE FLAGS.SILENT should be sending FETCH MODSEQ updates - When SELECTing a mailbox while CONDSTORE hasn't yet been enabled in the session, Dovecot returns a higher HIGHESTMODSEQ than what's used after CONDSTORE is

Running 2.2.15 on FreeBSD 10.0. Forcing replication with: doveadm replicator replicate -f user at host.com on one user that I've seen some syslogs show up to see what's going on. Other users are fine. When I run the above command on the one user it produces a core dump. See below for syslog output and full backtrace: syslog output: Oct 26 22:44:09 d3cstorage dovecot: dsync-server(user

OS: CentOS 7 x86_64 Dovecot version: 2.2.31 (65cde28) (GhettoForge RPM) Filesystem: GlusterFS, but working on changing that. Only one server is receiving activity. Was getting messages about corrupt dovecot.map.index files. Changed to dotlock from fcntl to try to fix that. Reading symbols from /usr/libexec/dovecot/imap...(no debugging symbols found)...done. [New LWP 74012] Core was generated by

I am getting some panics after upgrading from 2.2.13 to 2.2.14 This panic happens for one user only, he is subscribed to 86 folders, on two of them this panic happens quite often - several times a day. The mbox folders seems OK, less than 30M with 30 and 200 messages. Panic: file mail-index-sync-update.c: line 250 (sync_expunge_range): assertion failed: (count > 0) hmk GNU gdb 6.8