similar to: dovecot-1.2 with managesieve patch: imap crash with backtrace

Displaying 10 results from an estimated 10 matches similar to: "dovecot-1.2 with managesieve patch: imap crash with backtrace"

2007 May 24
1
unexpected error message (maildir_sync_index)
Hello, I recently saw these errors in my log, and one of my users complained that Dovecot disconnected him unexpectedly. Any idea what might have happened? dovecot: Error: IMAP(bmoore at forkit.org): file maildir-sync.c: line 1075 (maildir_sync_index): assertion failed: (uid > prev_uid) dovecot: Error: IMAP(bmoore at forkit.org): Raw backtrace: /usr/local/libexec/dovecot/imap
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
2007 Apr 26
1
assertion failed
What is this ? dovecot: Apr 24 13:03:29 Error: IMAP(tina.burdujan): file maildir-sync.c: line 1075 (maildir_sync_index): assertion failed: (uid >prev_uid) dovecot: Apr 24 13:03:29 Error: IMAP(tina.burdujan): Raw backtrace: /usr/libexec/dovecot/imap [0x80b8741] -> /usr/libexec/dovecot/imap [0x80b819c] -> /usr/libexec/dovecot/imap(maildir_sync_index+0x898) [0x80695f8] ->
2009 Nov 02
2
dovecot-1.2.6: Panic: pool_data_stack_realloc(): stack frame changed
When playing with large numbers of IMAP keywords on dovecot-1.2.6 imap crashed: Panic: pool_data_stack_realloc(): stack frame changed Looks like either maildir_file_do() shouldn't T_BEGIN/T_END or the keywords array should start larger. 0 libSystem.B.dylib 0x00007fff875f4eba __kill + 10 1 libSystem.B.dylib 0x00007fff875f4eac kill + 14 2 libSystem.B.dylib
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:
2010 Apr 03
1
dovecot 2 beta4 errors & core dumps
Hi, While running imaptest with "clients=50 seed=123 msgs=100000000 random secs=600", I got errors : "Error: user at domain.com[55]: Unexpected BYE: * BYE IMAP session state is inconsistent, please relogin.". dovecot.log : Apr 03 10:23:47 imap(user at domain.com): Panic: file index- transaction.c: line 145 (index_transaction_rollback): assertion failed:
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
2009 Jun 29
1
Dovecot-1.1.15 panics
Dovecot-1.1.15 assert-fails frequently. Attached are some errors from the logs, and a stack trace from the common panic. Hope you can fix these soon. Thanks. 0 libSystem.B.dylib 0x00007fff8825e606 __kill + 10 1 libSystem.B.dylib 0x00007fff882e1c92 abort + 83 2 imap 0x0000000100069e1b default_fatal_finish + 70 3
2008 Jun 11
0
Dovecot 1.1 rc9 compilation warnings
I've tried compiling 1.1.rc9 on everything to hand and I get various compilation warnings (but the compilation finishes). I don't know whether any of them are worth tracking down? I'm guessing most of the differences depend on the default gcc options and a couple of them are probably specific to our setup. All were configured with ./configure --prefix=/opt/RDGdovect
2010 Apr 02
1
Dovecot Migration so far
We've been doing our own beta testing of Dovecot 2.0-beta4 IMAP (both direct IMAP and webmail-fronted), and we've had nothing but glowing compliments from our beta users/victims. I've also been running a lone box with the latest mercurial build and that's been running just fine too. All mail data is on NFS, but I've put indexes on the local disk, which has worked just dandy so