Which ec2 instance size are you using? If it's a micro instance, then that is the nature of that size. Amazon intentionally limits the cpu of that size instance. On Thu, Apr 28, 2011 at 4:19 AM, Param <kalerparamvir@gmail.com> wrote: > Hi, > > I am facing an issue with PHP-FPM. I have configured it to run with > Nginx on Amazon EC-2. The load on the server increases suddenlyby dcampano - Php-fpm Mailing List - English
It sounds like the problem the OP is having is that he is not running configure with ALL of the previous flags. Follow Sammie's instructions and you should be fine. Your ./configure statement needs to have all the previous flags PLUS the one additional flag to enable fpm. On Wed, Sep 15, 2010 at 4:42 PM, Diemuzi <diemuzi@gmail.com> wrote: > This doesn't appear to be an FPM Related issby dcampano - Php-fpm Mailing List - English
Jerome, I like the idea that you had for renaming the processes (this makes it similar to nginx too). Do you think this will get merged in for the next point release? On Aug 20, 1:37 pm, Jérôme Loyet <m...@fatbsd.com> wrote: > 2010/8/20 Thomas Fritz <fritz...@gmail.com>: > > > > > > > > > 2010/8/20 Jérôme Loyet <m...@fatbsd.com> > > >by dcampano - Php-fpm Mailing List - English
Thanks for the tip, I was able to get it working by taking the script from Remi's rpm and modifying it. I guess maybe the init.d script that comes with source doesn't work on centos. Can anyone confirm this? On Sun, Aug 29, 2010 at 10:45 PM, Brandon Amaro <omega13a@fedtrek.com>wrote: > Have you tried the php-fpm from Remi's repo? I have no problem with the > init.d script that comeby dcampano - Php-fpm Mailing List - English
Hey everyone, I'm having some problems with the init.d script on a fresh CentOS 5 install. It seems like it is having a problem creating the PID file. I have not made any modifications to the init.d script, just copied it exactly after the compile/make from sapi/fpm/init.d.php-fpm. Running the php-fpm command by itself runs fine. Any one have any thoughts or similar problems? Davyby dcampano - Php-fpm Mailing List - English
This is great news! Thanks for your hard work! Davy On Wed, May 26, 2010 at 11:29 AM, Antony Dovgal <tony@daylessday.org> wrote: > Hello all. > > After a short discussion with Rasmus and Johannes (how's maintaining PHP > 5.3 branch) it was agreed that FPM > can't break anything serious and even though 5.3 is a bugfix branch, it's > safe to add FPM there. > > Whichby dcampano - Php-fpm Mailing List - English
Hey Jerome, I think he might have been confused because you called it /status but in the curl examples you were calling it with status.php. Also, just wanted to thank you for your well done examples. Thanks Davy 2010/2/24 Jérôme Loyet <ml@fatbsd.com> > as you wish. > > I recommand not to choose a .php extension in order to NOT confuse > with a classic PHP file. This alsoby dcampano - Php-fpm Mailing List - English
The new php-fpm that is built into PHP 5.3 supports a /status command to get information about the pool. I'm wondering if anyone knows if there is an easy way to query this status from a shell script using netcat or something similar? Thanks Davyby dcampano - Php-fpm Mailing List - English
What does this new status module do? Is there any documentation somewhere for it? Also, Alex, the "no input file specified" occurs in Nginx when Nginx cannot find the php page that it is trying to find, usually due to this variable not being set or pointing to the wrong path: fastcgi_param SCRIPT_FILENAME /var/www/html$fastcgi_script_name; Davy 2010/1/28 Jérôme Loyet <ml@fatbby dcampano - Php-fpm Mailing List - English
Alex, Are you running any other extensions? Probably the best place to get it figured out though is by debugging it with gdb as Alexey mentioned. The good part is that it sounds like it is quickly reproducible. On Sat, Jan 23, 2010 at 4:21 PM, Michael Shadle <mike503@gmail.com> wrote: > This is true. I was getting confused with SIGCHLD. Some people have > posted on here with veryby dcampano - Php-fpm Mailing List - English
>Recycling in only 9 seconds seems pretty quick. It looks like he is receiving a SIGSEGV which would be a segmentation fault, so it wouldn't be related to recycling. I haven't tried the 5.3.x code, but it appears that it is probably something in your application code that is buggy. On Sat, Jan 23, 2010 at 3:47 PM, Michael Shadle <mike503@gmail.com> wrote: > Recycling in only 9 secoby dcampano - Php-fpm Mailing List - English
Does anyone what the defaults are for fastcgi_connect_timeout and how it works? It seems like at first when one of my upstream backends was down, that it waited 10-11 seconds before trying an alternate, but then after a few failures it started only waiting 3 seconds to try the alternate. Davyby dcampano - Nginx Mailing List - English
Does anyone what the defaults are for fastcgi_connect_timeout and how it works? It seems like at first when one of my upstream backends was down, that it waited 10-11 seconds before trying an alternate, but then after a few failures it started only waiting 3 seconds to try the alternate. Davyby dcampano - Nginx Mailing List - English
If I have a configuration like this for FastCGI, is it possible to determine which server responded to the request? Is there a variable that would tell this that I can use for nginx's log? upstream phpservers { server 10.1.1.50:5201; server 10.1.1.51:5201; } Davyby dcampano - Nginx Mailing List - English