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

Timo Sirainen tss at iki.fi
Tue May 17 23:01:27 UTC 2016


> On 15 May 2016, at 17:28, aki.tuomi at dovecot.fi wrote:
> 
>> 
>> On May 15, 2016 at 2:48 PM Peer Heinlein <p.heinlein at heinlein-support.de> wrote:
>> 
>> 
>> 
>> 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)
>> [0x7f37027b84b7] -> /usr/lib/dovecot/libdovecot.so.0(+0xab851)
>> [0x7f37027b9851] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0)
>> [0x7f37027b89a6] -> /usr/lib/dovecot/libdovecot.so.0(+0xd0405)
>> [0x7f37027de405] -> /usr/lib/dovecot/libdovecot.so.0(+0xa56e2)
> 
> Any chance for you to get a corefile and run gdb command 'bt full' on it?

Setting CORE_OUTOFMEM=1 environment will produce core dump on out of memory (a huge one of course).



More information about the dovecot mailing list