vsz_limit is 18,447 PB

[Dan Langille]

On Sep 7, 2014, at 4:39 AM, Jiri Bourek <bourek at thinline.cz> wrote:

> On 6.9.2014 22:38, Dan Langille wrote:
>> 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: imap(dan): Fatal: master: service(imap): child 71153 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes })
>> Sep  6 03:59:41 mailjail dovecot: imap(dan): Fatal: pool_system_realloc(2097152): Out of memory
>> Sep  6 03:59:41 mailjail dovecot: imap(dan): Fatal: master: service(imap): child 67732 returned error 83 (Out of memory (service imap { vsz_limit=256 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump)
>> 
> 
> Check the message again - it says vsz_limit=256MB

Yes, I saw that…. I can’t explain why I didn’t question the rest of the output.

> 
>> Background: I’m in the only user on this system, but this server is accessed by my phone, my laptop, my tablet, and perhaps a web interface.
>> 
> 
>> 
>> But there are some interesting values when I look at the output of doveconf.  Specifically, vsz_limit is 18,447 PB… yeah, that’s pretty big.
>> 
>> service imap-login {
>>  vsz_limit = 18446744073709551615 B
>> }
>> 
> 
> According to your log it was process “im ap" what ran out of memory. You are showing configuration for imap-login - they are not the same thing, see http://wiki2.dovecot.org/Design/Processes

My errror, sorry.  OK, here’s imap:

service imap {
  chroot =
  client_limit = 1
  drop_priv_before_exec = no
  executable = imap
  extra_groups =
  group =
  idle_kill = 0
  privileged_group =
  process_limit = 1024
  process_min_avail = 0
  protocol = imap
  service_count = 1
  type =
  unix_listener login/imap {
    group =
    mode = 0666
    user =
  }
  user =
  vsz_limit = 18446744073709551615 B
}

Still the same value…  why not 265MB?

> Not sure if this behaviour is a bug or something that is to be expected when you run out of VSZ limit in imap process - that needs to be answered by someone more knowledgeable

It seems quite common:

 $ doveconf | grep vsz_limit
default_vsz_limit = 256 M
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
  vsz_limit = 18446744073709551615 B
[dan at mailjail:~] $ 

Thank you.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 333 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://dovecot.org/pipermail/dovecot/attachments/20140908/478822f3/attachment.sig>