Project

General

Profile

Actions
Copy link

Bug #2282

closed

PHP-Script always times out at 1 minute

Added by lifeofguenter over 13 years ago. Updated about 8 years ago.

Status:
Invalid
Priority:
Normal
Category:
-
Target version:
-
ASK QUESTIONS IN Forums:

Description

Problem:
Scripts that do not send any data for over a minute die. Even though max_execution_time etc. are set higher than a minute.

No PHP-Error is shown (empty error.log) - no server reply - e.g. no response headers.

Env:
> Lighttpd 1.5/svn
> PHP-FPM 5.3.4 (xcache)
-> Intel Xeon E5430 / 8GB RAM

Reproduce:
$ time curl -i http://localhost/foo.php
curl: (52) Empty reply from server

real 1m0.950s
user 0m0.005s
sys 0m0.009s

Expected:
$ time curl -i http://localhost/foo2.php
HTTP/1.1 200 OK
Content-type: text/html
Content-Length: 0
Date: Sun, 26 Dec 2010 19:41:31 GMT
Server: lighttpd

real 0m30.049s
user 0m0.005s
sys 0m0.007s

I did not have this with Apache + mod_php/eaccelerator so this seems to be a new lighttpd + php-fpm issue.

Also maybe something to do with: http://wiki.nginx.org/HttpFcgiModule#fastcgi_read_timeout (at least default there is 60s, too) - but did not find anyway to configure this via lighttpd.

Files

Download all files
foo.php (17 Bytes) foo.php lifeofguenter, 2010-12-26 20:55
foo2.php (16 Bytes) foo2.php lifeofguenter, 2010-12-26 20:55
php-fpm.conf.txt (951 Bytes) php-fpm.conf.txt lifeofguenter, 2010-12-26 21:04
phpinfo__-1.jpg (25.2 KB) phpinfo__-1.jpg lifeofguenter, 2010-12-26 21:07
Actions
Copy link
 #3

Updated by lifeofguenter over 13 years ago

thanks to nitrox (via irc) who gave me following hint:

server.max-read-idle has to be raised (default 60s) - which I did according to php's max_execution_time.

now the empty reply comes much later but it still comes:

$ time curl -i http://localhost/foo.php
curl: (52) Empty reply from server

real 6m0.971s
user 0m0.010s
sys 0m0.024s

I get 6min every time, this is too predictable to be a random server/network connection loss.

Actions
Copy link
 #4

Updated by Olaf-van-der-Spek over 13 years ago

  • Target version set to 1.4.29
Actions
Copy link
 #5

Updated by Olaf-van-der-Spek over 13 years ago

  • Target version deleted (1.4.29)

What version is this about?

Actions
Copy link
 #6

Updated by lifeofguenter over 13 years ago

lighttpd 1.5 (svn 2776)

Actions
Copy link
 #7

Updated by Olaf-van-der-Spek over 13 years ago

1.5 isn't supported (AFAIK). Can you reproduce this on 1.4?

Actions
Copy link
 #8

Updated by gstrauss about 8 years ago

  • Status changed from New to Invalid

The default for server.max-write-idle is 360 seconds, or 6 minutes, so that is your new timeout issue. Please configure that appropriately to your needs. BTW, in addition to server.max-write-idle and server.max-read-idle, please also see server.max-keep-alive-idle.

Actions
Copy link

Also available in: Atom