similar to: indexer-worker out of memory with vsz_limit=750 MB?!

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:

We're running Dovecot in a multipe instance cluster with individual userdb-querys to different LDAP-Servers. As far as I can see there's no way to use the doveadm mailbox command with different Auth-Sockets or different configurations. While root at dobby4:/etc/dovecot# doveadm user -a /var/run/dovecot-xy/auth-master p.heinlein at example.com field value uid 10000 gid 10000

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

Hello, dovecot 2.2.18 on CentOS6.5 Jul 08 11:53:44 dsync-server(system): Fatal: master: service(doveadm): child 32554 returned error 83 (Out of memory (service doveadm { vsz_limit=521 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) I tried increasing to 1 G, 1024 M or even disabling via value of zero -- to no change. Every other service has the famous

Hi, Lately I've seen a few examples of users hitting the vsz_limit (usually trying to "delete" mails i Spam/Junk by moving them to Trash with a large dovecot.index.cache - which resulted in mails left/leaked in the tmp directory of Trash. Sometimes it seems the client gets into a state were it repeatedly tried to sync the client and server state so it does it again and again,

Hello I am looking for help around memory management 1 - How to get the current value of "vsz_limit" from inside a plugin (namely https://github.com/grosjo/fts-xapian/ ) , especially for indexer-worker 2 - Is there a macro or function in dovecot to get the remaining free memory from this vsz value ? Thank you -------------- next part -------------- An HTML attachment was

> On 04/11/2020 05:19 Joan Moreau <jom at grosjo.net> wrote: > > > Hello > I am looking for help around memory management > 1 - How to get the current value of "vsz_limit" from inside a plugin (namely https://github.com/grosjo/fts-xapian/ ) , especially for indexer-worker > 2 - Is there a macro or function in dovecot to get the remaining free memory from this

> On 04/11/2020 05:19 Joan Moreau <jom at grosjo.net> wrote: > > > Hello > I am looking for help around memory management > 1 - How to get the current value of "vsz_limit" from inside a plugin (namely https://github.com/grosjo/fts-xapian/ ) , especially for indexer-worker > 2 - Is there a macro or function in dovecot to get the remaining free memory from this

yes, will do so. It would be nice however to be able to access the actual dovecot config from the plugin side On 2020-11-04 06:46, Aki Tuomi wrote: > You could also add it as setting for the fts_xapian plugin parameters? > > Aki > > On 04/11/2020 08:42 Joan Moreau <jom at grosjo.net> wrote: > > For machines with low memory, I would like to detect how much ram

ok found it, However, it returns me some random number. Maybe I am missing something On 2020-11-06 13:57, Aki Tuomi wrote: > Duh... src/lib/restrict-process-size.h > > Should be in the installed include files as well, > > /usr/include/dovecot/restrict-process-size.h > > Aki > > On 06/11/2020 15:56 Joan Moreau <jom at grosjo.net> wrote: > > Hello >

Bump. Any advice would be most appreciated. Thanks. From: Terence Lau Sent: Wednesday, 24 January 2018 9:59 AM To: 'dovecot at dovecot.org' <dovecot at dovecot.org> Subject: Out of memory on lmtp vsz_limit Hi, We've been getting these types or errors for quite a while now ... Fatal: master: service(lmtp): child 63477 returned error 83 (Out of memory (service lmtp {

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)

Seems I had forgotten that you can use src/lib/restrict.h, in particular, restrict_get_process_size() to figure out the limit. You can combine this with getrusage to find out current usage. Aki > On 06/11/2020 13:26 Joan Moreau <jom at grosjo.net> wrote: > > > yes, will do so. > It would be nice however to be able to access the actual dovecot config from the plugin side

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,

You could also add it as setting for the fts_xapian plugin parameters? Aki > On 04/11/2020 08:42 Joan Moreau <jom at grosjo.net> wrote: > > > For machines with low memory, I would like to detect how much ram remains available before starting indexing a mail, so I can commit everything on disk before the ram is exhausted (and break the process) > I tried to put a

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

Latest Mercurial seems to miss defaults for some services e.g. 'managesieve' and 'lmtp'. Example error message upon start: dovecotdoveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: service(managesieve-login): vsz_limit is too low failed! Regards Thomas

Hello, I would like to ask on suggested vsz_limit values. Is there any way of calculating such values? How should we determine them? I don't want to risk wrong values (and possible errors) on a production system, if I upgrade to 2.0.16 where vsz_limit values are enforced (I read release notes)! If there is no standard way of calculation, could someone please check the following info and

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

How about you try moving the mail into another folder on daily basis, this way the INBOX would stay nice and empty. doveadm move -u archive at company.com Archive MAILBOX INBOX SENTBEFORE todays-date Aki On 16.02.2018 06:19, Terence Lau wrote: > > Bump. > > ? > > Any advice would be most appreciated. > > ? > > Thanks. > > ? > > *From:*Terence Lau >