Re: Director with dovecot 2.3 and Panic/Fatal error

> On 19/03/2020 17:02 Alessio Cecchi wrote: > > > > Hi, > > after the upgrade to Dovecot 2.3 for our director ring we found some times > in the log errors like this: > > Mar 18 14:22:51 Panic: imap-login: file iostream-openssl.c: line 599 > (openssl_

Director with dovecot 2.3 and Panic/Fatal error

Hi, after the upgrade to Dovecot 2.3 for our director ring we found some times in the log errors like this: Mar 18 14:22:51 Panic: imap-login: file iostream-openssl.c: line 599 (openssl_iostream_handle_error): assertion failed: (errno != 0) Mar 18 14:22:51 Fatal: imap-login: master: service

Re: imap panic: file array.c: line 10 (array_idx_modifiable_i)

‐‐‐ Original Message ‐‐‐ On Tuesday, January 28, 2020 10:17 AM, mabi wrote: > > Your separator seems to be . instead of / so maybe inbox.* > > Thanks, that was it! Now let's see if I still get this panic... Unfortunately even after a successful force-resync of all mai

Re: imap panic: file array.c: line 10 (array_idx_modifiable_i)

‐‐‐ Original Message ‐‐‐ On Tuesday, January 28, 2020 10:12 AM, Sami Ketola wrote: > Your separator seems to be . instead of / so maybe inbox.* Thanks, that was it! Now let's see if I still get this panic...

Re: imap panic: file array.c: line 10 (array_idx_modifiable_i)

> On 28 Jan 2020, at 10.31, mabi wrote: > > ‐‐‐ Original Message ‐‐‐ > On Tuesday, January 28, 2020 9:06 AM, Sami Ketola > wrote: > >> doveadm does not travel over namespace boundaries. you need to run it >> separately for all namespaces you have with NAMESPACE/* as folder > > I

Re: imap panic: file array.c: line 10 (array_idx_modifiable_i)

‐‐‐ Original Message ‐‐‐ On Tuesday, January 28, 2020 9:06 AM, Sami Ketola wrote: > doveadm does not travel over namespace boundaries. you need to run it > separately for all namespaces you have with NAMESPACE/* as folder I see, so with my following namespace config: namespace inbox

Re: imap panic: file array.c: line 10 (array_idx_modifiable_i)

> On 28 Jan 2020, at 9.42, mabi wrote: > > So it looks like it did something but only for the INBOX mailbox. How do I > make force-resync do its job on all mailboxes? doveadm does not travel over namespace boundaries. you need to run it separately for all namespaces you have with

Re: imap panic: file array.c: line 10 (array_idx_modifiable_i)

‐‐‐ Original Message ‐‐‐ On Monday, January 27, 2020 8:37 AM, Aki Tuomi wrote: > You could try force-resync, it is safe to run. > > Anyways, without backtrace from core file it's hard to say. Hi Aki, I now ran the following command to force resync all mailboxes: sudo doveadm -Dv

Re: imap panic: file array.c: line 10 (array_idx_modifiable_i)

; > > Dovecot 2.1.7 (Debian 7) mailbox server to a Dovecot 2.3.4 (Debian 10) > > > > mailbox server and one particular mailbox does not work properly and > > > > generates the following error log entries: > > > > Jan 21 09:39:21 Panic: > >

Re: imap panic: file array.c: line 10 (array_idx_modifiable_i)

Debian 7) mailbox server to a Dovecot 2.3.4 (Debian 10) mailbox >>> server and one particular mailbox does not work properly and generates the >>> following error log entries: >>> Jan 21 09:39:21 Panic: >>> imap(EMAIL_ADDRESS)<7741>: file array.c: >>>

Re: imap panic: file array.c: line 10 (array_idx_modifiable_i)

ildir format) from a Dovecot > > 2.1.7 (Debian 7) mailbox server to a Dovecot 2.3.4 (Debian 10) mailbox > > server and one particular mailbox does not work properly and generates the > > following error log entries: > > Jan 21 09:39:21 Panic: > > imap(EMAIL_ADD

Re: imap panic: file array.c: line 10 (array_idx_modifiable_i)

Hello, > > I just migrated a few dovecot IMAP mailbox (Maildir format) from a Dovecot > 2.1.7 (Debian 7) mailbox server to a Dovecot 2.3.4 (Debian 10) mailbox server > and one particular mailbox does not work properly and generates the following > error log entries: > &

imap panic: file array.c: line 10 (array_idx_modifiable_i)

Hello, I just migrated a few dovecot IMAP mailbox (Maildir format) from a Dovecot 2.1.7 (Debian 7) mailbox server to a Dovecot 2.3.4 (Debian 10) mailbox server and one particular mailbox does not work properly and generates the following error log entries: Jan 21 09:39:21 Panic: imap

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@backup.invalid mdbox:/home/copymail2/mdbox "" \ mailbox INBOX header X-Spam Yes nd I'm getting: doveadm(restore@backup.invalid): Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset &l

Re: Panic: file smtp-client-connection.c: line 1212 (smtp_client_connection_established): assertion failed: (!conn->connect_succeeded)

Is this (DOV-3600) fixed in 2.3.9? Best regards Hativ Am Montag, den 14.10.2019, 09:44 +0200 schrieb Stephan Bosch: > On 11/10/2019 10:06, Hativ via dovecot wrote: > > Hello Aki, > > I have this problem just with 2.3.8, my self-compiled 2.3.3 works > > fine. I have previously tried to update from

Re: FTS indexer-worker Panic

Please kindly file an issue on github, together with an example of email causing the panic On 2019-11-11 15:21, Yarema via dovecot wrote: Set up fts_xapian over the weekend and re-indexed. https://github.com/grosjo/fts-xapian Tried to search my INBOX and got: dovecot: indexer-worker

Re: BUG: panic when using fs:posix as dict for acl_shared_dict

): Panic: file dict-fs.c: line 127 (fs_dict_iterate_init): assertion failed: ((flags & DICT_ITERATE_FLAG_RECURSE) == 0) doveadm(USERNAME): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x9f3de) [0x7f0e4a4b23de] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handl

Re: BUG: panic when using fs:posix as dict for acl_shared_dict

Marco Giunta wrote: > >> Hi, > >> I'm using Dovecot 2.2.33.2 on a RHEL 7, new installation. When I use > >> fs:posix as dict for acl_shared_dict, like in Dovecot wiki > >> (https://wiki.dovecot.org/SharedMailboxes/ClusterSetup), > >> doveadm-server crash

Re: BUG: panic when using fs:posix as dict for acl_shared_dict

=DEST_USERNAME lookup read write-seen doveadm(USERNAME): Panic: file dict-fs.c: line 127 (fs_dict_iterate_init): assertion failed: ((flags & DICT_ITERATE_FLAG_RECURSE) == 0) doveadm(USERNAME): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x9f3de) [0x7f0e4a4b23de] -> /usr/lib64/

Re: Panic: file smtp-client-connection.c: line 1142 (smtp_client_connection_established)

2019-11-18 20:17:51 lmtp(17274): Panic: file smtp-client-connection.c: line 1142 (smtp_client_connection_established): assertion failed: (!conn->connect_succeeded) 2019-11-18 20:17:51 lmtp(17274): Fatal: master: service(lmtp): child 17274 killed with signal 6 (core not dumped - ht

Panic: file smtp-client-connection.c: line 1142 (smtp_client_connection_established)

I'm using dovecot in a multi server setup. Two directors forward pop3, imap and smtp to backend dovecots with their central storage on NFS. Yesterday I stumbled upon these log lines: 2019-11-18 20:17:51 lmtp(17274): Info: Connect from 172.22.1.6 2019-11-18 20:17:51 lmtp(17274): Panic: file smtp

FTS indexer-worker Panic

Set up fts_xapian over the weekend and re-indexed. https://github.com/grosjo/fts-xapian Tried to search my INBOX and got: > dovecot: indexer-worker: Panic: file charset-iconv.c: line 83 (charset_to_utf8_try): assertion failed: (srcleft <= CHARSET_MAX_PENDING_BUF_SIZE) What could I possibl

Re: Panic: file smtp-client-connection.c: line 1212 (smtp_client_connection_established): assertion failed: (!conn->connect_succeeded)

On 11/10/2019 10:06, Hativ via dovecot wrote: Hello Aki, I have this problem just with 2.3.8, my self-compiled 2.3.3 works fine. I have previously tried to update from 2.3.3 to higher versions (possibly 2.3.5 or so), but always had this error, which is why I am always back to 2.3.3.

Re: Panic: file smtp-client-connection.c: line 1212 (smtp_client_connection_established): assertion failed: (!conn->connect_succeeded)

Hello Aki, I have this problem just with 2.3.8, my self-compiled 2.3.3 works fine. I have previously tried to update from 2.3.3 to higher versions (possibly 2.3.5 or so), but always had this error, which is why I am always back to 2.3.3. Configuration is exactly the same. Here my output from

Re: Panic: file smtp-client-connection.c: line 1212 (smtp_client_connection_established): assertion failed: (!conn->connect_succeeded)

On 11.10.2019 10.50, Hativ via dovecot wrote: > Hello, > > after migrating from self-compiled Dovecot 2.3.3 to Dovecot 2.3.8 from > the repository (Ubuntu 18.04 LTS "Bionic" packages) I have issues with > the submission service. If I send an email, it will not be forwarded > and I get the

Panic: file smtp-client-connection.c: line 1212 (smtp_client_connection_established): assertion failed: (!conn->connect_succeeded)

v2 dovecot: submission(ha...@example.com)<15819>: Panic: file smtp-client-connection.c: line 1212 (smtp_client_connection_established): assertion failed: (!conn->connect_succeeded) Oct 11 09:29:01 srv2 dovecot: submission(ha...@example.com)<15819>: Error: Raw backtrace: /usr/lib/dovecot

Panic at "doveadm backup" (mailbox_symlink_exists): assertion failed: (ret > 0)

Hi. I try to sync from a dovecot server to another server via the following command. doveadm -D -o mail_fsync=never -o imapc_user=i...@domain.com -o imapc_password='PASS' backup -R -u i...@domain.com imapc: After some short runtime I get the following panic. ``` dsync(i...@domain.com): Panic

Re: Panic: Module context expire_mail_user_module missing (Debian 10)

Am 2019-08-02 11:05, schrieb Thomas Krause: Thomas, please keep the discussion on list. There is zero need to copy send any list discussion to my personal address. # diff dovecot.conf dovecot.conf-ok 5c5 < mail_plugins = quota mailbox_alias acl zlib expire --- mail_plugins = quota

Re: Panic: Module context expire_mail_user_module missing (Debian 10)

-partition and /etc/dovecot from the old to the new server. Dovecot started with 2 warnings. When trying to fetch mails via pop3 the server crashes: Aug 1 16:56:47 mail19 dovecot: pop3-login: Login: user=, rip=::1, mpid=22394, session= Aug 1 16:56:47 mail19 dovecot: pop3(testuser)<22394>:

Re: Panic: Module context expire_mail_user_module missing (Debian 10)

. Dovecot started with 2 warnings. When trying to fetch mails via pop3 the server crashes: Aug 1 16:56:47 mail19 dovecot: pop3-login: Login: user=, rip=::1, mpid=22394, session= Aug 1 16:56:47 mail19 dovecot: pop3(testuser)<22394>: Panic: Module context expire_mail_user_module missing D

Re: Panic: Module context expire_mail_user_module missing (Debian 10)

via pop3 the server crashes: Aug 1 16:56:47 mail19 dovecot: pop3-login: Login: user=, rip=::1, mpid=22394, session= Aug 1 16:56:47 mail19 dovecot: pop3(testuser)<22394>: Panic: Module context expire_mail_user_module missing Disable the expire plugin in your configuration. [ ... ]

Panic: Module context expire_mail_user_module missing (Debian 10)

dovecot: pop3-login: Login: user=, rip=::1, mpid=22394, session= Aug 1 16:56:47 mail19 dovecot: pop3(testuser)<22394>: Panic: Module context expire_mail_user_module missing Aug 1 16:56:47 mail19 dovecot: pop3(testuser)<22394>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.s

Panic alert

Hi, I am getting a panic alert when sending an email in my box.  Below is the backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x9f3de) [0x7fa90b5543de] -> /usr/lib64/dovecot/libdovecot.so.0(+0x9f4be) [0x7fa90b5544be] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fa90b4e577c] -&

Re: [ext] Re: Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000)

* Aki Tuomi via dovecot : > Known issue when folder cache is too big. Try rm -rf dovecot.index.cache > for the folder. -rw--- 1 mail mail 1746959712 May 24 14:37 dovecot.index.cache yes, it is quite big :) 1.746.959.712 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk

Re: Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000)

ailbox INBOX header X-Spam Yes SAVEDBEFORE 2019-05-23 > > doveadm(restore@backup.invalid): Panic: file mail-index-util.c: line 10 > (mail_index_uint32_to_offset): assertion failed: (offset < 0x4000) > doveadm(restore@backup.invalid): Error: Raw backtrace: > /usr/lib/do

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@backup.invalid mdbox:/home/copymail2/mdbox '' mailbox INBOX header X-Spam Yes SAVEDBEFORE 2019-05-23 doveadm(restore@backup.invalid): Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed

Re: v2.2.27 Panic: file rfc822-parser.h: line 23 (rfc822_parser_deinit): assertion failed: (ctx->data <= ctx->end)

Hi Hendrik, Hendrik Boom via dovecot wrote on 29/3/19 4:03 am: > On Wed, Mar 27, 2019 at 10:25:02AM +1100, Jason Lewis via dovecot wrote: >> Hi Aki, >> >> debian jessie backports has been moved to archive.debian.org and >> initially I was unable to install dovecot-dbg because of that. But I've >>

Re: v2.2.27 Panic: file rfc822-parser.h: line 23 (rfc822_parser_deinit): assertion failed: (ctx->data <= ctx->end)

On Wed, Mar 27, 2019 at 10:25:02AM +1100, Jason Lewis via dovecot wrote: > Hi Aki, > > debian jessie backports has been moved to archive.debian.org and > initially I was unable to install dovecot-dbg because of that. But I've > managed to resolve that issue now. Just curious -- what deb line did

Re: Panic: file mail-transaction-log-file.c: line 105 (mail_transaction_log_file_free): assertion failed: (!file->locked)

On 28 Mar 2019, at 10.15, Arkadiusz Miśkiewicz wrote: > > error = 0x55e3e2b40ac0 "Fixed index file > /var/mail/piast_efaktury/dovecot.index: log_file_seq 13 -> 15", > nodiskspace = true, This was one of the things I was first wondering, but I'm not sure why it's not logging an error. Anyway,

Re: v2.2.27 Panic: file rfc822-parser.h: line 23 (rfc822_parser_deinit): assertion failed: (ctx->data <= ctx->end)

> On 28 Mar 2019, at 1.08, Jason Lewis via dovecot wrote: > > Thanks Timo. > > Given the age of these dovecot packages, and this being on debian > oldstable, what should we do next? I'm inclined to just delete the email > in question and move on. > https://repo.dovecot.org/

Re: v2.2.27 Panic: file rfc822-parser.h: line 23 (rfc822_parser_deinit): assertion failed: (ctx->data <= ctx->end)

_plugin.so: >> undefined symbol: lucene_index_iter_deinit (this is usually intentional, >> so just ignore this message) >> Debug: Module loaded: >> /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so >> Debug: Skipping module doveadm_mail_crypt_plugin, because

Re: v2.2.27 Panic: file rfc822-parser.h: line 23 (rfc822_parser_deinit): assertion failed: (ctx->data <= ctx->end)

What's non-trivial about apt-get install dovecot-dbg? Aki On 26.3.2019 5.38, Jason Lewis via dovecot wrote: > After some investigation, it turns out it is non trivial to install > dovecot-dbg on debian jessie. > > Sorry I can't investigate further. > > Jason > > Aki Tuomi wrote on 25/3/19 6:12

Re: Panic: file mail-transaction-log-file.c: line 105 (mail_transaction_log_file_free): assertion failed: (!file->locked)

On 28/03/2019 09:36, Timo Sirainen wrote: > On 28 Mar 2019, at 10.15, Arkadiusz Miśkiewicz > wrote: >> >>  error = 0x55e3e2b40ac0 "Fixed index file >> /var/mail/piast_efaktury/dovecot.index: log_file_seq 13 -> 15", >>  nodiskspace = true, > > This was one of the things I

Re: Panic: file mail-transaction-log-file.c: line 105 (mail_transaction_log_file_free): assertion failed: (!file->locked)

On 27/03/2019 16:12, Timo Sirainen wrote: > On 27 Mar 2019, at 14.58, Timo Sirainen via dovecot > wrote: >> >>> dovecot isn't able to auto fix the indexes and manual deletion is >>> required in all such cases >> >> So if it keeps repeating, it's very strange. Could you

Panic: file mail-transaction-log-file.c: line 105 (mail_transaction_log_file_free): assertion failed: (!file->locked)

g_file_seq 13 -> 15 > Mar 27 11:13:50 mbox dovecot[22370]: lmtp(piast_efaktury): pid=<24428> > session=, Panic: file mail-transaction-log-file.c: > line 105 (mail_transaction_log_file_free): assertion failed: (!file->locked) > Mar 27 11:13:50 mbox dovecot[22370]: lmtp(piast_efaktu

Re: v2.2.27 Panic: file rfc822-parser.h: line 23 (rfc822_parser_deinit): assertion failed: (ctx->data <= ctx->end)

On 27 Mar 2019, at 1.25, Jason Lewis via dovecot wrote: > > Hi Aki, > > debian jessie backports has been moved to archive.debian.org and > initially I was unable to install dovecot-dbg because of that. But I've > managed to resolve that issue now. > > This was the command I ran: > doveadm -D

Re: v2.2.27 Panic: file rfc822-parser.h: line 23 (rfc822_parser_deinit): assertion failed: (ctx->data <= ctx->end)

Hi Aki, debian jessie backports has been moved to archive.debian.org and initially I was unable to install dovecot-dbg because of that. But I've managed to resolve that issue now. This was the command I ran: doveadm -D -f flow fetch imap.envelope mailbox crm-spam.2008.g Backtrace follows.

Re: Panic: file mail-transaction-log-file.c: line 105 (mail_transaction_log_file_free): assertion failed: (!file->locked)

On 27 Mar 2019, at 14.58, Timo Sirainen via dovecot wrote: > >> dovecot isn't able to auto fix the indexes and manual deletion is >> required in all such cases > > So if it keeps repeating, it's very strange. Could you send me such broken > dovecot.index and dovecot.index.log files (without

Re: v2.2.27 Panic: file rfc822-parser.h: line 23 (rfc822_parser_deinit): assertion failed: (ctx->data <= ctx->end)

Thanks Timo. Given the age of these dovecot packages, and this being on debian oldstable, what should we do next? I'm inclined to just delete the email in question and move on. Jason Timo Sirainen wrote on 28/3/19 12:16 am: > On 27 Mar 2019, at 1.25, Jason Lewis via dovecot wrote: >> >> Hi

Re: Panic: file mail-transaction-log-file.c: line 105 (mail_transaction_log_file_free): assertion failed: (!file->locked)

already has sequence 15. I could maybe believe such a bug with long-running IMAP connections, but this is LMTP. And it's supposed to be fixing the problem here.. >> Mar 27 11:13:50 mbox dovecot[22370]: lmtp(piast_efaktury): pid=<24428> >> session=, Panic: file mail-transact

Re: v2.2.27 Panic: file rfc822-parser.h: line 23 (rfc822_parser_deinit): assertion failed: (ctx->data <= ctx->end)

ssage) > doveadm(jason): Debug: Effective uid=1000, gid=1000, home=/home/jason > doveadm(jason): Debug: Namespace inbox: type=private, prefix=, sep=, > inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir > doveadm(jason): Debug: maildir++: root=/home/jason/Maildir

Panic

Dovecot-2.3.5, FreeBSD-12 (amd64), I will wait to see coredumps after setting up things to allow it. Mar 24 20:56:08 imap(john@crownkenya.com)<82746>: Panic: file mempool-system.c: line 137 (pool_system_realloc): assertion failed: (old_size == (size_t)-1 || mem == NULL || ol

v2.2.27 Panic: file rfc822-parser.h: line 23 (rfc822_parser_deinit): assertion failed: (ctx->data <= ctx->end)

Hi, I've been having an issue with the indexer giving me errors on mailbox in dovecot. I managed to narrow it down to a specific email in that mailbox. Various dovecot functions have issues with this email. The email itself is just spam. I can email it to you if you want to analyse it. I did

Re: 2.3.3: Panic: file ostream-zlib.c: line 37 (o_stream_zlib_close): assertion failed

Op 02/10/2018 om 11:26 schreef Tom Sommer: I see this in my logs after 2.3.3: using zlib plugin, ofc. Oct 02 10:01:39 imap(u...@example.com)<50643>: Panic: file ostream-zlib.c: line 37 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished ||

Re: Panic…

? On Thu, Dec 13, 2018 at 07:42, Timo Sirainen <mailto:t...@iki.fi>> wrote: On 13 Dec 2018, at 7.31, SH Development wrote: > > 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_

Re: panic when using dovecot master account

On 2019-01-20 12:38, Stephan Bosch wrote: Op 12/01/2019 om 20:31 schreef André Rodier via dovecot: On Sat, 2019-01-12 at 19:11 +, André Rodier via dovecot wrote: Happy new year, everyone! Aki, I have been able to reproduce the problem, and this time, with the packages from Debian stable.

Re: panic when using dovecot master account

Op 12/01/2019 om 20:31 schreef André Rodier via dovecot: On Sat, 2019-01-12 at 19:11 +, André Rodier via dovecot wrote: Happy new year, everyone! Aki, I have been able to reproduce the problem, and this time, with the packages from Debian stable. So you were right, this had nothing to do

Re: panic when using dovecot master account

), 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: > > > > > > > >

Re: panic when using dovecot master account

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->synci

Re: Re: Panic…

Btw, what sizes are we talking about here? I assume it would be really huuuge? What's the max size of the .cache file and how many mails might create this size? Kai

Re: Panic…

t; wrote: >> On 13 Dec 2018, at 7.31, SH Development >> wrote: >> > >> > 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)

Re: Panic…

>> need to do? >> >> Panic: file mail-index-util.c: line 37 (mail_index_uint32_to_offset): >> assertion failed: (offset < 0x4000) > > Your dovecot.index.cache file has grown too huge. The only solution now is to > delete it, and perhaps try to

Re: Panic…

On 13 Dec 2018, at 7.31, SH Development wrote: > > 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 < 0x4000) Your dovecot

Panic…

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 < 0x4000) Dec 12 23:29:44 mail dovecot: imap(j...@stariontech.com): Error: Raw backtrace: /usr/li

Dovecot 2.3.4 crashing on Solaris 10 - "Panic: output stream is missing error handling"

~~ # Hostname: merlin service pop3-login { inet_listener pop3 { port = 1110 } } submission_max_mail_size = 0 doveconf: Panic: output stream is missing error handling doveconf: Error: Raw backtrace: 0xff01b3a8 -> 0xff063b04 -> 0x1673c -> 0x1797c -> 0x14478 Abort (core dumped) Th

Re: Panic: file dsync-brain-mailbox-tree.c: line 448: unreached

:4191 This ran successful when I set it up and didn't look at it anymore. Recently I noticed errors: dsync-local(administration): Panic: file dsync-mailbox-tree-sync.c: line 1253 (sync_create_mailboxes): assertion failed: (node->ns == other_node->ns) dsync-local(administration): Erro

Panic: file dsync-brain-mailbox-tree.c: line 448: unreached

Hi all, To backup our imap folders I've a cronjob running in the night: /usr/bin/doveadm -o stats_writer_socket_path= backup -R -A -N tcp:xxx.yyy.zzz:4191 This ran successful when I set it up and didn't look at it anymore. Recently I noticed errors: dsync-local(administration): Panic: file

Re: panic when using dovecot master account

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]:

Re: panic when using dovecot master account

> > 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

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

Re: Panic: file istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion failed: (ret != -2)

On 30 Oct 2018, at 16.25, Peter Nabbefeld wrote: > Oct 26 07:41:20 lda(peter.nabbef...@gmx.de)<24607>: > Panic: file istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion > failed: (ret != -2) > > $ dovecot -n > # 2.3.3 (dcead646b): /etc/dovecot/dovecot

Re: Panic: file istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion failed: (ret != -2)

;~/.getmail/log")     max_bytes_per_session : 0     max_message_size : 0     max_messages_per_session : 0     message_log : ~/.getmail/log     message_log_syslog : False     message_log_verbose : False     read_all : True     received : False     verbose : 1 dovecot.log: Oct 26 07:41:20 lda(p

Re: Panic: file istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion failed: (ret != -2)

Op 28-10-2018 om 23:28 schreef Peter Nabbefeld: Hello, cannot fetch mails from an IMAP folder because of the error in the subject - fetching always stops with SIGABRT. Could anybody help me, please? We need more information than that: - Your configuration and version, which is privided

Panic: file istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion failed: (ret != -2)

Hello, cannot fetch mails from an IMAP folder because of the error in the subject - fetching always stops with SIGABRT. Could anybody help me, please? Kind regards Peter

Re: 2.3.3: Panic: file ostream-zlib.c: line 37 (o_stream_zlib_close): assertion failed

On 2 Oct 2018, at 12.26, Tom Sommer wrote: > > I see this in my logs after 2.3.3: > > using zlib plugin, ofc. > > Oct 02 10:01:39 imap(u...@example.com)<50643>: Panic: file > ostream-zlib.c: line 37 (o_stream_zlib_close): assertion failed: > (zstrea

2.3.3: Panic: file ostream-zlib.c: line 37 (o_stream_zlib_close): assertion failed

I see this in my logs after 2.3.3: using zlib plugin, ofc. Oct 02 10:01:39 imap(u...@example.com)<50643>: Panic: file ostream-zlib.c: line 37 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished || zstream->ostream.ostream.stream_errno != 0

Re: dovecot (2.2.13) panic on imap-login from iphone se

ovecot.org Subject: Re: dovecot (2.2.13) panic on imap-login from iphone se here is our config: (doveconf -n) # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.6.11-gentoo x86_64 Gentoo Base System release 2.2 auth_cache_size = 10 M auth_mechanisms = plain login default_client_li

Re: dovecot (2.2.13) panic on imap-login from iphone se

> Date: 18/09/2018 19:13 (GMT+02:00) > To: Aki Tuomi > Subject: Re: dovecot (2.2.13) panic on imap-login from iphone se > > > Sorry. I think upgrade is not possible because it is a very outdated > gentoo installation and im not abe to compile without compiling the > who

Re: dovecot (2.2.13) panic on imap-login from iphone se

ot (2.2.13) panic on imap-login from iphone se Sorry. I think upgrade is not possible because it is a very outdated gentoo installation and im not abe to compile without compiling the whole source stack of glibc and all other dependencies. It is planned to replace the server in the next 8 weeks

Re: dovecot (2.2.13) panic on imap-login from iphone se

Can you upgrade to 2.2.36 or 2.3.2.1 and reproduce this issue? 2.2.13 is quite old. ---Aki TuomiDovecot oy Original message From: "Andre Hoepner - i.based: Systemhaus GmbH + Co. KG" Date: 18/09/2018 16:17 (GMT+02:00) To: dovecot@dovecot.org Subject: dovecot (2.2

dovecot (2.2.13) panic on imap-login from iphone se

, but if we use the iphone se we got this error. Are there any known issues with this combination? Thanks for your help. best regardings Andre Hoepner ---8< # HOST = hostname of the system; USER = username that gets this error Sep 18 12:46:02 HOST dovecot: imap(USER): Panic: file mailbox-lis

Re: lmtp Panic Buffer write out of range

Op 23-8-2018 om 8:16 schreef Gabriele Nencioni: On 08/22/2018 04:03 PM, Stephan Bosch wrote: Op 21-8-2018 om 14:57 schreef Gabriele Nencioni: Hi all, as described here: https://www.dovecot.org/pipermail/dovecot/2018-July/112173.html we are experiencing the same error on dovecot version

Re: lmtp Panic Buffer write out of range

On 08/22/2018 04:03 PM, Stephan Bosch wrote: > Op 21-8-2018 om 14:57 schreef Gabriele Nencioni: >> Hi all, >> as described here: >> https://www.dovecot.org/pipermail/dovecot/2018-July/112173.html >> >> we are experiencing the same error on dovecot version 2.3.2.1 >> while it never occurs on an old

Re: lmtp Panic Buffer write out of range

://dovecot.org/list/dovecot/2018-July/112167.html That one is fixed pending release. Regards, Stephan. It followings the error logs: On an upgraded dovecot backend: Aug 21 12:03:51 backend20 dovecot: lmtp(te...@internalinboundcm.eu): Panic: Buffer write out of range (789 + 18446744073709551606) /var

lmtp Panic Buffer write out of range

dovecot: lmtp(te...@internalinboundcm.eu): Panic: Buffer write out of range (789 + 18446744073709551606) /var/log/dovecot_lmtp_20180821.12.log-Aug 21 12:03:51 monti-backend20 dovecot: lmtp(te...@internalinboundcm.eu): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xcb851) [0x7f78e6f0a851

Re: dovecot Panic: file mail-index-sync-update.c: line 1013

This has been fixed on later release. You are using very old version. ---Aki TuomiDovecot oy Original message From: Eugen I Date: 08/08/2018 15:12 (GMT+02:00) To: dovecot@dovecot.org Subject: dovecot Panic: file mail-index-sync-update.c: line 1013 An email came to several

dovecot Panic: file mail-index-sync-update.c: line 1013

An email came to several users but one user didn't receive it and we got 'Mail delivery failed' message. As I see from the log below, there were broken index file. Then dovecot repaired that index and we got the error: Panic: file mail-index-sync-update.c: line 1013 (mail_index_sync_map

Aw: Re: Re: Re: Panic: Leaked view for index - virtual mailbox

Ok. Here it is! (Attachment!!)   Jakob   Gesendet: Donnerstag, 26. Juli 2018 um 12:12 Uhr Von: "Aki Tuomi" An: wertsto...@nurfuerspam.de Betreff: Re: Aw: Re: Re: Panic: Leaked view for index - virtual mailbox I tried with 32k messages, and I wasn't able to provoke it to fail. C

Aw: Re: Re: Re: Panic: Leaked view for index - virtual mailbox

Ok. Here it is! (Attachment!!)   Jakob   Gesendet: Donnerstag, 26. Juli 2018 um 12:12 Uhr Von: "Aki Tuomi" An: wertsto...@nurfuerspam.de Betreff: Re: Aw: Re: Re: Panic: Leaked view for index - virtual mailbox I tried with 32k messages, and I wasn't able to provoke it to fail. C

Re: Aw: Re: Re: Panic: Leaked view for index - virtual mailbox

t; -INBOX/Junk > -INBOX/Junk/* > -INBOX/SYSTEM > -INBOX/SYSTEM/* >  all >   >   > When i try to open a Mailbox from them in Thunderbird i get this error > in my logs (for example i opened Alle): > Jul 26 11:33:44 aldebaran dovecot[14873]: imap-login: Login: > use

Aw: Re: Re: Panic: Leaked view for index - virtual mailbox

LAIN, rip=92.60.9.18, lip=192.168.0.14, mpid=17347, TLS, session= Jul 26 11:33:45 aldebaran dovecot[14873]: imap(jakob)<17347>: Panic: file mail-index.c: line 752 (mail_index_close_nonopened): assertion failed: (index->views == NULL) Jul 26 11:33:45 aldebaran dovecot[14873]: imap(jakob)<17

Re: Aw: Re: Panic: Leaked view for index - virtual mailbox

es, there is this Synoptic/INBOX/Archives Mailbox. This is > for a special Mailclient "K9Mail" (on Android). Because i used there > only the Synoptic-Namespace. And K9Mail created itself an own > Archive-Folder, if there is no one below INBOX. With this solution, > K9Mail sho

Aw: Re: Panic: Leaked view for index - virtual mailbox

K9Mail can handle different Identities (for Alias-Emailadresses) for the same Account, but only one Namespace... Jakob   Gesendet: Donnerstag, 26. Juli 2018 um 07:54 Uhr Von: "Aki Tuomi" An: "Jakobus Schürz" , dovecot@dovecot.org Betreff: Re: Panic: Leaked view for index -

Re: Panic: Leaked view for index - virtual mailbox

om git! >>> >>> /usr/local/sbin/dovecot --version >>> 2.3.2.1 (0719df592) >>> >>> jakob >>> >>> >>> Am 25.07.2018 um 08:30 schrieb Aki Tuomi: >>>> And can you provide dovecot --version too, please. >>>> >>>> Aki

Re: Panic: Leaked view for index - virtual mailbox

Aki Tuomi: Try running gdb again with corrected path for imap binary --- Aki Tuomi Dovecot oy Original message ---- From: Jakobus Schürz Date: 25/07/2018 10:46 (GMT+02:00) To: dovecot@dovecot.org Subject: Re: Panic: Leaked view for index - virtual mailbox Hi Aki! The config is

Re: Panic: Leaked view for index - virtual mailbox

  Hi Aki! Sorry. Here is the right output.   # gdb /usr/local/libexec/dovecot/imap /var/core/24491 GNU gdb (Debian 8.1-3) 8.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There

Re: Panic: Leaked view for index - virtual mailbox

Try running gdb again with corrected path for imap binary ---Aki TuomiDovecot oy Original message From: Jakobus Schürz Date: 25/07/2018 10:46 (GMT+02:00) To: dovecot@dovecot.org Subject: Re: Panic: Leaked view for index - virtual mailbox Hi Aki! The config

Re: Panic: Leaked view for index - virtual mailbox

i On 25 July 2018 at 05:18 Jakobus Schürz wrote: 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>: Panic: Leaked view for index

Re: 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. > >>> > >

Re: Panic: Leaked view for index - virtual mailbox

release is this? Aki On 25 July 2018 at 05:18 Jakobus Schürz wrote: 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>:

<    1   2   3   4   5   6   7   8   9   10   >