[horde] Login tasks memory exhausted

Luis Felipe Marzagao lfbm.andamentos at gmail.com
Tue Sep 5 03:45:58 UTC 2017



Em 04/09/2017 15:48, Luis Felipe Marzagao escreveu:
>
>
> Em 04/09/2017 12:14, Jan Schneider escreveu:
>>
>> Zitat von Luis Felipe Marzagao <lfbm.andamentos at gmail.com>:
>>
>>> Hi, List:
>>>
>>> horde 5.2.16
>>> imp 6.2.19
>>>
>>> When running the login tasks I get stuck with an HTTP ERROR 500 at 
>>> the address services/logintasks.php?app=imp
>>>
>>> Looking at the logs I get:
>>>
>>> Sep  4 07:52:31 sistema HORDE: [imp] Allowed memory size of 
>>> 134217728 bytes exhausted (tried to allocate 20480 bytes) [pid 25 
>>> 397 on line 402 of "/usr/share/php/Horde/Stream.php"]
>>>
>>> Line 402 is "$read = fread..." below:
>>>
>>>         while (!feof($this->stream) && ($to_end || $length)) {
>>>             $read = fread($this->stream, $to_end ? 16384 : $length);
>>>             $out .= $read;
>>>             if (!$to_end) {
>>>                 $length -= strlen($read);
>>>             }
>>>         }
>>>
>>>         return $out;
>>>     }
>>>
>>>
>>> In php.ini I have:
>>>
>>> memory_limit = 128M
>>>
>>>
>>> Any pointers on how to further debug this?
>>>
>>> Thanks.
>>
>> If you enable DEBUG logging in Horde, you might get an actual 
>> backtrace. Enabling xdebug would do the same, if the error is sent to 
>> the browser.
>>
> Ok. How do I force login tasks to run? Now when I go to 
> .../services/logintasks.php?app=imp it simply returns to IMP´s main 
> screen.
>

Okay, just found out there is a "each connection" login tasks perform 
option.

Turns out the problem was an excessive number of messages in the Trash 
folder (more than 13k). That is why php was running out of memory.

Manually deleting older messages has put things on track again and the 
login tasks are now working just fine.

Tks.

> Tks.



More information about the horde mailing list