Php – How to run mod_php and fastcgi side-by-side

You can tell haproxy to stop sending connections to a server. For that, you have to specify "http-check disable-on-404" in your haproxy config, and have your web server return 404 (and nothing else) to haproxy's health checks. If haproxy sees this, it will mark the server as "NOLB", meaning that it's excluded from the load balancing, but still finishes its connections, and still accepts persistent connections requesting it. That way, all new clients go to other servers.

The simplest way to do this is to check for an "alive" file, which, once removed, will cause a 404 to be returned (hence the choice of this return code). Of course, developping a more complete server-side application to respond to health-checks is better !

Here are some possibilities for this:

1. You have enabled some kind of opcode cache with mod_php
2. You have turned on mod_cache in apache
3. You are using TCP connection method in php-fpm.

Post back with these details.

Also, try apache + mod_fastcgi + apc + php-fpm.

And, if you are using the if condition in nginx for rewrite rules, switch to try_files instead. if sometimes has performance issues.