similar to: Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed:

Displaying 20 results from an estimated 5000 matches similar to: "Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed:"

2018 Oct 02
2
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(user at example.com)<50643></2k4Sjp3vMqC496W>: Panic: file ostream-zlib.c: line 37 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished || zstream->ostream.ostream.stream_errno != 0 || zstream->ostream.error_handling_disabled) Oct 02 10:01:39 imap(user at
2018 Jan 23
2
Panic: data stack: Out of memory when allocating bytes
Hello, I'm using Dovecot 2.3 and sometimes i get this: --- snip --- Jan 23 14:23:13 mail dovecot: imap(bob at tutech.de)<4880><PDqibHFjMvrAqG1n>: Panic: data stack: Out of memory when allocating 134217768 bytes Jan 23 14:23:13 mail dovecot: imap(bob at tutech.de)<4880><PDqibHFjMvrAqG1n>: Fatal: master: service(imap): child 4880 killed with signal 6 (core dumped)
2018 Jan 23
2
Panic: data stack: Out of memory when allocating bytes
On Tue, Jan 23, 2018 at 14:03:27 -0500, Josef 'Jeff' Sipek wrote: > On Tue, Jan 23, 2018 at 18:21:38 +0100, Thomas Robers wrote: > > Hello, > > > > I'm using Dovecot 2.3 and sometimes i get this: > > > > --- snip --- > > Jan 23 14:23:13 mail dovecot: imap(bob at tutech.de)<4880><PDqibHFjMvrAqG1n>: > > Panic: data stack: Out of
2017 Dec 24
3
zlib plugin producing errors on 2.3.0
Hello, I use the zlib and imap_zlib plugins on FreeBSD. As of 2.3.0, my logs are producing these errors every so often, but AFAICT the messages themselves aren't getting corrupted. Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished || zstream->ostream.ostream.stream_errno != 0) Fatal: master: service(imap): child 80128 killed with
2014 Mar 28
1
Panic: file ostream-lzma.c: line 147: unreached. Dovecot 2.2.12 with zlib/XZ compression
While migrating users from Cyrus IMAP v2.3.14 to Dovecot 2.2.12 (compiled from source) dsync aborts with a backtrace on some (maybe 15 out of 800) mail accounts: (same error happens wiht or without -f flag) dsync -D -v -o mail_fsync=never mirror -f -R -u user at domain imapc: <snip> dsync(user at domain.com): Debug: brain M: in state=sync_mails dsync(user at domain.com): Debug: brain M:
2018 Jan 23
0
Panic: data stack: Out of memory when allocating bytes
On Tue, Jan 23, 2018 at 18:21:38 +0100, Thomas Robers wrote: > Hello, > > I'm using Dovecot 2.3 and sometimes i get this: > > --- snip --- > Jan 23 14:23:13 mail dovecot: imap(bob at tutech.de)<4880><PDqibHFjMvrAqG1n>: > Panic: data stack: Out of memory when allocating 134217768 bytes Interesting... imap is trying to allocate 128MB and failing. A couple of
2017 Nov 10
3
rawlog segfaults (error 4 in libdovecot.so.0.0.0)
Hello everybody, i tried to debug imap sessions with the rawlog feature and rawlog creates files but when i try to dump them doveadm tells me [...] Error: zlib.read((file)): unexpected EOF at [...]. I looked at syslog files and i see, that rawlog gets terminated with a segfault, e.g.: segfault at 10 ip 00007ff6da362596 sp 00007fffe725a080 error 4 in libdovecot.so.0.0.0[7ff6da2a4000+122000] Is
2014 Jun 23
4
OOM in Dovecot 2.2.13 imap
Hi, we run Dovecot 2.2.13 on Debian Wheezy with a couple thousand mailboxes. We have two users that repeatedly trigger an OOM condition with IMAP. Jun 23 12:53:21 lxmhs74 dovecot: imap(USER): Fatal: pool_system_realloc(268435456): Out of memory Jun 23 12:53:21 lxmhs74 dovecot: imap(USER): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x6c15f) [0x7f11766cc15f] ->
2014 May 06
0
on High Load using IMAPSYNC : Panic: file ostream-lzma.c: line 147: unreached. Dovecot 2.2.12 with zlib/XZ compression
when syncing Mailboxes with IMAPSYNC, using xz compression the dbox file gets corrupted. the same configuration was working ok on low load with xz compression. Dovecot Version 2.2.12 Linux Mint 16 EXT4 Filesystem another dovecot user already reported the same problem on the mailinglist, using dsync. That user switched to bz2 compression what worked for him. the answer was : > are you on
2014 May 06
1
WG: on High Load using IMAPSYNC : Panic: file ostream-lzma.c: line 147: unreached. Dovecot 2.2.12 with zlib/XZ compression
when syncing Mailboxes with IMAPSYNC, using xz compression the dbox file gets corrupted. the same configuration was working ok on low load with xz compression. Dovecot Version 2.2.12 Linux Mint 16 EXT4 Filesystem another dovecot user already reported the same problem on the mailinglist, using dsync. That user switched to bz2 compression what worked for him. the answer was : > are you on
2011 Aug 27
2
: error while loading shared libraries: libdovecot.so.0 (arm cross compile)
Hi. I've made a new attempt at build Dovecot. The build and then install processes appeared to work find. Then when I try to run Dovecot it reports the error: /share/MD0_DATA/optware/opt/sbin/dovecot: error while loading shared libraries: libdovecot.so.0: cannot open shared object file: No such file or directory To get a better idea of what's going on, I added
2012 Feb 13
2
[Dovecot 2.1] imap service crash when using some clients
Hello Pascal, I've just tested rc6 and get almost the same results. imap still crashes, but Horde still works. I forgot to mention that this is on FreeBSD 8 using gcc 4.6 and LTO. And contrary to what I said in my initial email, it doesn't seem to be ACL plugin related. imap crashes even if it's not in the plugins list. Here is the backtrace: # gdb /usr/libexec/dovecot/imap
2018 Jun 06
1
Shared mailboxes, index files and 'per-user-seen' flags
Hello, i have a dovecot server version 2.3.1 under CentOS 6.9 and we're using shared mailboxes with index files shared. With this configuration I can see a lot of error messages like: Jun 6 13:20:31 mail dovecot: Error: imap(userA at tutech.de)<4513> <onjjWPdtDuLAqG3R>: /export/home/imap/userA at tutech.de/shared /userB at tutech.de/folder/dovecot.index.pvt view is
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
2018 Nov 21
2
Crash in director for secure lmtp proxy connections
Hi, After updating some of our director servers from 2.2.36 to 2.3.3 (dcead646b) we experience crashes in about 1/5000 mails in lmtp delivery: Nov 13 12:23:36 Fatal: lmtp(113620): master: service(lmtp): child 113620 killed with signal 6 (core dumped) Nov 13 12:23:36 Panic: lmtp(113623): file ostream-dot.c: line 208 (o_stream_dot_sendv): assertion failed: ((size_t)ret == sent + added) Nov 13
2018 Jan 06
2
zlib plugin producing errors on 2.3.0
On 5 Jan 2018, at 18.33, Carsten Uppenbrink <info at uppenbrink.net> wrote: > > On 24.12.2017 15:58, Adam Weinberger wrote: >> Hello, >> I use the zlib and imap_zlib plugins on FreeBSD. As of 2.3.0, my logs >> are producing these errors every so often, but AFAICT the messages >> themselves aren't getting corrupted. >> Panic: file ostream-zlib.c: line
2016 Nov 01
1
Panic: file mail-transaction-log-file.c: line 104 (mail_transaction_log_file_free): assertion failed: (!file->locked)
On 25.08.2016 10:29, Aki Tuomi wrote: > > On 14.07.2016 10:56, Arkadiusz Mi?kiewicz wrote: >> 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:
2018 Jan 29
1
Panic: data stack: Out of memory when allocating bytes
Any idea what the problem could be? Is there anything more i could do to encircle the problem? Or perhaps is the information i provided uncomplete? Am 25.01.2018 um 16:24 schrieb Thomas Robers: > Hi, > > Am 24.01.2018 um 23:39 schrieb Josef 'Jeff' Sipek: >> It looks like the binaries are stripped.? There should be a "debug" >> package >> you can
2013 Nov 05
0
infinite loop (causing crash) whilst closing connection
Hi Timo, As a follow-up to my earlier email, I've managed to get a few backtraces now. #305439 o_stream_close (stream=0x1680c10) at ostream.c:85 #305440 0x00007ff222f70f3c in o_stream_zlib_send_outbuf (zstream=0x1680b80) at ostream-zlib.c:97 #305441 0x00007ff222f70fef in o_stream_zlib_send_flush (zstream=0x1680b80) at ostream-zlib.c:182 #305442 0x00007ff222f711cb in o_stream_zlib_flush
2013 Nov 12
2
dovecot-2.2.7: Fatal: master: service(imap): child 49545 killed with signal 11 (core dumped)
Hi! After upgrade I'm noticing many coredummps, below is backtrace: $ echo "bt"|gdb .... #0 o_stream_zlib_flush (stream=0xc8be5b27640) at ostream-zlib.c:222 222 if (o_stream_zlib_send_flush(zstream) < 0) (gdb) #0 o_stream_zlib_flush (stream=0xc8be5b27640) at ostream-zlib.c:222 #1 0x00007a695e8f09cd in o_stream_flush (stream=stream at entry=0xc8be5b276d0) at