Mailing List Archive: Cherokee: users

php-cgi, and php.ini. Memory leaks and configuration.

Index | Next | Previous | View Threaded

email at davebv

Nov 2, 2009, 9:41 AM

Post #1 of 5 (108 views)
Permalink

php-cgi, and php.ini. Memory leaks and configuration.

Hi,

I am having problems with php configuration in as FastCGI in Debian with
cherokee 0.99.26.

Mainly my problem is I set up the memory limit in /etc/php5/cgi/php.ini to
64M but the php-cgi processes keep growing in memory.

After some time, the php-cgi have eaten all my memory server.

I just found out that passing -c /etc/php5/cgi/php.ini as the argument in
the interpreter (/usr/bin/php-cgi -c /etc/php5/cgi -b
/tmp/cherokee-php.socket) seems to comply with the limits I established in
the php.ini.

The thing is that I do not know if it is a problem my configuration file, or
it is problem of the default behavior of cherokee not picking the right
file.

Any help would be much appreciated.
THanks,
David.

alvaro at octality

Nov 2, 2009, 10:34 AM

Post #2 of 5 (104 views)
Permalink

Re: php-cgi, and php.ini. Memory leaks and configuration. [In reply to]

On 02/11/2009, at 11:41, Site Mail wrote:

> I just found out that passing -c /etc/php5/cgi/php.ini as the
> argument in the interpreter (/usr/bin/php-cgi -c /etc/php5/cgi -b /
> tmp/cherokee-php.socket) seems to comply with the limits I
> established in the php.ini.
>
> The thing is that I do not know if it is a problem my configuration
> file, or it is problem of the default behavior of cherokee not
> picking the right file.

Actually, it looks like a PHP installation issue. Cherokee launches
php-cgi, it's up the the interpreter the configuration file it uses.

By the way, I'd strongly encourage you to set up php-cgi to use a TCP
socket instead of a Unix socket; experience has taught us, that's a
better way to run it.

Cheers!

--
Octality
http://www.octality.com/

