Why use FPM ?

By admin ( December 17, 2011 at 5:43 am) · Filed under Web Server, ,

FPM IS FastCgi ! “F.P.M.” stands for “FastCGI Process Manager”

CGI is really slow. FastCGI, as its name indicates… Is not slow. CGI
is slow for the simple reason you have to completely launch PHP and all
its libraries & etc. … whenever FastCGI launches “hanging” PHP
processes that are waiting for requests to spend their time doing
something more useful than “hanging” in memory :)

But this is the very fact why there is currently a problem with running
many websites with FastCGI : it’s memory consuming if you have so many hanging processes waiting for queries (as a php process is ~ 15MB, and even more when parsing a wordpress website ! (~35MB !) ).

(note : “hanging” here does not mean the unix “hang” signal, huh, it
just means hanging as anything in real life)

Comments

Nginx : child 3947 exited on signal 11

By admin ( May 5, 2011 at 9:56 am) · Filed under Linux Centos, Web Server, , ,

Are you a noob in nginx ? or php-fpm  ?
Stuck with strings in php-fpm error log.

May 05 13:38:26.087569 [WARNING] [pool www] child 3912 exited on signal 11 (SIGSEGV) after 12.275636 seconds from start
May 05 13:38:26.089376 [NOTICE] [pool www] child 3931 started
May 05 13:38:29.964830 [WARNING] [pool www] child 3881 exited on signal 11 (SIGSEGV) after 32.302211 seconds from start
May 05 13:38:30.049895 [NOTICE] [pool www] child 3936 started
May 05 13:38:36.689665 [WARNING] [pool www] child 3928 exited on signal 11 (SIGSEGV) after 10.764960 seconds from start
May 05 13:38:36.691593 [NOTICE] [pool www] child 3947 started
May 05 13:38:39.960130 [WARNING] [pool www] child 3931 exited on signal 11 (SIGSEGV) after 13.870757 seconds from start
May 05 13:38:39.961723 [NOTICE] [pool www] child 3953 started
May 05 13:38:46.212047 [WARNING] [pool www] child 3947 exited on signal 11 (SIGSEGV) after 9.520457 seconds from start
May 05 13:38:46.213457 [NOTICE] [pool www] child 3973 started

The service is suddenly stuck with unkown cause.
It has been 12 hours looking for the solutions, I tried to increase nginx worker and number of max php-fpm daemons with no luck.

The solution is simple, you need to update the php-fpm.
Yes, it was funny. Why suddenly needs to update ? anyway, may be it is a bug . But the point is it is work.

# yum –enablerepo=webtatic update php-fpm

Then, restart your php-fpm

# service php-fpm restart

 

Comments