similar to: Dovecot 1.1.2, index-sync.c, line 39, assertion

Displaying 17 results from an estimated 17 matches similar to: "Dovecot 1.1.2, index-sync.c, line 39, assertion"

2008 Jul 25
0
Dovecot 1.1.2, SIGABRT on copy mail
Hi folks, with the brandnew release Dovecot 1.1.2, the daemon killed itself with signal 6 (SIGABRT) when trying to save a mail from the INBOX to another folder. The mail client is PINE 4.64. After reconnecting to the IMAP server, the mail was actually copied to the destination folder, but the original mail was still in the INBOX and not flagged as "deleted". This is the panic: Jul 25
2008 Aug 17
4
Dovecot 1.1.2, index_mailbox_set_recent_seq crash again
Hi folks, after about 3 weeks without any problems, I've found this crash in yesterday's logfile (again related to index_mailbox_set_recent_seq): Aug 16 03:39:58 linux dovecot: IMAP(user1): Raw backtrace: imap [0x80cf8e0] -> imap [0x80cf93a] -> imap [0x80cf26c] -> imap [0x809d11a] -> imap(index_mailbox_set_recent_seq+0x3e) [0x809d15e] -> imap(mbox_sync+0x105d) [0x80823fd]
2008 Mar 10
2
dovecot 1.1.rc3 assertion failed at index_mailbox_set_recent_uid while deleting message with thunderbird.
To some users happens this assertion failure while deleting a message. dovecot: Mar 10 08:40:44 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists (&ibox->recent_flags, uid)) dovecot: Mar 10 08:40:44 Error: IMAP(user): Raw backtrace: [see bleow] dovecot: Mar 10 08:40:44 Error: child 17683 (imap) killed with signal 6 And the
2009 May 04
2
index_mailbox_set_recent_uid error on 1.1.14
Seen this error a few times from dovecot-1.1.14, Mac OS X, 64-bit Intel. Pretty sure NFS was not used. Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: seq_range_exists(&ibox->recent_flags, uid) The backtrace is: 0 libSystem.B.dylib 0x00007fff85025166 __kill + 10 1 libSystem.B.dylib 0x00007fff850a80e0
2008 Apr 09
1
dovecot-1.1.rc3 assertion failure in index-sync.c
We just came across a mailbox today that, when accessed via POP3 or IMAP, crashes Dovecot. It seems to be another index-related corruption issue (as removing "dovecot.index" for INBOX fixed it); Using POP3: dovecot: Apr 09 10:28:14 Warning: POP3(USERNAME): Maildir /mail/USERNAME/Maildir: UIDVALIDITY changed (1145576765 -> 1207677483) dovecot: Apr 09 10:28:14 Panic:
2009 Jul 25
0
dovecot-1.2 with managesieve patch: imap crash with backtrace
Log: Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): /home/v/i/virus-al/Maildir/dovecot-uidlist: next_uid was lowered (216 -> 2) Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): Panic: file index-sync.c: line 25 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): Raw backtrace: imap [0x80efdb1]
2009 Jun 20
1
imap signal 6 crash with backtrace (1.2rc5)
GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as
2010 Mar 09
1
Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)
Hi, captured a crash on mdbox with latest mercurial: Mar 9 13:56:28 spectre dovecot: imap(tlx at leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=1438073): msg header has bad magic value Mar 9 13:56:28 spectre dovecot: imap(tlx at leuxner.net): Corrupted dbox file /var/vmail/leuxner.net/tlx/mdbox/storage/m.59 (around offset=1438073): uid=4831
2008 Aug 08
1
Dovecot crashing
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sent an e-mail off as was detailed here: http://wiki.dovecot.org/MboxProblems for crashes but I also wanted to see if any of you folks had insight into the issue. Dovecot is crashing on a certain user inbox which is in mbox format as well as one of the users other mbox files. The crash doesn't exactly match what is listed in the aforementioned
2003 May 10
0
Protocol problem (bug?) with rsync-2.5.6
On Sat, May 10, 2003 at 01:26:17AM +0200, wrote: > Hi, > > let me shortly describe the background of my problem: I was using a Gentoo box > as a workstation and a NetBSD-1.6 box as a backup machine. Everything ran > perfectly. Now I switched my workstation OS to FreeBSD-4.8_RELEASE. > > Both rsyncs are made from the ports, respectively (with Gentoo, it were the >
2012 May 07
1
Panic in index-sync.c: line 25 on dovecot-1.2.17
Hi, with dovecot-1.2.17 (yes i know it's old) i'm getting the folowing error after doing a system upgrade. May 7 22:04:26 mail dovecot: deliver(elon): Panic: file index-sync.c: line 25 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) May 7 22:04:27 mail kernel: pid 79989 (deliver), uid 4873: exited on signal 6 (core dumped) this
2008 Aug 29
4
Lots of assertion PANICs in error log
I have just upgraded to dovecot 1.1.2 and am seeing lots of the following panic messages filling up the error logs: dovecot: Aug 29 09:34:32 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) dovecot: Aug 29 09:34:32 Error: IMAP(user): Raw backtrace: imap [0x483888] -> imap [0x484293] -> imap
2008 Aug 21
3
dovecot panic after upgrade 1.0.15 to 1.1.2
I recently upgraded dovecot from 1.0.15 to 1.1.2 and since then I am getting the following types of things in the logs: Aug 21 17:23:13 mail1 dovecot: imap-login: Login: user=<myuser>, method=PLAIN, rip=172.16.78.20, lip=172.16.78.22 Aug 21 17:24:01 mail1 dovecot: Panic: IMAP(myuser): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed:
2008 May 30
4
v1.1.rc6 released
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc6.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc6.tar.gz.sig This is it. The first v1.1 release that actually deserves the "release candidate" name. It contains everything I require from v1.1.0 release. There are two bugs left that I'd like to get fixed, but they won't block v1.1.0 release: *
2008 May 30
4
v1.1.rc6 released
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc6.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc6.tar.gz.sig This is it. The first v1.1 release that actually deserves the "release candidate" name. It contains everything I require from v1.1.0 release. There are two bugs left that I'd like to get fixed, but they won't block v1.1.0 release: *
2008 Aug 19
2
assertion failed
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I just switched over to dovecot 1.1.2 on our live system last night. I'm seeing the following errors in the logs: Aug 19 10:01:03 goku dovecot: [ID 107833 mail.crit] Panic: IMAP(elevin): file in dex-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range _exists(&ibox->recent_flags, uid)) I did apply the assertion fix
2008 Jul 20
2
Dovecot 1.1.1 killed with SIGABRT
Hi folks, with Dovecot 1.1.1, I've had two "crashes" (SIGABRT) recently. Dovecot 1.1.1 has been compiled from source and is running on Fedora 8 Linux 32 Bit (all patches) with custom OpenSSL 0.9.8h. [ output of "dovecot -n" ] # 1.1.1: /usr/local/dovecot/etc/dovecot.conf ssl_cert_file: /usr/local/dovecot/etc/dovecot.crt ssl_key_file: /usr/local/dovecot/etc/dovecot.key