Re: replicator: Panic: data stack: Out of memory when allocating 275GB

On 10/15/24 9:00 AM, Aki Tuomi wrote: Can you try if https://github.com/dovecot/core/ commit/9302c5746770f20e0c41da4e3e8a081cd8f7cec0 fixes your issue? I use version 2.3.21.1 and it looks like this patch alread

Re: replicator: Panic: data stack: Out of memory when allocating 275GB

than 10Gb. Whole /var/mail dir is 1.8Tb.   With vsz_limit it crashes much earlier, this log with 275GB produced by setting vsz_limit = 0   Server has 192GB of RAM, can it be some bug?   Oct 14 15:51:59 mailserver dovecot[826177]: replicator: Panic: data

Re: replicator: Panic: data stack: Out of memory when allocating 275GB

15.10.2024 02:04, Sergej Pupykin via dovecot пишет: Hello, I found similar reports in this ML with values less than mine but was not able to find the solution. There is no solution. I checked size of all dovecot.* files in /var/mail and it is less than 10Gb. Whole /var/mail dir is 1.8Tb.

replicator: Panic: data stack: Out of memory when allocating 275GB

setting vsz_limit = 0 Server has 192GB of RAM, can it be some bug? Oct 14 15:51:59 mailserver dovecot[826177]: replicator: Panic: data stack: Out of memory when allocating 274877906984 bytes Oct 14 15:51:59 mailserver dovecot[826177]: replicator: Error: Raw backtrace: /usr/lib/dovecot

Re: Panic with FTS_BACKEND_FLAG_TOKENIZED_INPUT and virtual mailboxes: file index-search-result.c: line 132

