similar to: Backtrace:dovecot/imap with 2.0.9 hg checkout from 1st of Febrauary

This may be identical to the one I posted previously. >From the log: Jan 12 15:25:55 postamt dovecot: imap(mfxxxch): Panic: file squat-trie.c: line 876 (squat_build_word): assertion failed: (i + bytelen <= size) Jan 12 15:25:55 postamt dovecot: imap(mfxxxch): Error: Raw backtrace: /usr/dovecot-2/lib/dovecot/libdovecot.so.0(+0x3b861) [0xb7721861] ->

The log says: Jan 10 19:41:19 postamt dovecot: imap(heixxxxe): Panic: file squat-trie.c: line 876 (squat_build_word): assertion failed: (i + bytelen <= size) Jan 10 19:41:19 postamt dovecot: imap(heixxxxe): Error: Raw backtrace: /usr/dovecot-2/lib/dovecot/libdovecot.so.0(+0x3b861) [0xb7639861] -> /usr/dovecot-2/lib/dovecot/libdovecot.so.0(+0x3b8cf) [0xb76398cf] ->

https://bugzilla.samba.org/show_bug.cgi?id=10497 Summary: rsync fails to sync certain sparse file combinations with compression Product: rsync Version: 3.1.1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

Hi, I obtain continuosly segmentation fault of processes pop3 and imap, with version 2.2.10. This is the error for the pop3 process (but for imap is is the same): 2014-02-10 11:06:22 pop3(xxxxxxx at yyyyyyyy.zz): Fatal: master: service(pop3): child 23804 killed with signal 11 (core dumped) This is the kernel log: Feb 10 11:06:22 pecpop5 kernel: pop3[23804]: segfault at 7fa42a3f4070 ip

hello list when I run the step make for update my samba4 I have the follow warning warning: The current binary is a PIE (Position Independent Executable), which GDB does NOT currently support. Most debugger features will fail if used in this session. libndr.so: symbol ndr_transfer_syntax_ndr64 has changed - please update major version old_signature: uuid = {time_low = 1903232307,

Hey, i am now a bit deeper into dovecot debugging with gdb and have a full bt now, with debugging infos. Is there a patch that resolve this Problem in dovecot 2.2.22-1ubuntu2.13 for ubuntu 16? Here the bt: (gdb) bt full #0 0x00007ffff73cf3f3 in array_count_i (array=0x555555810d38) at ../../src/lib/array.h:155 No locals. #1 message_part_finish (ctx=ctx at entry=0x555555810ce0)

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

I'm not sure how useful this is with optimization turned back on, but here it is anyway. This was just a one off that happened last night: Jan 27 20:49:05 gehenna17.rutgers.edu dovecot: IMAP(user): fscking index file /rci/nqu/rci/u2/user/dovecot/.INBOX/dovecot.index Jan 27 20:49:05 gehenna17.rutgers.edu dovecot: IMAP(user): Panic: file mail-transaction-log-view.c: line 108

Jun 2 10:05:14 hostname dovecot: IMAP(testuser): Panic: file istream- raw-mbox.c: line 380: assertion failed: (new_pos > 0) Jun 2 10:05:14 hostname dovecot: dovecot: child 544822 (imap) killed with signal 6 (dbx) where raise(??) at 0x90000000005a68c abort() at 0x900000000085c2c default_fatal_finish(type = LOG_TYPE_PANIC, status = 0), line 160 in "failures.c"

Hi, while searching through the message bodies in a real folder I got a coredump. I used the master user for this operation. dovecot.index* files have been removed before I started this operation. This looks a bit different to my previous report. Coredump: Program terminated with signal 6, Aborted. [New process 1628] #0 0x00002b5e82a8ced5 in raise () from /lib/libc.so.6 #0 0x00002b5e82a8ced5

Please keep responses on list. Can you please run valgrind on this, as it appears to be some sort of memory corruption issue. Aki > On April 7, 2017 at 5:37 AM Hongying Liu <hongyliu at redhat.com> wrote: > > > Thanks for your response. > > (gdb) p cache > $1 = (struct mail_cache *) 0x7fc4a811a320 > (gdb) p cache->hdr > $2 = (const struct mail_cache_header

Sorry for late response. This issue occurs ran randomly. So I don't know how to run valgrind command. 2017-04-10 17:14 GMT+08:00 Hongying Liu <hongyliu at redhat.com>: > Sorry for late response. > > This issue occurs ran randomly. So I don't know how to run valgrind > command. > > I upload the coredump. > > The version of dovecot is

On Tue, Jun 20, 2017 at 02:26:59AM -0400, Travis S. Johnson wrote: >Hello, > >I came across an interesting problem in my home lab a few weeks ago as I'm >prepping for my RHCE exam using Michael Jang study guide. I've been at this >for days now, and I still can't wrap my head around how two or more virtual >networks in default NAT configuration are even allowed to

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:

Backtrace:/usr/local/libexec/dovecot/imap 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

file message-address.c: line 43 (parse_local_part): assertion failed: (ctx->parser.data != ctx->parser.end) #0 0x001b3402 in __kernel_vsyscall () No symbol table info available. #1 0x0043ed20 in raise () from /lib/libc.so.6 No symbol table info available. #2 0x00440631 in abort () from /lib/libc.so.6 No symbol table info available. #3 0x080f6968 in default_fatal_finish

Hello, I recently upgraded to dovecot 2.0.2 (on gentoo ~amd64) and now fts_squat's index building seems to hang for some of my mailboxes. The imap process gets stuck at 100% cpu usage and dovecot.index.search is never touched. I traced the problem to a message (attached) for one of the problematic mailboxes. Also attached are a full backtrace and the output of dovecot -n. The problem

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:

Hello, I came across an interesting problem in my home lab a few weeks ago as I'm prepping for my RHCE exam using Michael Jang study guide. I've been at this for days now, and I still can't wrap my head around how two or more virtual networks in default NAT configuration are even allowed to communicate with each other despite what the libvirt documentation said. Here's the

I haven't seen this before 1.1b16, it happened to two users today while they were searching using fts. Feb 18 16:41:36 hill dovecot: IMAP(username): file buffer.c: line 288 (buffer_set_used_size): assertion failed: (used_size <= buf->alloc) Feb 18 16:41:36 hill dovecot: child 53560 (imap) killed with signal 6 I can probably narrow it down to an example mail if needed. GNU gdb 6.1.1