[Dovecot] Out of memory after upgrading to dovecot 2.0.21
Arnaud Abélard
arnaud.abelard at univ-nantes.fr
Tue Feb 5 20:15:28 EET 2013
On 02/05/2013 06:44 PM, Reindl Harald wrote:
> hard to say without config-details
>
> shared prcoess or one per connection?
One per connection, around 1000 connections right now.
> in case of shared 256 MB is really really low
I changed the vsz_limit to 512MB and it seems better, but I'm still
surprised my mailbox actually hit the memory limit since I doubt it's
most used one.
Arnaud
>
> Am 05.02.2013 18:38, schrieb Arnaud Abélard:
>> Hrm... exactly when I pressed sent, dovecot started giving me more information:
>>
>> master: Error: service(imap): child 22324 returned error 83 (Out of memory (service imap { vsz_limit=256 MB }, you
>> may need to increase it))
>>
>> Is that why the imap processes were running out of memory or is that just another symptom of the same problem? How
>> come we never had that problem with the older version of dovecot 2.0 (sorry, i can't remember which one we were
>> running...).
>>
>> Arnaud
>>
>> On 02/05/2013 06:33 PM, Arnaud Abélard wrote:
>>> 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
>>>
>>> /vmail/a/b/abelard-a/dovecot.index.cache is 224MB big and my mailbox is
>>> 72% full of 8GB.
>>>
>>> any idea of what is happening?
>
--
Arnaud Abélard
jabber: arnaud.abelard at univ-nantes.fr / twitter: ArnY
Administrateur Système
DSI Université de Nantes
-
More information about the dovecot
mailing list