<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 22 May 2013 02:50:02 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Till Klampaeckel' Blog: PHP parse errors with cgi and nginx]]></title>
      <guid>http://www.phpdeveloper.org/news/14191</guid>
      <link>http://www.phpdeveloper.org/news/14191</link>
      <description><![CDATA[<p>
<i>Till Klampaeckel</i> has a very quick post about a problem he was coming across when using PHP as a CGI on the <a href="http://nginx.org/">nginx</a> web server. It was throwing errors ("client prematurely closed connection...") with no evident cause.
</p>
<blockquote>
The issue was a PHP parse error which I overlooked when I added a new file. The weird thing is, I had nothing in the logs (E_ALL, display_errors is off, but all logs are enabled and I tailed them using multitail) and nginx only displayed a blank page. The errors above were in nginx's own log file.
</blockquote>
<p>
The <a href="http://www.vanheusden.com/multitail/">multitail</a> command lets you run the "tail" command on more than one file at a time and view them split out in your console for easier reference. The full error message reads:
</p>
<blockquote>
client closed prematurely connection, so upstream connection is closed too while sending request to upstream, client: a.a.a.a, server: localhost, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/tmp/.fastcgi.till/socket:", host: "localhost"
</blockquote>]]></description>
      <pubDate>Tue, 16 Mar 2010 11:18:59 -0500</pubDate>
    </item>
  </channel>
</rss>
