Displaying 6 results from an estimated 6 matches similar to: "Subject: IMAP crash on index"
2009 Oct 06
1
Dovecot 1.2.4 - assertion crash in view_lookup_seq_range
Hi all,
We have a number of machines running Dovecot 1.2.4 that have been assert
crashing occasionally. It looks like it's occurring when the users
expunge their mailboxes, but I'm not sure as I can't reproduce it
myself. The error in the logs is:
Oct 6 07:33:09 oh-popmap3p dovecot: imap: user=<YYYY>, rip=XXXX,
pid=11931: Panic: file mail-index-view.c: line 264
2008 Dec 16
2
panic in mail-index-view.c
With just one user, on a virtual hosting system with several hundred
users spread across a couple of dozen domains, there is the following
error, repeated a couple of times a second without variation, when the
user tries to connect with Thunderbird to read his mail:
dovecot: Panic: IMAP(*******@****.co.uk): file mail-index-view.c: line
265 (view_lookup_seq_range): assertion failed: (first_uid
2008 Oct 20
5
SIGBART/SIGSEGV while SELECTing virtual folder
Hello!
I just installed Dovecot's latest nightly build (20081020) and tried the
virtual folder features. I started with a really simple "all" folder:
| # virtual/all
| *
| all
But selecting this folder causes dovecot to panic (in most cases).
While trying to debug this, I got slightly different results and I am
not really sure yet if this is just non-deterministic, depends on
2016 Dec 05
2
2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)
Hi,
Dec 5 20:24:31 dovecot: imap(xx at yy.zz,7ckWZu1CuZFVTILa): Fatal: master:
service(imap): child 7292 killed with signal 6 (core dumped)
Dec 5 20:24:32 dovecot: imap(xx at yy.zz,LnAlZu1COBVVTILa): Panic: file
mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion
failed: (first_uid > 0)
Dec 5 20:24:32 dovecot: imap(xx at yy.zz,LnAlZu1COBVVTILa): Error: Raw
backtrace:
2016 Dec 06
0
2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)
Hi,
On 05-Dec-16 20:28, Toni Mattila wrote:
> Panicing stopped when all index files where deleted.
It happens again in same user account, so rebuilding indexes didn't fix it.
Here's bt full instead of just bt:
#0 0x001d4402 in __kernel_vsyscall ()
No symbol table info available.
#1 0x00949d70 in raise () from /lib/i686/nosegneg/libc.so.6
No symbol table info available.
#2
2016 Dec 06
2
2.2.27 panic file mail-index-map.c: line 549 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0)
On 06.12.2016 09:32, Toni Mattila wrote:
> Hi,
>
> On 05-Dec-16 20:28, Toni Mattila wrote:
>> Panicing stopped when all index files where deleted.
>
> It happens again in same user account, so rebuilding indexes didn't
> fix it.
>
> Here's bt full instead of just bt:
> #0 0x001d4402 in __kernel_vsyscall ()
> No symbol table info available.
> #1