similar to: 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)

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

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

Hi Timo, some imap processes seems to have some problems. Regards, Pascal -------------- next part -------------- Core was generated by `dovecot/imap'. Program terminated with signal 6, Aborted. #0 0x00007fbf87b25475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt full #0 0x00007fbf87b25475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1

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

Hello, I'm developing an encryption plugin for dovecot and ran into a problem with the stacking of i/o-streams. The encryption i/o-streams are working fine on any kind of mail the test suite is passing through them. But as soon as the zlib plugin is enabled the logs show an cache error: failed: Cached message size larger than expected (214 > 206, box=INBOX, UID=1) I've already

I've been getting a few of these errors on a couple different mboxes. This is using the CVS version as of May 14. So far, these are the only errors and it looks like most/all of the older ones are gone. (maybe I shouldn't say that ;-) dovecot: May 16 17:41:07 Error: 20973 IMAP(todd.bluegenesis.com): file mbox-sync.c: line 1165 (mbox_sync_handle_eof_updates): assertion failed:

Apart from a few warnings (attached), and a bit of patience, the compiler terminates without error. On patience, OBSD has two processes who took almost half the CPU when compiling: reaper and zerothread. Will look into the warnings, and the testing errors (also attached). Let see how it works on this machine. OpenBSD 6.7 (GENERIC.MP) #2: Thu Jun 4 09:55:08 MDT 2020 real mem = 17125511168

Hi List, try 1.1.4 and have new Panics in Log. Hoped that 1.1.3 finishes this errors... Oct 8 21:56:28 dd10636 dovecot: IMAP(username): Loading modules from directory: /usr/lib/dovecot/imap Oct 8 21:56:28 dd10636 dovecot: IMAP(username): Module loaded: /usr/lib/dovecot/imap/lib20_mail_log_plugin.so Oct 8 21:56:28 dd10636 dovecot: IMAP(username): Effective uid=857, gid=628,

I found imap core in coredump dir: (gdb) bt #0 0x00000000004abdea in message_parse_header_next (ctx=0x79c150, hdr_r=0x7fffffffe478) at message-header-parser.c:114 #1 0x00000000004a8193 in read_header (mstream=0x795330) at istream-header-filter.c:162 #2 0x00000000004a84e7 in i_stream_header_filter_read (stream=0x795330) at istream-header-filter.c:288 #3 0x00000000004bc216 in i_stream_read

Hi, I've enabled autoexpunge for Trash and Junk. Now imap process core dumps occasionally. Tomppa > program terminated by signal SEGV (no mapping at the fault address) > 0xff0dc2e0: o_stream_get_buffer_used_size : ld [%o0 + 20], %o0 > Current function is notify_ok (optimized) > 13 if (o_stream_get_buffer_used_size(client->output) != 0) >

http://bugzilla.mindrot.org/show_bug.cgi?id=303 Summary: conftest fails to determine mmap anon shared Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: openssh-unix-dev at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=303 mouring at eviladmin.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From mouring at eviladmin.org

Can anyone describe the asterisk implementation of this any better than the sample config files do? from zapata.conf ; Trunk groups are used for NFAS or GR-303 connections. ; ; Group: Defines a trunk group. ; group => <trunkgroup>,<dchannel>[,<backup1>...] ; ; trunkgroup is the numerical trunk group to create ; dchannel is the zap channel which will

For those who don't watch asterisk-cvs, it appears that markster has begun (and possibly) completed adding GR-303 FXS support to Asterisk. This means that Asterisk could be used as an "access concentrator" off of a class 5 switch, which gives us a higher-level alternative between using single PRIs and going all the way to SS7. I for one am very interested in pursuing this option

I'm a little confused on whether the GR303 support in * will accept calls from a Siemens central office that has GR303. Anyone know for sure?

-----BEGIN PGP SIGNED MESSAGE----- Does anyone have any working example GR-303 configurations for zaptel and zapata conf? The information available on the wiki as well as in the sample configurations just doesn't seem to be enough to bridge the gap for me. In Zaptel.conf, Do you set up a GR-303 circuit like a PRI with b and d channels or do you set fxo or fxs, ks signalling? How do you

Can anybody tell me please, what isn't correct? What should I change in config? /var/samba/log/log.XP-CLIENT-IP: [2006/06/22 08:24:54, 1] smbd/sesssetup.c:reply_spnego_kerberos(303) Username DOMAIN\XP-CLIENT-NAME$ is invalid on this system all works in general, but the error above is listed in every /var/log/samba/log.CLIENT Thanks Steffen ---------------------------------------------

Full_Name: Naoki Takebayashi Version: 0.65.1 OS: Linux/Alpha Submission from: (NULL) (129.79.224.171) When I was reading a file with read.table("junk.data"), it seg-faulted. I found out that it seg-faulted when the last line of data file didn't have the newline char. For example, file like this: 23 3 31 2 24 1<EOF> Here is a fix. --- R-0.65.1/src/main/scan.c.orig

> > Is this behavior cured, or do you continue to see it? > No, the behavior isn't cured. We still continue to see it with various clients. I have posted a couple of truss outputs, but so far no resolution. Sorry for the slow response. I've been "fighting other fires". Jackie > Jackie Hunt wrote: > >> On Mon, 2007-09-03 at 12:37 +0200, Robert

In data marted? 18 settembre 2018 14:07:26 CEST, Aki Tuomi ha scritto: > If you are using systemd, create > /etc/systemd/system/dovecot.service.d/limits.conf and put > [Service]LimitCORE=infinity > > and run > systemctl daemon-reloadsystemctl restart dovecot Nope, I'm on a debian 7, without systemd. Anyway, I've resolved the issue: I had to set fs.suid_dumpable BEFORE