similar to: auth service: out of memory

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

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:

Hi Timo, since I've upgraded to 2.1.8, solr indexer doesnt work correctly. I see a lot of these errors in logs: Fatal: master: service(indexer-worker): child 9582 returned error 83 (Out of memory (service indexer-worker { vsz_limit=256 MB }, you may need to increase it)) I've tried to set vsz_limit to a lot more, (around 4096 MB) but same problem occurs. thank for your help ! Regards

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:

Hello guys we have Dovecot 2.0.19 and we are getting those errors opening files of dovecot Too many open files, we?ve tried to increase limits in /etc/security/limits Wih ulimits ?a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 63735

Good day Guys Currently on Debian Stretch (2.2.27). This morning we enabled SNI for our clients (file per domain). On going live with the new server configuration, we started getting the following on our shared hosting servers. Jun 30 07:25:04 REMOVED_HOSTNAME dovecot: doveconf: Fatal: block_alloc(134217728): Out of memory Jun 30 07:25:04 REMOVED_HOSTNAME dovecot: config: Fatal:

hello dovecot network hello Timo I've just upgraded to 2.0.8 dovecot and I wonder it should be good value of vsz_limit I put value as 64 M but I do not know if it's good value return are welcome sincerely and happy new year this my dovecot -n ~]# /usr/sbin/dovecot -n # 2.0.8: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32.2-xxxx-grs-ipv6-32 i686 CentOS release 5.5 (Final)

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)

hello guys hello master Timo i build the last release of dovecot on my centos 5 work well and fine but what the correct value for client limit in service auth { client_limit=6000 } and service anvil { client_limit=6000 } my current dovecot -n ks37777 i386]# dovecot -n # 2.1.1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.31.5-xxxx-rt14-ipv6-32 i686 CentOS release 5.7 (Final) auth_mechanisms =

hi guys hi master of "Fu" hi Timo I am having problems to migrate to dovecot dovecot 2.0.18 to 2.1.1 I encounter fatal errors. I created it myself rpms available here http://ns.fakessh.eu/rpms/dovecot-2.1.1-1.centme.el5.src.rpm I can not run dovecot with this config file like this http://ns.fakessh.eu/rpms/dovecot-2.1.1-1.centme.el5.src.rpm i run this config ks37777 ~]# dovecot -n #

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 dear honorable doctor timo reading the list I saw appear a new style for the "writing of INBOX". namely this example mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent }

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hello dovecot network hello timo hello all others reader I do not use the namespace notation in my dovecot configuration. I use Maildir mailboxes that get stuck in /home users. my question is simple I advise you to use the namespace and what should be its own configuration. I use lda to issue the emails my dovecot -n ~]# /usr/sbin/dovecot -n #

Hi Timo and the other directors of the following pigeonhole dovecot sieve I wonder what are the strengths and weaknesses of my config, and what do I need to change to stick more to a best configuration r13151 ~]# /usr/sbin/dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32.2-xxxx-grs-ipv6-32 i686 CentOS release 5.5 (Final) auth_mechanisms = plain login base_dir =

Hi Timo... It's happens some strange issue with my maildir using NFS. If i use a Local Hard disk, i don't get any of this messages about memory error. Jan 12 10:57:50 brc dovecot: imap(alex at exemplo.com.br): Error: opendir(/storage/nfs/3/emexis/messages/ exemplo.com.br/alex/Maildir/.Drafts/new) failed: Cannot allocate memory Jan 12 10:57:51 brc last message repeated 4 times Jan 12

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

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 pasted my config below, hoping someone can point out something obvious. In my dovecot.log I am seeing: Warning: quota: Namespace '' is not Maildir, skipping for Maildir++ quota I am using mysql userdb_* and passing maildir:~/maildir or mdbox:~/mdbox for mail. When its maildir its fine, I had that originally then used dsync to convert to mdbox, updated mysql entry to point to

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,

I am not sure how to get the symbols necessary, however the following is the backtrace (this is Fedora 19 latest everything): Jul 8 03:23:02 MX dovecot: auth: Fatal: block_alloc(2147483648): Out of memory Jul 8 03:23:02 MX dovecot: auth: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x5f437) [0x7f97a952f437] -> /usr/lib64/dovecot/libdovecot.so.0(+0x5f4fe) [0x7f97a952f4fe] ->