[horde] How much memory to set memory_limit to? (SOLVED)

[Michael M Slusarz]

Quoting Pro Green European <pro_green_european at yahoo.com>:

>> ----- Original Message -----
>> From: Pro Green European <pro_green_european at yahoo.com>
>> To: "horde at lists.horde.org" <horde at lists.horde.org>
>> Cc:
>> Sent: Monday, November 28, 2011 10:37 AM
>> Subject: Re: [horde] How much memory to set memory_limit to?
>>
>>
>>> ----- Original Message -----
>>> From: Michael M Slusarz <slusarz at horde.org>
>>> To: horde at lists.horde.org
>>> Cc:
>>> Sent: Saturday, November 26, 2011 12:21 AM
>>> Subject: Re: [horde] How much memory to set memory_limit to?
>>>
>>> Quoting Simon Brereton <simon.brereton at buongiorno.com>:
>>>
>>>> On 25 November 2011 16:20, Pro Green European
>>>> <pro_green_european at yahoo.com> wrote:
>>>>> Hi.
>>>>>
>>>>> I've set 512M as the default memory_limit value in PHP for my  
>>>>> webmail system.
>>>>>
>>>>> How much should I really allocate? I think 512M is quite a lot of memory.
>>>>>
>>>>> I've tried with 384M, but it didn't take long before I started  
>>>>> seeing memory exhausted messages in Apache's error log.
>>>>
>>>> This was discussed at length a few weeks ago because of an issue I was
>>>> having.  You should be able to find the thread in the archive.  Some
>>>> were ok with 256, some recommended 512 and some even proposed 1024.
>>>> Currently I'm up to 384, but I can go to 512 if I get more out of
>>>> memory messages.
>>>
>>> And as I previously mentioned, all of these values seem  
>>> exceedingly high.  Especially for viewing a message.
>>>
>>> The only possibility of reaching this kind of memory use is by  
>>> using the SQL VFS backend.  This is now highly discouraged - use  
>>> the filesystem VFS backend instead.
>>>
>>> michael
>>
>>
>> Hi.
>>
>> I do use the filesystem for VFS.
>>
>> This is the error message with the exhausted memory error message:
>>
>> PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted  
>> (tried to allocate 59 bytes) in  
>> /usr/share/pear/Horde/Cache/Storage/File.php on line 78,
>>
>> These errors started appearing when I updated to the latest  
>> version, and when trying to update the .procmailrc file.
>>
>>
>> Regards,
>> /PGE
>
> This was a configuration issue, in the hostspec setting for procmail  
> (ingo), I forgot to set the proper hostname of the server to  
> contact. Nevertheless, generating memory errors for this kind of  
> configuration error is a bit confusing.

Uhhhhh.... how is this supposed to work.  **YOU** misconfigured Horde  
to cause it to go into an infinite loop, that eventually exhausted the  
memory pool.  How are we supposed to safeguard against that, let alone  
report it?

We can try to sanity-check certain configuration values, especially  
when they are easily seen to potentially cause problems.  But we can't  
foresee every issue potentially caused by an admittedly bad  
configuration.

michael

___________________________________
Michael Slusarz [slusarz at horde.org]