_______________________________________________
Cherokee mailing list
Cherokee[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee

email at davebv

Nov 2, 2009, 10:43 AM

Post #3 of 5 (104 views)
Permalink

Re: php-cgi, and php.ini. Memory leaks and configuration. [In reply to]

Thank you for the quick answer.

In fact, in info.php I see the configuration is taken from the same file in
both cases (the right file) So I do not know why in "top" the php.cgi
processes shows up using more than 100M sometimes.

I just set up the fascgi as tcp (I did not upgrade from old version of
wizzards).

By the way, I am using php 5.2.6, maybe this is the problem, I am going to
try with dotdeb repository, which is 5.2.11, and see if the issue stops.

THanks for the help.

On Mon, Nov 2, 2009 at 7:34 PM, Alvaro Lopez Ortega <alvaro[at]octality.com>wrote:

> On 02/11/2009, at 11:41, Site Mail wrote:
>
> I just found out that passing -c /etc/php5/cgi/php.ini as the argument in
>> the interpreter (/usr/bin/php-cgi -c /etc/php5/cgi -b
>> /tmp/cherokee-php.socket) seems to comply with the limits I established in
>> the php.ini.
>>
>> The thing is that I do not know if it is a problem my configuration file,
>> or it is problem of the default behavior of cherokee not picking the right
>> file.
>>
>
> Actually, it looks like a PHP installation issue. Cherokee launches
> php-cgi, it's up the the interpreter the configuration file it uses.
>
> By the way, I'd strongly encourage you to set up php-cgi to use a TCP
> socket instead of a Unix socket; experience has taught us, that's a better
> way to run it.
>
> Cheers!
>
> --
> Octality
> http://www.octality.com/
>
>

email at davebv

Nov 2, 2009, 10:45 AM

Post #4 of 5 (104 views)
Permalink

Re: php-cgi, and php.ini. Memory leaks and configuration. [In reply to]

In fact, I was using 5.2.11 already, my bad I looked at the wrong package.

On Mon, Nov 2, 2009 at 7:43 PM, Site Mail <email[at]davebv.com> wrote:

> Thank you for the quick answer.
>
> In fact, in info.php I see the configuration is taken from the same file in
> both cases (the right file) So I do not know why in "top" the php.cgi
> processes shows up using more than 100M sometimes.
>
> I just set up the fascgi as tcp (I did not upgrade from old version of
> wizzards).
>
> By the way, I am using php 5.2.6, maybe this is the problem, I am going to
> try with dotdeb repository, which is 5.2.11, and see if the issue stops.
>
> THanks for the help.
>
>
> On Mon, Nov 2, 2009 at 7:34 PM, Alvaro Lopez Ortega <alvaro[at]octality.com>wrote:
>
>> On 02/11/2009, at 11:41, Site Mail wrote:
>>
>> I just found out that passing -c /etc/php5/cgi/php.ini as the argument in
>>> the interpreter (/usr/bin/php-cgi -c /etc/php5/cgi -b
>>> /tmp/cherokee-php.socket) seems to comply with the limits I established in
>>> the php.ini.
>>>
>>> The thing is that I do not know if it is a problem my configuration file,
>>> or it is problem of the default behavior of cherokee not picking the right
>>> file.
>>>
>>
>> Actually, it looks like a PHP installation issue. Cherokee launches
>> php-cgi, it's up the the interpreter the configuration file it uses.
>>
>> By the way, I'd strongly encourage you to set up php-cgi to use a TCP
>> socket instead of a Unix socket; experience has taught us, that's a better
>> way to run it.
>>
>> Cheers!
>>
>> --
>> Octality
>> http://www.octality.com/
>>
>>
>

email at davebv

Nov 3, 2009, 11:44 PM

Post #5 of 5 (95 views)
Permalink

Re: php-cgi, and php.ini. Memory leaks and configuration. [In reply to]

I do not know why was that, I removed the xcache package and it seems all
the php-cgi behavior is back to normal, as far as I can tell, there is no
more memory leak or growth. I will look into this to see if the problem is
really solved.

On Mon, Nov 2, 2009 at 7:45 PM, Site Mail <email[at]davebv.com> wrote:

> In fact, I was using 5.2.11 already, my bad I looked at the wrong package.
>
>
> On Mon, Nov 2, 2009 at 7:43 PM, Site Mail <email[at]davebv.com> wrote:
>
>> Thank you for the quick answer.
>>
>> In fact, in info.php I see the configuration is taken from the same file
>> in both cases (the right file) So I do not know why in "top" the php.cgi
>> processes shows up using more than 100M sometimes.
>>
>> I just set up the fascgi as tcp (I did not upgrade from old version of
>> wizzards).
>>
>> By the way, I am using php 5.2.6, maybe this is the problem, I am going to
>> try with dotdeb repository, which is 5.2.11, and see if the issue stops.
>>
>> THanks for the help.
>>
>>
>> On Mon, Nov 2, 2009 at 7:34 PM, Alvaro Lopez Ortega <alvaro[at]octality.com>wrote:
>>
>>> On 02/11/2009, at 11:41, Site Mail wrote:
>>>
>>> I just found out that passing -c /etc/php5/cgi/php.ini as the argument
>>>> in the interpreter (/usr/bin/php-cgi -c /etc/php5/cgi -b
>>>> /tmp/cherokee-php.socket) seems to comply with the limits I established in
>>>> the php.ini.
>>>>
>>>> The thing is that I do not know if it is a problem my configuration
>>>> file, or it is problem of the default behavior of cherokee not picking the
>>>> right file.
>>>>
>>>
>>> Actually, it looks like a PHP installation issue. Cherokee launches
>>> php-cgi, it's up the the interpreter the configuration file it uses.
>>>
>>> By the way, I'd strongly encourage you to set up php-cgi to use a TCP
>>> socket instead of a Unix socket; experience has taught us, that's a better
>>> way to run it.
>>>
>>> Cheers!
>>>
>>> --
>>> Octality
>>> http://www.octality.com/
>>>
>>>
>>
>

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com