similar to: dovecot-1.2.12 core

Having a problem with a mailbox. I've been trying to rebuild - but doveadm force-resync crashes. This is mdbox with sis. doveadm purge -u dmiller at amfes.com doveadm(dmiller at amfes.com): Panic: file istream.c: line 466 (i_stream_grow_buffer): assertion failed: (stream->max_buffer_size > 0) doveadm(dmiller at amfes.com): Error: Raw backtrace:

FreeBSD-12 Dovecot-2.3.5 I am having problems with one use Mar 25 21:30:12 imap(gau.mon at crownkenya.com)<91364><U7qCZO+ECfCaRh6E>: Fatal: master: service(imap): child 91364 killed with signal 6 (core dumped) Mar 25 21:30:14 imap(gau.mon at crownkenya.com)<2381><moHYZO+EDvCaRh6E>: Fatal: master: service(imap): child 2381 killed with signal 6 (core dumped) Mar 26 06:29:26

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.doe at crownkenya.com)<82746><wg80zdqEy+eaTXHr>: Panic: file mempool-system.c: line 137 (pool_system_realloc): assertion failed: (old_size == (size_t)-1 || mem == NULL || old_size <= malloc_usable_size(mem)) Mar 24 20:56:08 imap(john.doe at

I thought I had cleared out the corruption I had before - perhaps I was mistaken. What steps should I take to help locate these issues? Currently using 2.1rc1. I see the following errors in my logs, including out of memory and message size issues (at 15:30): Jan 4 05:17:17 bubba dovecot: indexer-worker(user1 at domain.com): Error: Raw backtrace:

Hello, I though this bug should be reported, although there is workaround already made and in use. Dovecot 2.2.10 crashes into out of memory error when there is defined system users (userdb+passdb) and own virtual users (userdb+passdb). Removing either one solves the issue and Dovecot is working as it should. When memory leak (I replaced pw_init and gr_init with the version that is found

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

Hi, I have some out of memory errors in my logs (file errors.txt attached) I'm using dovecot 2.0.19, I can see some memory leaks fix in hg after the 2.0.19 release but they seem related to imap-login service, I attached my config too, is something wrong there? Should I really increase the limit based on my settings? Can these commits fix the reported leak?

Hi. In my setup exim delivers mails to dovecot using LMTP. In one LMTP session exim can deliver up to 200 recipients (batch_max set to that value). Now the problem is that sometimes 256MB is not enoug for dovecot lmtp to handle incoming emails. My questions: - how big memory limit should be for lmtp? I was thinking that lmtp (more or less) simply reads from one descriptor and writes to file,

Do these errors indicate a memory leak? I see them in the logs a few times per day on each of our servers, running CVS dovecot-20060924... Oct 8 22:21:30 mail38b dovecot: auth(default): block_alloc(): Out of memory Oct 8 22:21:30 mail38b dovecot: child 6391 (auth) returned error 83 (Out of memory) Oct 9 20:05:05 mail38b dovecot: auth(default): pool_system_realloc(): Out of memory Oct 9

On 2017-05-02 09:35, Aki Tuomi wrote: > On 2017-05-02 10:20, Tom Sommer wrote: >> On 2017-05-01 19:26, Aki Tuomi wrote: >>>> On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote: >>>> >>>> >>>> I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my >>>> dmesg >>>> and /var/log/messages

Hello, I have here a problem with managesieve. With the login about webmail (roundcube) comes here in the log: --snip dovecot: managesieve-login: Fatal: pool_system_realloc(4294967296): Out of memory dovecot: managesieve-login: Fatal: master: service(managesieve-login): child 10157 returned error 83 (Out of memory (service managesieve-login { vsz_limit=1024 MB }, you may need to increase it))

Hello! I have used Dovecot for more than a year without problems, but today it just crashed with this message: dovecot: Apr 09 21:23:38 Panic: file mempool-system.c: line 104 (pool_system_realloc): assertion failed: (old_size == (size_t)-1 || mem == NULL || old_size <= malloc_usable_size(mem)) dovecot: Apr 09 21:23:38 Error: Raw backtrace: /usr/local/sbin/dovecot [0x805757c] ->

Hello, I've upgraded our servers and now dovecot seems to be running out of memory when accessing my own mailbox (and only mine, which is in a way pretty fortunate): dovecot: imap(abelard-a): Error: mmap() failed with file /vmail/a/b/abelard-a/dovecot.index.cache: Cannot allocate memory imap(abelard-a): Fatal: pool_system_realloc(131072): Out of memory

Hi, First I have this warning when configuring: configure: WARNING: sys/ucred.h: present but cannot be compiled configure: WARNING: sys/ucred.h: check for missing prerequisite headers? configure: WARNING: sys/ucred.h: see the Autoconf documentation configure: WARNING: sys/ucred.h: section "Present But Cannot Be Compiled" configure: WARNING: sys/ucred.h: proceeding with the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 23 Jun 2014, Bernhard Schmidt wrote: > > 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. Do those users have mailboxes extra ordinary large or is one message of them extra ordinary large? Jun 23 12:53:21 lxmhs74 dovecot: imap(USER):

We're running 2.2.24 with fts_lucene and I wonder why indexer-working can be out-of-memory even with vsz_limit=750 MB ?! Peer May 15 12:14:51 dobby4 dovecot: indexer-worker(user at example.com): Fatal: pool_system_realloc(134217728): Out of memory May 15 12:14:51 dobby4 dovecot: indexer-worker(user at example.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xaa4b7)

I encountered this error on FreeBSD 9.3 with dovecot2-2.2.13_3 Short version; vsz_limit is 18,447 PB and it ran out of RAM. Suggestions for change? Sep 6 03:39:32 mailjail dovecot: imap(dan): Panic: file imap-fetch.c: line 556 (imap_fetch_more): assertion failed: (ctx->client->output_cmd_lock == NULL || ctx->client->output_cmd_lock == cmd) Sep 6 03:39:32 mailjail dovecot:

Hi, I am looking for deb packages of libvirt with version 1.2.12. It would be a great help if you can help me here. The following packages are in need : 1. libvirt-daemon-system (1.2.12) 2. libvirt-clients (1.2.12) 3. libvirt-daemon (1.2.12) If this is not the right place to contact, please redirect me to correct mailing group. Any help would be highly appreciated ! Thanks in advance ! Best

Anyone seen this and know how to fix it? (note the Assembler messages at the end). Thanks in advance: server# make linux26 cc -I. -O4 -g -Wall -DBUILDING_TONEZONE -m64 -DSTANDALONE_ZAPATA -DZAPTEL_CONFIG=\"/etc/zaptel.conf\" -DHOTPLUG_FIRMWARE -c -o gendigits.o gendigits.c cc -o gendigits gendigits.o -lm ./gendigits > tones.h cc -I. -O4 -g -Wall -DBUILDING_TONEZONE -m64

Hi, We have been trying to get live migration working between two xen boxes running libvirt 1.2.12, However i seem to be getting the following error root@libvirt-xen1:~# virsh migrate --live trusty-image qemu+ssh://192.168.13.9/system --copy-storage-all --verbose --persistent --undefinesource root@192.168.13.9's password: error: unsupported flags (0x48) in function