similar to: Assertion during dsync receive

Thanks. I've had the user clear out that mailbox, and replication is working fine for them again. Is there a better way to catch this than watch for crashes and read the backtrace to find what mailbox needs to be shrunk? Where is the threshold for "too big"? -- Ian On 2/23/18 11:33 AM, Aki Tuomi wrote: > The mailbox is too big. > > > > --- > Aki Tuomi >

The mailbox is too big. ---Aki TuomiDovecot oy -------- Original message --------From: Ian Bobbitt <ibobbitt at globalnoc.iu.edu> Date: 23/02/2018 17:52 (GMT+02:00) To: dovecot at dovecot.org Subject: Assertion during dsync receive Hi, I'm getting an assertion failed on the receiving side, causing syncs to fail for one user. The servers are setup so that only one is receiving any

Once you cache grows bigger than 0x4000000 you have problems ---Aki TuomiDovecot oy -------- Original message --------From: Ian Bobbitt <ibobbitt at globalnoc.iu.edu> Date: 23/02/2018 20:33 (GMT+02:00) To: dovecot at dovecot.org Subject: Re: Assertion during dsync receive Thanks. I've had the user clear out that mailbox, and replication is working fine for them again.

OS: CentOS 7 x86_64 Dovecot version: 2.2.31 (65cde28) (GhettoForge RPM) Filesystem: GlusterFS, but working on changing that. Only one server is receiving activity. Was getting messages about corrupt dovecot.map.index files. Changed to dotlock from fcntl to try to fix that. Reading symbols from /usr/libexec/dovecot/imap...(no debugging symbols found)...done. [New LWP 74012] Core was generated by

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:

Steffen, 2.2.18 (2de3c7248922) Best regards, Sergey Schwartz Senior System Administrator Biblio Globus Tour Operator www.bgoperator.ru T: +7 495 5042500 ext 1532 E: sergey.schwartz at bgoperator.com 22.07.2015 12:16, Steffen Kaiser ?????: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wed, 22 Jul 2015, Sergey Schwartz wrote: > >> Should I report a bug or there

Do you have a huge >4GB dovecot.index.cache file? > On 17 Nov 2015, at 13:04, Sergey Schwartz <sergey.schwartz at bgoperator.com> wrote: > > Gentlemen, > > imap hits the same problem > > Nov 17 14:02:06 mx10 dovecot: imap(oleg.vasilyev at bgoperator.com): Panic: file mail-index-util.c: line 37 (mail_index_uint32_to_offset): assertion failed: (offset <

root at mx10:~# doveadm force-resync -u oleg.vasilyev at bgoperator.com noreply-05-08-2015 doveadm(oleg.vasilyev at bgoperator.com): Warning: fscking index file /srv/vmail/current/bgoperator.com/oleg.vasilyev/storage/dovecot.map.index doveadm(oleg.vasilyev at bgoperator.com): Warning: mdbox /srv/vmail/current/bgoperator.com/oleg.vasilyev/storage: rebuilding indexes doveadm(oleg.vasilyev at

Gents, I've just upgraded to the latest build of dovecot , now lmtp delivery process panics for just one user Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev at bgoperator.com): Panic: file str.c: line 22 (str_new_const): assertion failed: (str[len] == '\0') Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev at bgoperator.com): Panic: file str.c: line 22 (str_new_const):

https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig * auth: Use timing safe comparisons for everything related to passwords. It's unlikely that these could have been used for practical attacks, especially because Dovecot delays and flushes all failed authentications in 2 second intervals. Also it could have worked only

https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig * auth: Use timing safe comparisons for everything related to passwords. It's unlikely that these could have been used for practical attacks, especially because Dovecot delays and flushes all failed authentications in 2 second intervals. Also it could have worked only

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:

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 have started getting these in my log. ?What does this mean and what do I need to do? ?Panic: file mail-index-util.c: line 37 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000) Dec 12 23:29:44 mail dovecot: imap(jeff at stariontech.com): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x3cafa) [0x7f38c5a2cafa] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3cb46)

I've got a bit more details Jul 24 10:21:50 mx10 dovecot: imap(oleg.vasilyev at bgoperator.com): *Panic: file mail-index-util.c: line 37 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000)* Jul 24 10:21:50 mx10 dovecot: imap(oleg.vasilyev at bgoperator.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x7c96f) [0x7fe4a719d96f] ->

Mar 19 16:54:37 lmtp(xxxx at xxx.xxx): Panic: file file-lock.c: line 269: unreached Mar 19 16:54:37 lmtp(xxxx at xxx.xxx): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x35f647e07a] -> /usr/lib/dovecot/libdovecot.so.0 [0x35f647e0e6] -> /usr/lib/dovecot/libdovecot.so.0 [0x35f647d4ac] -> /usr/lib/dovecot/libdovecot.so.0 [0x35f6481edf] ->

2.2.25 (also happens on 2.2.24). Happens every time I try to make deliver and only for this user: Jul 14 09:52:02 mbox dovecot: lmtp(25601): Connect from local Jul 14 09:52:02 mbox dovecot: lmtp(powiadomienia): session=<CRU2EaJEh1cBZAAALZVUYQ>, Error: Index /var/mail/powiadomienia/dovecot.index: Lost log for seq=1009 offset=40: Missing middle file seq=1009 (between 1009..4294967295) Jul 14

On 13/04/16 06:41, Timo Sirainen wrote: > On 09 Apr 2016, at 21:48, Hugh Bragg <hughbragg at dodo.com.au> wrote: >> I'm repeatedly getting this error: >> >> Apr 07 04:37:27 imap(mymail at address): Panic: file mail-search.c: line 84 (mail_search_arg_init): assertion failed: (arg->initialized.keywords == NULL) >> Apr 07 04:37:27 imap(mymail at address):

Hello, I'm trying to figure out if this is a configuration issue or an actual bug. Dovecot does start, but if anybody tries to log in or if you run sievec you get an assertion fail and a coredump. --- sievec(root): Panic: file mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns != NULL) sievec(root): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9c3a2)

Thanks. Assuming that the IMAP mail directory for the account affected is under /home/xyz/mail, are you talking about the contents of the index directory, excluding the log file therein? On Wed, Nov 28, 2018 at 2:29 PM Thomas Durand <tom at rezoo.org> wrote: > Hi, > > I had the similar messages after an upgrade then downgrade. I was able to > fix by removing all indexes files.