Project

General

Profile

Bug #754

closed

after update from svn fastcgi can't handle responses >8k???

Added by chernousov about 14 years ago. Updated about 14 years ago.

Status:
Fixed
Priority:
Urgent
Category:
mod_fastcgi
Target version:
-
ASK QUESTIONS IN Forums:

Description

Just updated lighty sources from svn, and each response from fastcgi
backend over 8kbytes fails. I made simple php script which outputs I
something > 8 kbytes and did strace of php and see:


...
write(3, "\1\6\0\1\37\370\0\0Content-type: text/html\r"..., 8192) = 8192
setitimer(ITIMER_PROF, {it_interval={0, 0}, it_value={0, 0}}, NULL) = 0
write(3, "\1\6\0\1\3\345\3\0zzzzzzzzzzzzzzzzzzzzzzzz"..., 1024) = -1 
EPIPE (Broken pipe)
--- SIGPIPE (Broken pipe) @ 0 (0) ---
shutdown(3, 1 /* send */)               = 0
recv(3, "\1\5\0\1\0\0\0\0", 8, 0)       = 8
recv(3, "", 8, 0)                       = 0
close(3)                                = 0
accept(0,  <unfinished ...>
Process 26560 detached

After that i tried to strace lighttpd:


read(7, "\1\6\0\1\37\370\0\0Content-type: text/html\r"..., 8192) = 8192
read(7, 0x80e2a68, 8192)                = -1 EAGAIN (Resource 
temporarily unavailable)

and in logs:


2006-07-16 13:03:00: (mod_fastcgi.c.3461) handling it in mod_fastcgi
2006-07-16 13:03:00: (mod_fastcgi.c.1747) connect succeeded:  7
2006-07-16 13:03:00: (mod_fastcgi.c.2813) got proc: pid: 26559 socket: 
unix:/tmp/php.socket-3 load: 1
2006-07-16 13:03:00: (mod_fastcgi.c.2296) unexpected end-of-file 
(perhaps the fastcgi process died): pid: 26559 socket: 
unix:/tmp/php.socket-3
2006-07-16 13:03:00: (mod_fastcgi.c.3130) response not received, request 
sent: 970 on socket: unix:/tmp/php.socket-3 for /index.php , closing 
connection
2006-07-16 13:03:00: (mod_fastcgi.c.1509) released proc: pid: 26559 
socket: unix:/tmp/php.socket-3 load: 0
2006-07-16 13:03:00: (response.c.113) Response-Header:
HTTP/1.1 500 Internal Server Error

Gentoo linux, php 5.1.4.

#1

Updated by jan about 14 years ago

  • Status changed from New to Fixed
  • Resolution set to fixed

This should be fixed since r1182.

Also available in: Atom