similar to: Dovecot panic for one user after upgrading

Displaying 20 results from an estimated 900 matches similar to: "Dovecot panic for one user after upgrading"

2018 Jan 03
0
Dovecot panic for one user after upgrading
Hi! The problem seems to occur during mail index processing. Can you try deleting all dovecot.index* files under this user's maildir. There might be some more under various folders. Aki On 03.01.2018 08:51, Owen B. Mehegan wrote: > The EC2 instance that I run Dovecot on (personal mail server) was > forcibly "retired" yesterday, and as a result I ended up rebuilding >
2015 Nov 10
3
lmtp panic
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):
2015 Nov 13
2
lmtp panic
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
2016 May 21
3
mail-search backtrace
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):
2016 Mar 19
3
Crash when setting quota = count:User quota
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] ->
2016 Jul 14
3
Panic: file mail-transaction-log-file.c: line 104 (mail_transaction_log_file_free): assertion failed: (!file->locked)
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
2020 Mar 31
3
doveadm backup from gmail with imapc
On Tue, 2020-03-31 at 09:06 +0300, Aki Tuomi wrote: > > > > On 30/03/2020 22:11 Ben Mulvihill <ben.mulvihill at gmail.com> wrote: > > > > ? > > I am trying to backup a gmail account (not the one I am writing > > from) > > to dovecot, using doveadm-backup and imapc, but am having ssl > > connection problems. > > > > ted at
2015 Nov 21
2
lmtp panic
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 <
2017 Apr 20
3
namespace assertion failed
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)
2018 Nov 28
3
Dovecot crash
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.
2018 Jul 25
3
Panic: Leaked view for index - virtual mailbox
And can you provide dovecot --version too, please. Aki > On 25 July 2018 at 09:18 Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > Hi! > > Which debian release is this? > > Aki > > > On 25 July 2018 at 05:18 Jakobus Sch?rz <jakobus.schuerz at ebcont.com> wrote: > > > > > > Hi There! > > > > I run into this problem
2018 Nov 28
2
Dovecot crash
This happening when my Thunderbird client is trying to establish a connection with a Dovecot server. Some background first: 1) I am running Thunderbird 6.20.1 from a Linux client. 2) Other clients (e.g. Maildroid in my Android phone) do not have any issues. 3) The Dovecot software is version 2.2.9, running in a Linux server. 4) This may be the root of the problem: at some point, the
2017 Mar 21
3
replicator crashing - oom
I have the following in my log: Mar 21 14:46:59 bubba dovecot: replicator: Panic: data stack: Out of memory when allocating 1073741864 bytes Mar 21 14:46:59 bubba dovecot: replicator: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x97c90) [0x7f4638a7cc90] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x97d6e) [0x7f4638a7cd6e] ->
2018 Nov 08
2
panic when using dovecot master account
Hello, I am running dovecot 2.2.34 (874deae), on Debian stable, from backports. I just tried the master account, and although everything worked in the email client, I had logs in the error logs: > imap(mirina): Panic: file mail-index-sync.c: line 413 > (mail_index_sync_begin_to2): assertion failed: (!index->syncing) > Nov 08 22:06:24 osaka dovecot[1450]: imap(mirina): Error: Raw
2015 Mar 10
5
Released Pigeonhole v0.4.7.rc1 for Dovecot v2.2.16.rc1
Hello Dovecot users, Last time I had a few stupid problems in the releases, so I'll follow Timo's example and I release an RC first. The highlights include the implementation of the index and metadata extensions. Quite a few bugs are fixed as well. Changelog v0.4.7: * editheader extension: Made protection against addition and deletion of headers configurable separately. Also, the
2015 Mar 10
5
Released Pigeonhole v0.4.7.rc1 for Dovecot v2.2.16.rc1
Hello Dovecot users, Last time I had a few stupid problems in the releases, so I'll follow Timo's example and I release an RC first. The highlights include the implementation of the index and metadata extensions. Quite a few bugs are fixed as well. Changelog v0.4.7: * editheader extension: Made protection against addition and deletion of headers configurable separately. Also, the
2018 Jul 25
2
Panic: Leaked view for index - virtual mailbox
Hi There! I run into this problem with virtual Mailboxes on release-2.3.2 (and also in master and in older versions of dovecot) I added the core-file. Jul 25 04:11:29 aldebaran dovecot[10573]: imap(jakob)<11292><rg2GZclxHaPAqADc>: Panic: Leaked view for index /var/lib/dovecot/db/indexes/Maildir/jakob/&ANY-BB/dovecot.index: Opened in index-storage.c:338 Jul 25 04:11:29
2016 Dec 12
3
Dovecot 2.2.27 > 2.2.24 downgrade errors
Hello. Due win10 issue I had to downgrade 2.2.27 > 2.2.24 and now some gettings errors for some users: Dec 12 14:42:17 server dovecot: imap(user): Panic: file mail-index-sync-keywords.c: line 227 (keywords_update_records): assertion failed: (data_offset >= sizeof(struct mail_index_record)) Dec 12 14:42:17 star dovecot: imap(senefelder): Error: Raw backtrace:
2020 Aug 19
7
Indexer error after upgrade to 2.3.11.3
Hi, after the upgrade to Dovecot 2.3.11.3, from 2.3.10.1, I see frequently these errors from different users: Aug 18 11:02:35 Panic: indexer-worker(info at domain.com) session=<g71KISOttvS5LNVj:O3ahCyuZO18cYAAAEPCW+w>: file http-client-request.c: line 1232 (http_client_request_send_more): assertion failed: (req->payload_input != NULL) Aug 18 11:02:35 Error: indexer-worker(info at
2020 Oct 16
2
Indexer error after upgrade to 2.3.11.3
On 16.10.20 18:00, Scott Q. wrote: > This reminds me, the way I was able to reproduce this consistently was > by having large headers ( 100+ lines ). > > > On Friday, 16/10/2020 at 11:49 Patrik Peng wrote: > > On 19.08.20 17:37, Josef 'Jeff' Sipek wrote: > >> On Wed, Aug 19, 2020 at 17:03:57 +0200, Alessio Cecchi wrote: >>> Hi,