Databases
StackOverflow2013
Postsdbo
POPHP-FPM serving blank pages after fatal php error
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPHP-FPM serving blank pages after fatal php error
    primarykey
    data
    text
    <p>I've got a custom setup of nginx and php-fpm on arch linux. I'll post my configs below. I think I've read the documentation for these two programs front to back about 6 times by now, but I've reached a point where I simply can't squeeze any more information out of the system and thus have nothing left to google. Here's the skinny:</p> <p>I compiled both nginx and php from scratch (I'm very familiar with this, so presumably no problems there). I've got nginx set up to serve things correctly, which it does consistently: php files get passed through the unix socket (which is both present and read-/write-accessible to the http user, which is the user that both nginx and php-fpm run as), while regular files that exist get served. Calls for folders and calls for files that don't exist are both sent to the <code>/index.php</code> file. All permissions are in order.</p> <h2>The Problem</h2> <p>My pages get served just fine until there's a php error. The error gets dumped to nginx's error log, and all further requests for pages from that specific child process of php-fpm return blank. They <strong>do</strong> appear to be processed, as evidenced by the fact that subsequent calls to the file with errors continue to dump error messages into the log file, but both flawed and clean files alike are returned completely blank with a 200 status code.</p> <p>What's almost wilder is that I found if I then just sit on it for a few minutes, the offending php-fpm child process <em>doesn't</em> die, but a new one is spawned on the next request anyway, and the new process serves pages properly. From that point on, every second request is blank, while the other request comes back normal, presumably because the child processes take turns serving requests.</p> <p>My test is the following:</p> <pre><code>// web directory listing: mysite/ --index.php --bad_file.php --imgs/ ----test.png ----test2.png </code></pre> <p>index.php:</p> <pre><code>&lt;?php die('all cool'); ?&gt; </code></pre> <p>bad_file.php*:</p> <pre><code>&lt;?php non_existent_function($called); ?&gt; </code></pre> <p>* <strong>Note:</strong> I had previously posted <code>bad_file.php</code> to contain the line <code>$forgetting_the_semicolon = true</code>, but found that this doesn't actually produce the error I'm talking about (this was a simplified example that I've now implemented on my own system). The above code, however, <strong>does</strong> reproduce the error, as it produces a fatal error instead of a parse error.</p> <p>test calls from terminal:</p> <pre><code>curl -i dev.mysite.com/ # "all cool" curl -i dev.mysite.com/index.php # Redirected to / by nginx curl -i dev.mysite.com/imgs # "all cool" curl -i dev.mysite.com/imgs/test.png # returns test.png, printing gibberish curl -i dev.mysite.com/nofile.php # "all cool" curl -i dev.mysite.com/bad_file.php # blank, but error messages added to log curl -i dev.mysite.com/ # blank! noooooooo!! curl -i dev.mysite.com/ # still blank! noooooooo!! #wait 5 or 6 minutes (not sure how many - probably corresponds to my php-fpm config) curl -i dev.mysite.com/ # "all cool" curl -i dev.mysite.com/ # blank! curl -i dev.mysite.com/ # "all cool" curl -i dev.mysite.com/ # blank! #etc.... </code></pre> <p>nginx.conf:</p> <pre><code>user http; worker_processes 1; events { worker_connections 1024; } http { include mime.types; default_type text/plain; sendfile on; keepalive_timeout 65; index /index.php; server { listen 127.0.0.1:80; server_name dev.mysite.net; root /path/to/web/root; try_files /maintenance.html $uri @php; location = /index.php { return 301 /; } location ~ .php$ { include fastcgi_params; fastcgi_pass unix:/usr/local/php/var/run/php-fpm.sock; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; } location @php { include fastcgi_params; fastcgi_pass unix:/usr/local/php/var/run/php-fpm.sock; fastcgi_param SCRIPT_FILENAME $document_root/index.php; } } } </code></pre> <p>php-fpm.conf:</p> <pre><code>[global] pid = run/php-fpm.pid error_log = log/php-fpm.log log_level = warning [www] user = http group = http listen = var/run/php-fpm.sock listen.owner = http listen.group = http listen.mode = 0660 pm = dynamic pm.max_children = 5 pm.start_servers = 1 pm.min_spare_servers = 1 pm.max_spare_servers = 3 </code></pre> <p>php.ini upon request</p> <h2>In Summary</h2> <p>All pages are served as expected <em>until there's a php error</em>, at which point all subsequent requests to that particular php-fpm child process are apparently processed, but returned as completely blank pages. Errors that occur are reported and continue to be reported in the nginx error log file.</p> <p>If anyone's got any ideas, throw them at me. I'm dead in the water til I figure this out. Incidentally, if anyone knows of a source of legitimate documentation for php-fpm, that would also be helpful. php-fpm.org appears to be nearly useless, as does php.net's documentation for fpm.</p> <p>Thanks!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USkael
    1. USkael
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPHP-FPM serving blank pages after fatal php error
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPHP-FPM serving blank pages after fatal php error
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POPHP-FPM serving blank pages after fatal php error
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload