PHP dying

This isn’t really an Nginx problem, but hopefully someone can help me.
I’m running PHP as fcgi using spawn-fcgi.

I have a PHP script that resizes an image, but when I try to access this
page, it seems to get partway through processing the page, then the PHP
process handling the request dies. I receive in the browser the output
of the script as far as it got, and in the error log I get:

2010/01/12 15:29:33 7654#0: *15 readv() failed (104: Connection reset
by peer) while reading upstream, client: 127.0.0.1, server:
www.photosite.com, request: “POST /admin/upload.xhtml HTTP/1.0”,
upstream:
“fastcgi://unix:/home/djeyewater/webapps/spawn-fcgi/php-fastcgi.sock:”,
host: “www.photosite.com”, referrer:
http://www.photosite.com/admin/upload.xhtml

Other php pages work okay.

I’m guessing I need to change a timeout or max size setting somewhere?

Thanks

Dave

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,40290,40290#msg-40290

Probably you need to examine PHP logs (or even spawn-fcgi logs/output
to stderr) - problem should be clearly visible there. There are really
lots of reason for PHP to die :slight_smile:

On Tue, Jan 12, 2010 at 11:36 PM, djeyewater [email protected]
wrote:

Thanks

Dave


Aleksej Besciokov
EMail/JID: [email protected]
phone: +7 495 7853149

proforg Wrote:

Probably you need to examine PHP logs (or even
spawn-fcgi logs/output
to stderr) - problem should be clearly visible
there. There are really
lots of reason for PHP to die :slight_smile:

I added the following to my php.ini:

log_errors = on
error_log = /home/djeyewater/logs/php-errors.log

and modified the spawn-fcgi init script like so:

$FCGI_DAEMON -s $FCGI_SOCKET -C $PHP_FCGI_CHILDREN -P $FCGI_PIDFILE –
$FCGI_PROGRAM -c /home/djeyewater/webapps/php_fcgi/lib/php.ini
2>>/home/djeyewater/logs/php-fcgi-err.log

Not sure if that is the correct way to read stderr from spawn-fcgi?

Anyway, after restarting php I got no errors (from the page I’m having
problems with) recorded in the php error log or the spawn-fcgi stderr
file. Still get the same error in the nginx error log for the site, and
obviously the page still isn’t working.

Could you advise me on how I’d get the error message to be recorded?

Thanks

Dave

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,40290,40465#msg-40465

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs