Notices tagged with fastcgi
-
@andstatus Perhaps we can consider it an easily worked around bug in #FastCGI and similar out-of-process #PHP runners.
-
@andstatus Wasn't it common to all instances using #FastCGI (and not observed on those using mod_php)?
-
@windigo Are you using #FastCGI? Maybe #Mustard is having the same problem that @andstatus was having. (I think it had to do with needing to have file size specified in the HTTP request.) @mcnalu
-
#notetoself #jessie #nginx #fastcgi remember to :
1) rename /etc/nginx/fastcgi_params to fastcgi.conf
2) Enter the following in top of file:
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
3) include it into the site file by:
include fastcgi.conf;
-
#NoteToSelf: When you add another #PHP extension, restarting #fastcgi / #php-fpm is not enough. You have to restart the web server, too. (at least #Apache, may be able to just reload #Lighttpd; not sure about #Nginx, since I've never used it)
-
@cmhobbs @pztrn I believe newest #andstatus has workaround for failed uploads on #fastcgi enabled servers.
-
@roland Your webserver should be able to read anything it uploads, since it should automatically have user permissions. Exception: if you're using #FastCGI and running your #PHP daemon under a different user, you may need to fiddle with group memberships. CC: @mmn
-
I may have fixed it. If you run into auth problems with your instance when using #FastCGI, take a look at your .htaccess file.
/via @freshadmin
-
I may have fixed it. If you run into auth problems with your instance when using #FastCGI, take a look at your .htaccess file.
/via @freshadmin
-
Have fully switched #mod_php5 -> #fastcgi with #fpm and #mod_ssl :-D It is now way much faster, still "Home" is a little slow.
-
@lnxw48 I have 8 GB RAM on a Quad-Core: AMD Athlon(tm) II X4 605e Processor (/proc/cpuinfo). This should be enough. And I still have #mod_php5 instead of #fastcgi as it crashes to often and consumes to much RAM (yes, some other processes are needed).
-
@gomerx The most recent thing seems to be using long-running interpreter processes connected by sockets. #FastCGI, #WSGI, #SCGI, and more CC: @clacke @speeddefrost