similar to: Dbox + imap_quota still crashing on 1.1rc4

Displaying 20 results from an estimated 200 matches similar to: "Dbox + imap_quota still crashing on 1.1rc4"

2008 Apr 01
0
Dovecot 1.1rc3 crashes with Dbox + imap_quota plugin
Version: Dovecot v1.1.rc3 OS: CentOS 5 running in OpenVZ CPU: x86_64 Was running fine with maildir and decided to get dbox a try. Test user created with a dbox mailstore backend and when a client logs in that tries to run a getquotaroot imap command the process SIGSEGV's. Have been able to narrow it down to dbox crashing against dict quota as well as dirsize. Maildir works just fine.
2005 Jun 08
2
Debugging test72
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,
2009 Aug 11
1
dovecot-1.2.3 (managesieve) crash with backtrace
>From the log: Aug 11 09:07:23 postamt dovecot: IMAP(zensy): Panic: file mail-index-transaction-view.c: line 106 (tview_apply_flag_updates): assertion failed: (map->hdr.record_size <= tview->record_size) Aug 11 09:07:23 postamt dovecot: IMAP(zensy): Raw backtrace: imap [0x80f0411] -> imap [0x80f0482] -> imap [0x80efe29] -> imap [0x80c839b] -> imap [0x80cea95] -> imap
2014 Apr 01
2
imap process and indexer-worker crash while creating folders
Hi, our dovecot processes sometimes crash when we create new folders. The "imap" process and the "indexer worker" process is crashing. We can reproduce this, we have a java program with multiple threads, and sometimes 2 threads try to create the same folder for the same user, and if both collide, dovecot processes crash. We don't see this happening in the real world if
2005 Sep 08
1
1.0alpha1: another imap core, no assert
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
2013 Apr 09
1
2.2.0rc6: crash with mailbox_list_index=yes (and virtual?)
Hello (Timo), depending on the client (with OfflineIMAP, but not a mobile one) my dovecot test configuration (config on request) crashes if mailbox_list_index=yes: Apr 9 09:26:31 host dovecot: imap-login: Login: user=<user>, method=CRAM-MD5, rip=2001:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx, lip=2001:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx, mpid=19028, TLS,
2006 May 22
1
beta8: cores on corrupted index file
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
2005 Apr 27
0
Assertion Failures in Current CVS version
I've attached a few assertion errors in imap. Any fixes or advice on where to look are appreciated. This is with the CVS version, current as of April 27. Todd Burroughs -------------- next part -------------- dovecot: Apr 27 00:00:45 Error: 5714 IMAP(chairman): file mail-index-transaction.c: line 808 (mail_index_update_ext): assertion failed: (seq > 0 && (seq <=
2008 Dec 01
1
Maildir loses keywords in index beyond 26
(NOTE: I am not on the mailing list so please Cc: me.) dovecot-1.1.6-2.fc10.i386 (configuration not changed from stock) Fedora 10 AMD Athlon XP ext3 Maildir format doesn't store keywords in the index properly -- it goes up to 26 and then further keywords are dropped. I ran the tests with a simple script that feeds the lines from "commands" to Dovecot one at a time and waits for
2009 Oct 03
1
Another 1.2.5 imap panic
We've had another random imap process crash. This is with the original 1.2.5 imap (I haven't applied the patch for two processes creating an index simultaneously): > Oct 03 13:24:56 imap-login: Info: Login: user=<xxxxxxxx>, method=PLAIN, rip=134.225.1.46, lip=134.225.16.6 > Oct 03 13:25:59 IMAP 6067 xxxxxxxx 134.225.1.46 : Info: delete: uid=483, msgid=<xxxxxxxx> > Oct
2015 Aug 06
3
Segfaults after upgrade to Debian Jessie
On Thu, 2015-08-06 at 09:49 +0200, Stephan Bosch wrote: > You have no debug symbols installed. Could you install dovecot-dbg > package and try again? Sorry, how's this: #0 sieve_validator_find_command_registration (valdtr=0xffffffff, command=0x7fc573c4bcd8 "extdata") at sieve-validator.c:309 No locals. #1 sieve_validator_register_command (valdtr=0xffffffff,
2019 Dec 03
0
[p2v PATCH 6/6] Remove whole-file.c
The only function in it, read_whole_file(), is not used anymore. (And anyway, the GLib function g_file_get_contents() can be used instead.) --- Makefile.am | 3 +- p2v.h | 3 -- whole-file.c | 94 ---------------------------------------------------- 3 files changed, 1 insertion(+), 99 deletions(-) delete mode 100644 whole-file.c diff --git a/Makefile.am b/Makefile.am index
2015 Aug 06
0
Segfaults after upgrade to Debian Jessie
What version of the extdata plugin are you using? This looks like a version built for Dovecot v2.1/Pigeonhole 0.3.0. Keep in mind that the extdata plugin is not part of the Pigeonhole distribution, so that will not be upgraded along with Pigeonhole. Since the extdata plugin is not part of the normal Debian packages (not afaik anyway), you likely compiled and installed the extdata plugin
2006 Jan 27
1
gcc 2.95 compile errors
Timo, This is what I get when I compile 1.0-beta2 with gcc 2.95. It looks like I can then open my problem mbox even without your mbox-sync patch. It turns out I'd been using gcc 3.2.2 inadvertently, probably via some sort of shell bug - I'd accidentally set an environment variable called "PATH=/opt/RDGgcc3/bin:/usr/bin ..." and I guess some script had mistaken it for the real
2019 May 24
0
Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000)
Known issue when folder cache is too big. Try rm -rf dovecot.index.cache for the folder. Aki On 24.5.2019 13.37, Ralf Hildebrandt via dovecot wrote: > I'm encountering a crash which this command: > > % doveadm import -u restore at backup.invalid mdbox:/home/copymail2/mdbox '' mailbox INBOX header X-Spam Yes SAVEDBEFORE 2019-05-23 > > doveadm(restore at
2019 May 24
2
Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000)
I'm encountering a crash which this command: % doveadm import -u restore at backup.invalid mdbox:/home/copymail2/mdbox '' mailbox INBOX header X-Spam Yes SAVEDBEFORE 2019-05-23 doveadm(restore at backup.invalid): Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000) doveadm(restore at backup.invalid): Error: Raw backtrace:
2020 Jan 10
0
Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000)
I'm trying this: doveadm import -u restore at backup.invalid mdbox:/home/copymail2/mdbox "" \ mailbox INBOX header X-Spam Yes nd I'm getting: doveadm(restore at backup.invalid): Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000) doveadm(restore at backup.invalid): Error: Raw backtrace:
2016 Aug 19
2
Crash on opening mailbox
Hi! I'm currently experiencing a crash of dovecot 2.2.25 on Gentoo, upon opening mailbox. The crash only triggers on opening inbox, other mailboxes seem to work fine. It happens every time, and can be reproduced on request. I also briefly tried 2.2.19, and it behaves the same. The bug seems to be triggered by some mail, as I encountered it previously and fixed by removing some spam. I
2015 Nov 16
0
[PATCH] p2v: Send physical server 'dmesg' output to debug dir on conversion server.
If the virt-p2v ISO doesn't contain the correct drivers for the hardware on the physical server, that can cause peculiar conversion problems. This was hard to diagnose because we could not see the 'dmesg' output from the physical server. Upload 'dmesg' output from the physical server (more precisely: from the virt-p2v ISO's kernel running on the physical server) to the
2015 Aug 17
2
Segfaults after upgrade to Debian Jessie
On Mon, 2015-08-17 at 14:13 +0200, Stephan Bosch wrote: > but until then you can avoid this by using the the exdata hg revision before tip > (57c8d3e6b562). Great, thanks for the quick reply, that fixed the compilation problem. I'm still getting a segfault though. This time the backtrace is: Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was