search for: stream_errno

Displaying 20 results from an estimated 42 matches for "stream_errno".

2008 Sep 16
2
assertion failure in current hg, file istream.c: line 303 (i_stream_read_data): assertion failed: (stream->stream_errno != 0) (1.1.3 was working fine)
Today I updated to current dovecot-1.1 hg tree and I got many of these assertion failures: file istream.c: line 303 (i_stream_read_data): assertion failed: (stream->stream_errno != 0) (gdb) bt full #0 0x00352402 in __kernel_vsyscall () No symbol table info available. #1 0x0043ed20 in raise () from /lib/libc.so.6 No symbol table info available. #2 0x00440631 in abort () from /lib/libc.so.6 No symbol table info available. #3 0x080f6968 in default_fatal_finish (type=LOG_T...
2012 Jan 13
1
2.1.rc3 (1a722c7676bb): Panic: file ostream.c: line 173 (o_stream_sendv): assertion failed: (stream->stream_errno != 0)
Hi Timo, today some imap processes are crashed. Regards, Pascal -- The trapper recommends today: f007ba11.1201322 at localdomain.org -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: core.imap.1326475521-24777_bt.txt URL: <http://dovecot.org/pipermail/dovecot/attachments/20120113/e24444ed/attachment-0008.txt> -------------- next part
2017 Dec 24
3
zlib plugin producing errors on 2.3.0
...d 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 signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished || zstream->ostream.ostream.stream_errno != 0) Fatal:...
2010 Aug 31
0
istream_read like zlib, but without zlib
...ize == 0){ /* need to read more data. try to read a full CHUNK_SIZE */ i_stream_skip(stream->parent, emxstream->prev_size); if (i_stream_read_data(stream->parent, &data, &size, CHUNK_SIZE-1) == -1 && size == 0) { if (stream->parent->stream_errno != 0) { stream->istream.stream_errno = stream->parent->stream_errno; } else { i_assert(stream->parent->eof); stream->istream.stream_errno = EPIPE; } return -1; } emxstream->prev_...
2018 Jan 06
2
zlib plugin producing errors on 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 signal 6 (core >> not dumped - set service imap { drop_priv_before_exec=yes }) >> Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion >> failed: (zstream->ostream.finished || >> zstream-...
2009 May 01
2
mbox-snarf plugin and istream-mail-stats.c revision 9000:b02c642b4e51
I'm getting this error: May 1 09:09:30 tr27n12.aset.psu.edu syslog: PSU mbox-snarf name is INBOX May 1 09:09:30 tr27n12.aset.psu.edu dovecot: Panic: IMAP(tstem38): file istream-mail-stats.c: line 75: assertion failed: (ret != -1 || stream->istream.eof || stream->istream.stream_errno != 0) Will this error go away before the general 1.2 release? Thanks, Jonathan
2009 Mar 03
4
failed assertion in 1.1.8: istream.c: line 81
Hello, We're having a problem in Dovecot 1.1.8 with a failed assertion on certain mbox format mailboxes. It happens both with deliver when it attempts to delier to the mailbox, and with IMAP connections for the affected box (though I'm not sure what they're doing at the time). Mar 3 12:55:26 <snip> dovecot: Panic: IMAP(<snip>): file istream.c: line 81 (i_stream_read):
2008 Feb 23
2
Update from 1.0.10 -> 1.1rc1 file message-parser.c: line 766 (message_parser_parse_next_block): assertion failed
Feb 23 20:40:36 postamt dovecot: IMAP(username): file message-parser.c: line 766 (message_parser_parse_next_block): assertion failed: (ctx->input->eof || ctx->input->closed || ctx->input->stream_errno != 0) Feb 23 20:40:36 postamt dovecot: IMAP(username): Raw backtrace: /usr/local/libexec/dovecot/imap [0x8009236d] -> /usr/local/libexec/dovecot/imap [0x80091ed8] -> /usr/local/libexec/dovecot/imap(message_parser_parse_next_block+0xad) [0x8008ae0d] -> /usr/local/libexec/dovecot/imap(index_...
2005 Sep 19
0
1.0alpha2: two asserts/cores
...95 395 i_stream_skip(input, part->physical_pos - input->v_offset); (gdb) print *ctx $1 = {pool = 0x0, key = 0x98f00 "MEETING", key_len = 7, charset = 0xa9788 "US-ASCII", unknown_charset = 0, search_header = 0} (gdb) print *input $2 = {v_offset = 1530, stream_errno = 0, mmaped = 0, closed = 0, seekable = 0, eof = 0, real_stream = 0xb9c78} (gdb) print *part $3 = {parent = 0xb2188, next = 0x0, children = 0xb2228, physical_pos = 1500, header_size = {physical_size = 857, virtual_size = 875, lines = 0}, body_size = {physical_size = 551367, virtual_size = 558...
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 example.com)<50643></2k4Sjp3vMqC496W>: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xce56a) [0x7f442487556a] -> /usr/lib64/dovecot/libdovecot.so.0(+0xce5b1) [0x7f44248755b1] -> /usr...
2008 Nov 23
3
dovecot >1.1.3 + antispam plugin issues
...et() used invalid cached next_offset? */ i_error("Next message unexpectedly lost from %"PRIuUOFF_T, rstream->hdr_offset + rstream->mail_size); rstream->eof = TRUE; rstream->corrupted = TRUE; rstream->istream.istream.stream_errno = EINVAL; stream->pos = 0; return -1; } Now, with versions >1.1.3 this won't helps and plugin fails. Anyone knows how to get it working? I would like to upgrade to newest dovecot release Best regards, mr
2003 Oct 16
2
A view quirks
Aloha Timo. I found a few odd things while playing with dovecot. At least one of them bugs me, but it might be a result of my own patches - I haven't testet it with mbox or maildir, yet. The details :) 1. * OK dovecot ready. A = (<return> Connection closed by foreign host. 2. * OK dovecot ready. A001 LOGIN xxxxxx xxxxxx A001 OK Logged in. A002 COPY 1 INBOX Connection closed by
2018 Jan 05
0
zlib plugin producing errors on 2.3.0
.... 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 signal 6 (core > not dumped - set service imap { drop_priv_before_exec=yes }) > Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion > failed: (zstream->ostream.finished || > zstream->ostream.ostream....
2018 Jan 09
0
zlib plugin producing errors on 2.3.0
...; 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 signal 6 (core >>> not dumped - set service imap { drop_priv_before_exec=yes }) >>> Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion >>> failed: (zstream->ostream.finished || &...
2008 Oct 16
2
dovecot 1.1.4 maildir imap segfault in message_parse_header_next
I've tried to stress test dovecot 1.1.4 with imaptest for days without any assertion failure or crash. Just some "got too little data" messages. So far it's the most stable 1.1.x version. Today a user got this imap segfault with vanilla 1.1.4 (I don't know if it's something you have already fixed in current tree). The user didn't complain of anything, I've just
2006 Sep 20
1
dovecot rc7 assert, core
...->v_offset); (gdb) print *ctx $1 = {pool = 0x66696c65, key = 0x2025733a <Address 0x2025733a out of bounds>, key_len = 543975790, charset = 0x65202564 <Address 0x65202564 out of bounds>, unknown_charset = 0, search_header = 0} (gdb) print *input $2 = {v_offset = 7882833662174520621, stream_errno = 1651467385, mmaped = 0, closed = 0, seekable = 1, eof = 0, real_stream = 0x7263682e} (gdb) print *part Cannot access memory at address 0x189 (gdb) print part $3 = (const struct message_part *) 0x189 (gdb) print &part Can't take address of "part" which isn't an lvalue. (gdb...
2005 Sep 07
0
1.0alpha1: new assert/core
...95 395 i_stream_skip(input, part->physical_pos - input->v_offset); (gdb) print *ctx $1 = {pool = 0x0, key = 0x98bd0 "LOBSTER", key_len = 7, charset = 0xa9460 "US-ASCII", unknown_charset = 0, search_header = 0} (gdb) print *input $2 = {v_offset = 1387, stream_errno = 0, mmaped = 0, closed = 0, seekable = 0, eof = 0, real_stream = 0xb95c8} (gdb) print part *part $3 = {parent = 0xb1918, next = 0xb19b8, children = 0x0, physical_pos = 1384, header_size = {physical_size = 93, virtual_size = 98, lines = 0}, body_size = {physical_size = 4312, virtual_size =...
2005 Jun 15
6
Compressed maildir
Greetings, I noticed a while back someone posted a patch/plugin that allowed Dovecot to use compressed mbox files. I'm now wondering how far that would put us from having compressed maildir? I have a server with more CPU than disk space, and while I can buy more HDD space, my backup solution doesn't make that practical. It seems to me that when looking for a message file, if it
2006 Apr 26
2
being courier_imap compatible
OK, I am running (for many years now) an existing courier_imap maildir ++ setup with exim as the MTA. Has been fine. I have my own custom ldap schema for user account definition and authorization. I installed dovecot 1.0 beta 7 as a test and have it listening on a different port. I would like, if possible, to set things up so that a user could use either dovecot or courier. Having to
2007 Nov 15
1
imap process consuming 100% CPU (Dovecot 1.0.3)
...gt; 234 if ((ret = i_stream_read(mstream->input)) == -2) { > > 235 if (stream->skip == 0) > > 236 return -2; > > 237 } > > 238 stream->istream.stream_errno = mstream->input->stream_errno; > > 239 stream->istream.eof = mstream->input->eof; > > 240 stream->buffer = i_stream_get_data(mstream->input, &pos); > > 241 } else { > > 242 ret...