#41138 [Opn->Bgs]: Broken output from PHP scrips (both in mod_php and fastcgi)
| From: | kovyrin at gmail dot com | Date: | Fri, 20 Apr 2007 02:44:42 +0000 |
| Subject: | #41138 [Opn->Bgs]: Broken output from PHP scrips (both in mod_php and fastcgi) | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-111712@lists.php.net to get a copy of this message | ||
ID: 41138
User updated by: kovyrin at gmail dot com
Reported By: kovyrin at gmail dot com
-Status: Open
+Status: Bogus
Bug Type: Unknown/Other Function
Operating System: Debian Linux 4.0 (2.6.17-2-686)
PHP Version: 5.2.1
New Comment:
Sorry guys, looks like it is some bug in linux kernel or in system
libraries: http://blog.kovyrin.net/2007/04/20/sos/
Previous Comments:
------------------------------------------------------------------------
[2007-04-19 21:55:08] kovyrin at gmail dot com
Hm, according to strace, php sends correct data to web servers (tried
all of them with fastcgi). So, moving to web-server debugging...
------------------------------------------------------------------------
[2007-04-19 20:04:31] tony2001@php.net
>Any advices about debugging/etc?
gdb & valgrind should help.
------------------------------------------------------------------------
[2007-04-19 19:52:27] kovyrin at gmail dot com
Just found out that with nginx these errors happen too (rarely, but
they still there)...
Guys, I'm desperate - I need your help. Any advices about
debugging/etc?
------------------------------------------------------------------------
[2007-04-19 19:38:42] tony2001@php.net
>What proxies do you mean if requests from localhost produce "bad"
>results?
How should I know?
>Really don't know how such things could happen
We don't know either, since it works perfectly fine in all
combinations.
------------------------------------------------------------------------
[2007-04-19 17:52:07] kovyrin at gmail dot com
Guys, I have one major update: When I tried to setup the same
configuration (php-fastcgi) using nginx web server (pointed to the same
php socket) everything looks fine. Really don't know how such things
could happen: apache+fcgi = bad, apache+mod_php = bad, lighttpd+fcgi =
bad, nginx with the same fcgi processes = fine.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/41138
--
Edit this bug report at http://bugs.php.net/?id=41138&edit=1