Just to be complete here is a second backtrace with a similar error (if it needs to be fixed at multiple places): ``` Panic: file index-search-result.c: line 174 (index_search_result_update_appends): assertion failed: (result->search_args->args == &search_arg) Error: Raw backtrace

Panic with FTS_BACKEND_FLAG_TOKENIZED_INPUT and virtual mailboxes: file index-search-result.c: line 132

Originally posted and debugged here: https://github.com/slusarz/dovecot-fts-flatcurve/issues/66 I have to following panic with fts flatcurve enabled: ``` Panic: file index-search-result.c: line 132 (index_search_result_update_flags): assertion failed: (result->search_args->args == &

"panic ... assertion failed" with virtual and flatcurve fts together

Hi, I'm getting the following error: $ doveadm fetch 'mailbox storageid' guid '1721115116.M995635P1988.exoco.falsifian.org,S=28763,W=29300' Error: net_connect_unix(/var/dovecot/stats-writer) failed: Permission denied doveadm(falsifian): Panic: file index-

Re: dovecot panic

> On 15/03/2024 10:53 EET Michael Grant via dovecot wrote: > > > I'm running dovecot 2.3.19.1 on debian stable. I just started seeing a > slew of these in my log: > > Mar 14 10:02:38 strange.networkguild.org dovecot[865654]: > imap(mgrant)<1939553>:

dovecot panic

I'm running dovecot 2.3.19.1 on debian stable.  I just started seeing a slew of these in my log: Mar 14 10:02:38 strange.networkguild.org dovecot[865654]: imap (mgrant)<1939553>: Panic: file istream-header-filter.c: line 663 (i_stream_header_filter_snapshot_free): assertion failed

Re: auth: Panic: file oauth2-request.c assertion failed

produces also "lmtp" and "quota-status" delays: ... Sep 5 07:43:18 dcot-server-1 dovecot: auth: Panic: file oauth2-request.c: line 201 (oauth2_request_start): assertion failed: (oauth2_valid_token(input->token)) Sep 5 07:43:18 dcot-server-1 dovecot: auth: Error: Raw back

Panic: file acl-backend-vfile.c: line 123 on access from Nextcloud Imap-Client

Hello, with activated imap_aci i get the following error: Jun 15 08:40:02 konsrvdata2 dovecot: imap(xp8it)<439797>: Panic: file acl-backend-vfile.c: line 123 (acl_backend_vfile_get_local_dir): assertion failed: (list == ns->list) Jun 15 08:40:02 konsrvdata2 dovecot: imap(xp8it)<439

Re: dovecot crash with Panic: file istream-header-filter.c: line 663

>>> After the above, it's no longer crashing, and my email client's "pending >>> operations" have >>> cleared. >> >> Does your server use ECC memory and if so, are there any errors logged >> (bitflip, ...)? >> >> Best regards, >> Gerald > > I don't have the logs from that time them nor do I

Re: dovecot crash with Panic: file istream-header-filter.c: line 663

On Mon, Mar 13, 2023 at 04:33:38PM +0100, Gerald Galster wrote: > > After the above, it's no longer crashing, and my email client's "pending > > operations" have > > cleared. > > Does your server use ECC memory and if so, are there any errors logged > (bitflip, ...)? > > Best regards, > Gerald

Re: dovecot crash with Panic: file istream-header-filter.c: line 663

> After the above, it's no longer crashing, and my email client's "pending > operations" have > cleared. Does your server use ECC memory and if so, are there any errors logged (bitflip, ...)? Best regards, Gerald

Re: dovecot crash with Panic: file istream-header-filter.c: line 663

On Mon, Mar 13, 2023 at 11:01:35AM +0200, Timo Sirainen wrote: > On 12. Mar 2023, at 20.17, Patrick Mansfield wrote: > > > > Mar 12 10:32:27 goffin dovecot[8269]: imap(patman)<8452>: > > Panic: file istream-header-filter.c: line 663 > > (i_stream_header_filter

Re: dovecot crash with Panic: file istream-header-filter.c: line 663

On 12. Mar 2023, at 20.17, Patrick Mansfield wrote: > > Mar 12 10:32:27 goffin dovecot[8269]: imap(patman)<8452>: > Panic: file istream-header-filter.c: line 663 > (i_stream_header_filter_snapshot_free): assertion failed: > (snapshot->mstream->snapshot_pending) T

Re: dovecot crash with Panic: file istream-header-filter.c: line 663

On Sun, Mar 12, 2023 at 11:17:43AM -0700, Patrick Mansfield wrote: > > email client is fairemail version 1.2042a on android, but an older version > had the same > problem. > > I mainly use fairemail to read emails on my phone, and that is working fine > but I noticed > that deleted emails were

dovecot crash with Panic: file istream-header-filter.c: line 663

/libexec/dovecot/auth" hostname=192.168.1.4 addr=192.168.1.4 terminal=dovecot res=success' Mar 12 10:32:26 goffin dovecot[8269]: imap-login: Login: user=, method=PLAIN, rip=192.168.1.4, lip=192.168.1.1, mpid=8479, TLS, session= Mar 12 10:32:27 goffin dovecot[82

Re: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes

and my new >> (2.3.20, Alpine Linux, Docker, apk package). When I turn on replication it >> works, but, after a while I see: >> >> Jan 06 00:50:31 replicator: Panic: data stack: Out of memory when allocating >> 268435496 bytes >> Jan 06 00:50:32 replicator: Fata

Re: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes

On January 6, 2023 3:56:39 AM GMT+02:00, Gerben Wierda mailto:gerben.wie...@rna.nl>> wrote: One step further in my quest to create a replacement mail server. I now have my old mail server (2.3.19.1, macOS + MacPorts) and my new (2.3.20, Alpine Linux, Docker, apk package). When

Re: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes

@open-xchange.com>> wrote: On January 6, 2023 3:56:39 AM GMT+02:00, Gerben Wierda mailto:gerben.wie...@rna.nl>> wrote: One step further in my quest to create a replacement mail server. I now have my old mail server (2.3.19.1, macOS + MacPorts) and my new (2.3.20, Alpine Linux, Docke

Re: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes

LECT home, uid, gid FROM email_users WHERE username = '%u' and > password <> 'alias' and status = True and destination = '%u' > > #iterate_query = SELECT user, password FROM email_users WHERE username = '%u' > and password <> 'a

Re: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes

Gerben Wierda mailto:gerben.wie...@rna.nl>> wrote: One step further in my quest to create a replacement mail server. I now have my old mail server (2.3.19.1, macOS + MacPorts) and my new (2.3.20, Alpine Linux, Docker, apk package). When I turn on replication it works, but, after a whil

Re: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes

and my new >> (2.3.20, Alpine Linux, Docker, apk package). When I turn on replication it >> works, but, after a while I see: >> >> Jan 06 00:50:31 replicator: Panic: data stack: Out of memory when allocating >> 268435496 bytes >> Jan 06 00:50:32 replicator: Fata

Re: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes

On January 6, 2023 12:21:45 PM GMT+02:00, justina colmena ~biz wrote: >On Thursday, January 5, 2023 10:53:13 PM AKST Aki Tuomi wrote: >> On January 6, 2023 3:56:39 AM GMT+02:00, Gerben Wierda > wrote: >> >Jan 06 00:50:31 replicator: Panic: data stack: Out of memor

Re: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes

On Thursday, January 5, 2023 10:53:13 PM AKST Aki Tuomi wrote: > On January 6, 2023 3:56:39 AM GMT+02:00, Gerben Wierda wrote: > >Jan 06 00:50:31 replicator: Panic: data stack: Out of memory when > >allocating 268435496 bytes Jan 06 00:50:32 replicator: Fatal: master: > ... &g

Re: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes

t works, but, >after a while I see: > >Jan 06 00:50:31 replicator: Panic: data stack: Out of memory when allocating >268435496 bytes >Jan 06 00:50:32 replicator: Fatal: master: service(replicator): child 133 >killed with signal 6 (core dumped) >Jan 06 00:50:32 lmtp(pid 195 user s

replicator: Panic: data stack: Out of memory when allocating 268435496 bytes

One step further in my quest to create a replacement mail server. I now have my old mail server (2.3.19.1, macOS + MacPorts) and my new (2.3.20, Alpine Linux, Docker, apk package). When I turn on replication it works, but, after a while I see: Jan 06 00:50:31 replicator: Panic: data stack: Out

auth: Panic: file oauth2-request.c assertion failed

n the future. Important to mention is that currently no users are stored in Azure B2C. I only prepared the hole configuration and authentiucation falls back to mysql database. Now sometimes I get the error below in my logs (not permanently): ... Dec 7 11:36:49 relay-out1 dovecot: auth: Panic:

lmtp with sieve editheader Panic: file edit-mail.c: line 1809 (merge_from_parent): assertion failed

Hi, I have experienced a crash in lmtp delivery on some mails when sieve editheader plugin is used. The first one was an "analytics mail" from azure exchange. I stripped down the mail to the relevant parts that trigger this error. log message: lmtp(johnd)<27019>: Error: Raw backtrace: /usr/lib/

oauth2 + postgres = Panic: file http-client.c: line 646 (http_client_context_close)

#x27;/usr/local/libexec/dovecot/auth' (x86_64). (lldb) run Process 54354 launched: '/usr/local/libexec/dovecot/auth' (x86_64) Error: stats: open(old-stats-user) failed: No such file or directory Panic: file http-client.c: line 646 (http_client_context_close): assertion failed: (cctx-

Re: Panic: file mail-index-transaction-finish.c: line 185

Hi list I have weird issue with my Dovecot 2.3.17.1 (476cd46418) When deleting a certain amount of messages from my INBOX via my MUA (Evolution) all over sudden dovecot starts to panic Panic: file mail-index-transaction-finish.c: line 185 (mail_index_transaction_get_uid): assertion failed: (s

Re: Panic: file mail-index-transaction-finish.c: line 185

2.3.17.1 (476cd46418) When deleting a certain amount of messages from my INBOX via my MUA (Evolution) all over sudden dovecot starts to panic Panic: file mail-index-transaction-finish.c: line 185 (mail_index_transaction_get_uid): assertion failed: (seq <= t->view- map->hdr.mes

Re: Panic: file mail-index-transaction-finish.c: line 185

of messages from my INBOX via my MUA (Evolution) all over sudden dovecot starts to panic Panic: file mail-index-transaction-finish.c: line 185 (mail_index_transaction_get_uid): assertion failed: (seq <= t->view- map->hdr.messages_count) Thanks! Aki Arkadiusz, is it possible for you

Re: Panic: file mail-index-transaction-finish.c: line 185

gt;>>> >>>>>>>> On 29/12/2021 11:20 tobiswo...@gmail.com wrote: >>>>>>>> >>>>>>>> Hi list >>>>>>>> >>>>>>>> I have weird issue with my Dovecot 2.3.17.1 (476cd46418)

Re: Panic: file mail-index-transaction-finish.c: line 185

Aki Tuomi wrote: On 29/12/2021 11:20 tobiswo...@gmail.com wrote: Hi list I have weird issue with my Dovecot 2.3.17.1 (476cd46418) When deleting a certain amount of messages from my INBOX via my MUA (Evolution) all over sudden dovecot starts to panic Panic: file mail-index-transaction-fini

Re: Panic: file mail-index-transaction-finish.c: line 185

> >>> > >>> On 29.12.2021 10:26, Aki Tuomi wrote: > >>>> > >>>>> On 29/12/2021 11:20 tobiswo...@gmail.com wrote: > >>>>> > >>>>>Hi list > >>>>> > >>>>> I have weir

Re: Panic: file mail-index-transaction-finish.c: line 185

> >>>>> On 29/12/2021 11:20 tobiswo...@gmail.com wrote: >>>>> >>>>>Hi list >>>>> >>>>> I have weird issue with my Dovecot 2.3.17.1 (476cd46418) >>>>> When deleting a certain amount of messages f

Re: Panic: file mail-index-transaction-finish.c: line 185

messages from my INBOX via my MUA (Evolution) all over sudden dovecot starts to panic Panic: file mail-index-transaction-finish.c: line 185 (mail_index_transaction_get_uid): assertion failed: (seq <= t->view- map->hdr.messages_count) imap(REDACTED)<24075>: Error: Raw backtrace: /us

Re: Panic: file mail-index-transaction-finish.c: line 185

my Dovecot 2.3.17.1 (476cd46418) > >> When deleting a certain amount of messages from my INBOX via my MUA > >> (Evolution) all over sudden dovecot starts to panic > >> > >> Panic: file mail-index-transaction-finish.c: line 185 > >> (mail_index_transaction_ge

Re: Panic: file mail-index-transaction-finish.c: line 185

On 29.12.2021 10:26, Aki Tuomi wrote: On 29/12/2021 11:20 tobiswo...@gmail.com wrote: Hi list I have weird issue with my Dovecot 2.3.17.1 (476cd46418) When deleting a certain amount of messages from my INBOX via my MUA (Evolution) all over sudden dovecot starts to panic Panic: file mail

Re: Replicator: Panic: data stack: Out of memory

Now is all ok, I put same configuration of Dovecot on primary and secondary server. Dana 06.06.2022 14:14, Paul Kudla (SCOM.CA Internet Services Inc.) je napisao(la): did you get this figured out / working getting posts out of order - just wanted to make sure your ok?

Re: Replicator: Panic: data stack: Out of memory

veadm(ivan@myserv.local)<79253>: Panic: data stack: Out of memory when allocating 536870952 bytes I have lots free memory and not sure what is problem? # free -m totalusedfree shared buff/cache available Mem:795626854966

Re: Replicator: Panic: data stack: Out of memory

did you get this figured out / working getting posts out of order - just wanted to make sure your ok? Happy Monday !!! Thanks - paul Paul Kudla Scom.ca Internet Services 004-1009 Byron Street South Whitby, Ontario - Canada L1N 4S3 Toronto 416.642.7266 Main 1.866.411.

Re: Replicator: Panic: data stack: Out of memory

Sry, I check my logs and this configuration of replication is not help. Jun 06 12:05:40 doveadm(ivan@myserv.local)<2864367>: Panic: data stack: Out of memory when allocating 134217768 bytes Jun 06 12:05:40 doveadm(ivan@myserv.local)<2864367>: Error: Raw backtrace: /usr

Re: Replicator: Panic: data stack: Out of memory

Dana 04.06.2022 15:34, Paul Kudla (SCOM.CA Internet Services Inc.) je napisao(la): ok thanks for the info from here you need to turn on full debugging and then filter the log by "replicat" Now replication work when set vsz_limit in service aggregator and remove parametar replication

Re: Replicator: Panic: data stack: Out of memory

Fax 1.888.892.7266 Email p...@scom.ca On 6/4/2022 6:07 AM, Marc wrote: I think it is because of the domain, obviously you should only be running a website. -Original Message- From: dovecot On Behalf Of hi@zakaria.website Sent: Saturday, 4 June 2022 11:15 To: Dovecot Subject: Re: Re

Re: Replicator: Panic: data stack: Out of memory

ok thanks for the info from here you need to turn on full debugging and then filter the log by "replicat" It is starting to look like you have a bad email somewhere causing the crash I have yet to see this however anything is possible, when you replicate anything it needs to update indexes

Re: Replicator: Panic: data stack: Out of memory

actually suggestion below is a good idea run ps -axww (or top) to list active processes this will give you some hints top is better for overall memory i also have a perl script that will show actual memory useage, free etc utilities like this are handy to have also i found i had to set in

RE: Replicator: Panic: data stack: Out of memory

anks - paul > > Paul Kudla > > > Scom.ca Internet Services <http://www.scom.ca> > 004-1009 Byron Street South > Whitby, Ontario - Canada > L1N 4S3 > > Toronto 416.642.7266 > Main 1.866.411.7266 > Fax 1.888.892.7266 > Email p...@scom.ca > > On 6/

Re: Replicator: Panic: data stack: Out of memory

c wrote: I think it is because of the domain, obviously you should only be running a website. -Original Message- From: dovecot On Behalf Of hi@zakaria.website Sent: Saturday, 4 June 2022 11:15 To: Dovecot Subject: Re: Replicator: Panic: data stack: Out of memory On 2022-06-04 02:46, Ivan Jur

RE: Replicator: Panic: data stack: Out of memory

I think it is because of the domain, obviously you should only be running a website. > -Original Message- > From: dovecot On Behalf Of > hi@zakaria.website > Sent: Saturday, 4 June 2022 11:15 > To: Dovecot > Subject: Re: Replicator: Panic: data stack: Out of memory

Re: Replicator: Panic: data stack: Out of memory

Ok a little more help : vsz_limit = 0 --> means unlimited ram for allocation, change this/try 2g etc pending avaliable ram. I try with 524M, 1G, 2G, 4G and 8G but in any case repclicator proces got crash.

Re: Replicator: Panic: data stack: Out of memory

th Whitby, Ontario - Canada L1N 4S3 Toronto 416.642.7266 Main 1.866.411.7266 Fax 1.888.892.7266 Email p...@scom.ca On 6/3/2022 5:13 AM, Ivan Jurišić wrote: Reproduce of error (Replicator: Panic: data stack: Out of memory): == When repl

Replicator: Panic: data stack: Out of memory

Reproduce of error (Replicator: Panic: data stack: Out of memory): == When replay on any mail I will got OOM. I try add in service replicate vsz_limit = 0 but that not help (after proces dovecot/replicator eat all ram I got OOM

Re: Panic: file userdb-blocking with Dovecot 2.3.19

On 2022-05-24, Niklas Meyer wrote: > since we´ve tested around with the new dovecot release in the mailcow > project we´ve came across a curious and new error with Dovecot: > > /auth: Panic: file userdb-blocking.c: line 124 > (userdb_blocking_iter_next): assertion failed: (ct

Re: Panic: file userdb-blocking with Dovecot 2.3.19

Am 24.05.22 um 16:00 schrieb Niklas Meyer: Hello all, since we´ve tested around with the new dovecot release in the mailcow project we´ve came across a curious and new error with Dovecot: /auth: Panic: file userdb-blocking.c: line 124 (userdb_blocking_iter_next): assertion failed: (ctx->co

Panic: file userdb-blocking with Dovecot 2.3.19

Hello all, since we´ve tested around with the new dovecot release in the mailcow project we´ve came across a curious and new error with Dovecot: /auth: Panic: file userdb-blocking.c: line 124 (userdb_blocking_iter_next): assertion failed: (ctx->conn != NULL)/ *System Informat

Re: Pop3 Panic Error

> On 24/03/2022 09:32 Aki Tuomi wrote: > > > > On 24/03/2022 09:29 Aurel Mihai wrote: > > > > > > Hello, > > after upgrade to version 2.3.18, we enconter a lot of errors, such as: > > > > Mar 22 14:08:32 mail2 dovecot: pop3(user@dom

Re: Pop3 Panic Error

> On 24/03/2022 09:29 Aurel Mihai wrote: > > > Hello, > after upgrade to version 2.3.18, we enconter a lot of errors, such as: > > Mar 22 14:08:32 mail2 dovecot: pop3(user@domain)<52269><3y3GeM3aQ+tWadtM>: > Panic: file lib-event.c: line 585 (event_reas

Pop3 Panic Error

Hello, after upgrade to version 2.3.18, we enconter a lot of errors, such as: Mar 22 14:08:32 mail2 dovecot: pop3(user@domain)<52269><3y3GeM3aQ+tWadtM>: Panic: file lib-event.c: line 585 (event_reason_code_prefix): assertion failed: (name[0] != '\0') Mar 22 14:08:32 ma

Re: imap_metadata plugin panic

Hi, So I have waited to see what comes in updates and while it hasn't been fixed on my end, it at least doesn't panic anymore and properly errors out. This error has only happened when deleting folders. No other action I do from day to day has triggered this in the logs that I can

Dovecot 2.3.18 Panic-Error (name[0] != '\0')

Hello, after upgrade to version 2.3.18, we enconter a lot of errors, such as: Mar 22 14:08:32 mail2 dovecot: pop3(user@domain)<52269><3y3GeM3aQ+tWadtM>: Panic: file lib-event.c: line 585 (event_reason_code_prefix): assertion failed: (name[0] != '\0') Mar 22 14:08:32 ma

Re: dovecot-2.3.17: "Panic: file ioloop.c: line 865"

ing dovecot package updates. > > Panic: file ioloop.c: line 865 (io_loop_destroy): assertion failed: (ioloop > == current_ioloop) > Error: Raw backtrace: #0 t_askpass[0x7fc609b0eba0] -> #1 > backtrace_append[0x7fc609b0ee00] -> #2 backtrace_get[0x7fc609b0ef70] ->

dovecot-2.3.17: "Panic: file ioloop.c: line 865"

Hello, we got the same backtrace in dovecot-ee version 2:2.3.17-8+ubuntu20.04 as Andreas Piper mentioned in November 2021  https://dovecot.org/pipermail/dovecot/2021-November/123468.html after installing dovecot package updates. Panic: file ioloop.c: line 865 (io_loop_destroy): assertion failed

Re: Dovecot 2.3.17 on FreeBSD 12.2 panic

ello, > > > > > > I have dovecot 2.3.17 running on FreeBSD 12.2 and it keeps panicking: > > > > > > Jan 10 03:04:07 strida dovecot[55198]: > > > imap(xiste...@0x58.com)<56382>: Panic: > > > file array.c: line 10 (array_idx_modifiable_i): as

Re: Dovecot 2.3.17 on FreeBSD 12.2 panic

> On Jan 9, 2022, at 22:35, Aki Tuomi wrote: > > >> On 10/01/2022 05:32 Bert JW Regeer wrote: >> >> >> Hello, >> >> I have dovecot 2.3.17 running on FreeBSD 12.2 and it keeps panicking: >> >> Jan 10 03:04:07 strida dovecot[55

Re: Dovecot 2.3.17 on FreeBSD 12.2 panic

> On 10/01/2022 05:32 Bert JW Regeer wrote: > > > Hello, > > I have dovecot 2.3.17 running on FreeBSD 12.2 and it keeps panicking: > > Jan 10 03:04:07 strida dovecot[55198]: > imap(xiste...@0x58.com)<56382>: Panic: file > array.c: line 10 (array_idx_m

Re: Panic: file mail-index-transaction-finish.c: line 185

Aki sorry for not being specific enough. I already use director on my two public-facing dovecots. Although the mailboxes on my dovecot backend are in nfs there is only one backend dovecot accessing the mailboxes. I had two backends long ago and the the nfs is a relict of that time. But atm only ha

Re: Panic: file mail-index-transaction-finish.c: line 185

> On 29/12/2021 11:40 tobiswo...@gmail.com wrote: > > > On Wed, 2021-12-29 at 11:26 +0200, Aki Tuomi wrote: > > > > > > Do you have multiple backends with concurrent access via e.g. nfs? > > > > Aki > > > > Aki, > > yes all mailboxes are in a nfs share. Concurrent access could be > possi

Re: Panic: file mail-index-transaction-finish.c: line 185

On Wed, 2021-12-29 at 11:26 +0200, Aki Tuomi wrote: > > > Do you have multiple backends with concurrent access via e.g. nfs? > > Aki > Aki, yes all mailboxes are in a nfs share. Concurrent access could be possible as I have several MUA (my desktop and my mobiles). Although only the client on

Re: Panic: file mail-index-transaction-finish.c: line 185

> On 29/12/2021 11:20 tobiswo...@gmail.com wrote: > > > Hi list > > I have weird issue with my Dovecot 2.3.17.1 (476cd46418) > When deleting a certain amount of messages from my INBOX via my MUA > (Evolution) all over sudden dovecot starts to panic > > Pani

Panic: file mail-index-transaction-finish.c: line 185

Hi list I have weird issue with my Dovecot 2.3.17.1 (476cd46418) When deleting a certain amount of messages from my INBOX via my MUA (Evolution) all over sudden dovecot starts to panic Panic: file mail-index-transaction-finish.c: line 185 (mail_index_transaction_get_uid): assertion failed: (seq

Re: dovecot panic

Sorry to reply to myself ;-) but I found a way around this panic. After unsubscribe and subscribe again to my inbox folder the panics in maillog suddenly stopped. Before I got the panic on EVERY click on my inbox in MUA. I was cleaning up my mailbox (moved and deleted a log of messages) when the

dovecot panic

Hi list since today I receive dovecot panics in my mail logs, whenever I want to access on my inbox in my mailclient (evolution) Details: dovecot --version 2.3.17.1 (476cd46418) Centos 7 (latest updates) x86 architecture mailbox stored in NFS > Panic: file mail-index-transaction-finis

Re: dovecot-2.3.17: "Panic: file ioloop.c: line 865"

Hi, I can add a detail, every time I get the "panic error" on the replica node, I had one minute before this log written on the first node: /dic 14 11:04:50 xxx dovecot[16715]: doveadm(xxx)<16454>: Error: Couldn't lock /mnt/mail-storage-lv0007/xxx/.dovecot-sync.l

Re: dovecot-2.3.17: "Panic: file ioloop.c: line 865"

/mnt/mail-storage-lv0003/xxx/Maildir/dovecot-uidlist: Duplicate file entry at line 2162: 1639396906.M258993P16725.xxx,S=7304,W=7467 (uid 71966 -> 71970)// //Dec 13 14:26:20 Error: doveadm(27294): write(xxx) failed: Timed out after 60 seconds// //Dec 13 14:26:20 Panic: doveadm(27294): fi

Re: 2.3.17: Panic on LMTP deliveries

abase// // //Dec 12 08:42:54 lmtp(u...@domain.tld)<80363>: Panic: file imem.c: line 65 (i_strconcat): assertion failed: (str1 != NULL) /I found your answer here <https://www.mail-archive.com/dovecot@dovecot.org/msg84893.html>: /Problem confirmed. This is a 2.3.17 regression. Tracking inter

Re: 2.3.17: Panic on LMTP deliveries

server: conn unix:uid=125 [1]: rcpt u...@domain.tld: >duplicate db: User u...@domain.tld doesn't have home dir set, disabling >duplicate database// >// >//Dec 12 08:42:54 lmtp(u...@domain.tld)<80363>: >Panic: file imem.c: line 65 (i_strconcat): assertion failed: (str

2.3.17: Panic on LMTP deliveries

...@domain.tld doesn't have home dir set, disabling duplicate database// // //Dec 12 08:42:54 lmtp(u...@domain.tld)<80363>: Panic: file imem.c: line 65 (i_strconcat): assertion failed: (str1 != NULL) /I found your answer here <https://www.mail-archive.com/dovecot@dovecot.org/msg84893.ht

Re: imap_metadata plugin panic

iv/$key), just the priv dict db schema > with "pattern = $key" per one of your emails to the ML, and just the > "priv/$key" pattern. All of those combinations produce the same issue. In > summary, I've tried several things but result is still that I can create &g

Re: imap_metadata plugin panic

ons produce the same issue. In summary, I've tried several things but result is still that I can create folders but deletion causes a panic. As of last email sending the dict, here is what dovecot knows about the dicts: dict {     quota_clone = mysql:/etc/dovecot/dovecot-quota-dict.c

Re: imap_metadata plugin panic

.com] > *Sent:* Monday, November 22, 2021, 5:13 AM > *To:* dovecot@dovecot.org, Elisamuel Resto > *Cc:* dove...@ptld.com > *Subject:* imap_metadata plugin panic > > > Hi, I wanted to see /etc/dovecot/dovecot-dict-sql.conf.ext > > > > Aki > > > >

Re: imap_metadata plugin panic

pen-xchange.com] *Sent:* Monday, November 22, 2021, 5:13 AM *To:* dovecot@dovecot.org, Elisamuel Resto *Cc:* dove...@ptld.com *Subject:* imap_metadata plugin panic Hi, I wanted to see /etc/dovecot/dovecot-dict-sql.conf.ext Aki On 22 November 2021 11.08.01 UTC, Elisamuel Resto wrote: Aki

Re: imap_metadata plugin panic

Hi, I wanted to see /etc/dovecot/dovecot-dict-sql.conf.ext Aki On 22 November 2021 11.08.01 UTC, Elisamuel Resto wrote: >Aki, > ># 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf ># Pigeonhole version 0.5.16 (09c29328) ># OS: Linux 5.14.16-arch1-1 x86_64 ext4

Re: imap_metadata plugin panic

sto wrote: >>> I have gone through my configuration and even found a configuration example >>> by Aki and that confirms how I configured it… still getting that >>> error. >> >>> Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Panic: lib-sql: Too many >>&g

Re: imap_metadata plugin panic

configured it… still getting that >> error. > >> Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Panic: lib-sql: Too many >> bind args (2) for statement: SELECT meta_key FROM metadata WHERE meta_key >> LIKE AND username = ? > > > You fixed the query s

Re: imap_metadata plugin panic

or. > > > Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Panic: lib-sql: Too many > > bind args (2) for statement: SELECT meta_key FROM metadata WHERE meta_key > > LIKE AND username = ? > > > You fixed the query syntax to make sure that is not the issue? > &quo

Re: imap_metadata plugin panic

> On 11-21-2021 1:15 pm, Elisamuel Resto wrote: > I have gone through my configuration and even found a configuration example > by Aki and that confirms how I configured it… still getting that > error. > Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Panic: lib-sql: Too many

Re: imap_metadata plugin panic

missing information or fix it otherwise. > > Regards, > Elisamuel Resto > > > Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Panic: lib-sql: Too many > bind args (2) for statement: SELECT meta_key FROM metadata WHERE meta_key > LIKE AND username = ? > Nov 15 12:

Re: dovecot-2.3.17: "Panic: file ioloop.c: line 865"

Hello, as these 'Panic'-Events continue to appear every few minutes in my replicator-log, I would like to ask, if you have any hints how to repair the correlated mailbox? Andreas Am 11.11.21 um 15:04 schrieb Piper Andreas: Hello, Can you install dovecot debug symbols and re

Re: imap_metadata plugin panic

ards, > Elisamuel Resto > > > Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Panic: lib-sql: Too > many bind args (2) for statement: SELECT meta_key FROM metadata WHERE > meta_key LIKE  AND username = ? > Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Error: Raw backtrace

imap_metadata plugin panic

61]: dict(51438): Panic: lib-sql: Too many bind args (2) for statement: SELECT meta_key FROM metadata WHERE meta_key LIKE  AND username = ? Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x43) [0x7f449789d073] ->

Re: 2.3.17: Panic on LMTP deliveries

On 11/11/2021 14:20, Michael Glaus wrote: Since the doevcot update to 2.3.17 i get a panic if a mail is delivered with lmtp. In the logs i get these messages: lmtp(r...@example.com)<21067>: Error: lmtp-server: conn 10.0.0.105:52981 [1]: rcpt r...@example.com: duplicate db:

Re: dovecot-2.3.17: "Panic: file ioloop.c: line 865"

Hello, Can you install dovecot debug symbols and redo the gdb backtrace? Package name is likely `dovecot-dbg`. done, thanks for the hint. Andreas (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x7f4e58be0921 in __GI_abort () at abort.c:79 #2 0

Re: dovecot-2.3.17: "Panic: file ioloop.c: line 865"

> On 11/11/2021 15:53 Piper Andreas wrote: > > > Hello, > > since the upgrade from dovecot-2.3.16 to 2.3.17 I get 'Panic'-errors in > the system-log of my replicator hosts. See below for log messages, > doveconf-output and gdb-backtrace. Storage filesystem

dovecot-2.3.17: "Panic: file ioloop.c: line 865"

Hello, since the upgrade from dovecot-2.3.16 to 2.3.17 I get 'Panic'-errors in the system-log of my replicator hosts. See below for log messages, doveconf-output and gdb-backtrace. Storage filesystem is ZFS. The error seems to be correlated with exactly one user-mailbox, thi

2.3.17: Panic on LMTP deliveries

Hello Since the doevcot update to 2.3.17 i get a panic if a mail is delivered with lmtp. In the logs i get these messages: lmtp(r...@example.com)<21067>: Error: lmtp-server: conn 10.0.0.105:52981 [1]: rcpt r...@example.com: duplicate db: User r...@example.com doesn't have h

Re: replicator: Panic: data stack: Out of memory when allocating ...

stian Podjasek wrote: I've seen thread with problem identical to mine started "Fri May 28 13:54:27 EEST 2021" and I was wondering did you get to fix this issue? Mine looks like this: dovecot: replicator: Panic: data stack: Out of memory when allocating 1073741864 bytes dovecot: re

replicator: Panic: data stack: Out of memory when allocating ...

I've seen thread with problem identical to mine started "Fri May 28 13:54:27 EEST 2021" and I was wondering did you get to fix this issue? Mine looks like this: dovecot: replicator: Panic: data stack: Out of memory when allocating 1073741864 bytes dovecot: replicator: Error

  1   2   3   4   5   6   7   8   9   10   >