Bug #14529 Updated: script doesn't always finish output

ID: 14529 Updated by: yohgaki@php.net -Summary: script doesn't always finish output Reported By: jay1@swift-web.com -Status: Open +Status: Feedback Bug Type: Output Control Operating System: Linux RH 7.2 PHP Version: 4.1.1 New Comment: Anyone have short complete script for this bug? Previous Comments: ------------------------------------------------------------------------ [2002-02-05 16:25:52] pmarks@employees.org I have verified this bug with the latest 4.2.0-dev version. Output problems are still the same: corrupt output with buffering off, and correct output with buffering on, without any HTTP GET variables. (http://ged.dynodns.net/band/index.php?func=article&oid=19288) But only on some pages, for some reason. (E.G. events.php never works) I'm backing up to 4.0.6 to get the site to a production status again. (If 4.0.6 doesn't work, I'll post again...) ------------------------------------------------------------------------ [2002-02-01 19:03:20] pmarks@employees.org I am also experiencing this problem with PHP. On some pages no output is generated whatsoever (http://ged.dynodns.net/band/events.php [events.phps for source]). But the main page (http://ged.dynodns.net/band/index.php [index.phps for source]) works fine until GET var's are passed to it (ie: index.php?func=article&oid=19288), in which case it doesn't work at all. It cuts output off when I have output buffering off, but appears to work OK when I have output buffering enabled. ./configure \ --with-apxs \ --disable-short-tags \ --without-mysql \ --with-pgsql=/usr/pgsql and the php.ini file can be viewed here: http://ged.dynodns.net/band/php.ini I also, do not get any error reports or crashes when running Apache in gdb for debugging. I have all logging in PHP set to E_ALL so I should see any cought source errors, and Apache set to 'debug' so I should get verbose error messages there, and none are showing up for this problem. ------------------------------------------------------------------------ [2002-01-19 23:50:47] jay1@swift-web.com Never thought to look at apache logs. Here is a very common error. [Sat Jan 19 20:49:54 2002] [notice] child pid 14822 exit signal Segmentation fault (11) [Sat Jan 19 21:25:20 2002] [warn] child process 14826 still did not exit, sending a SIGTERM [Sat Jan 19 21:25:24 2002] [error] child process 14826 still did not exit, sending a SIGKILL The first line has at least 20 of them in a row and then the last two occasionally show up at the end of it. It happens on every page load. I was using trans-sid for most tests. Register globals has been Off for most tests as well. No use of ob_end_flush() or ob_end_clean() anywhere in my scripts. (I have output_buffering set to Off - but have tried, On and 4K). I'm not sure what you mean by gdb for running httpd under. I tried using tail on the error_log and when the page locks the error message (above) is what I got. ------------------------------------------------------------------------ [2002-01-19 23:33:04] yohgaki@php.net Please update Version :) Here comes more questions. Do you use trans-sid? (If yes, do you have "register_globals=On"?) Do you use ob_end_flush(), ob_end_clean() anywher in your scripts? I guess you have already checked, but Do you see any error logs for "Apache" and "PHP"? Could you try to run httpd under gdb to see if you get any signal or exit code. ------------------------------------------------------------------------ [2002-01-19 23:29:21] jay1@swift-web.com PHP4.0.6 compiled with the same ./configure line works flawless so it's only happening in 4.1.0 - 4.2.0-dev In linux the pages almost never load simply gives me error reports (some sort of connection error so drops connection), IE loads about 60-70% of the time (but I've noticed it is only displaying old cached information even though I've got it set to nocache in php.ini and tried sending headers to force no caching). I even tried forcing IE not to cache in it's settings but it still does it or else it locks up forever (ALT-CTL-DEL to finally end that task - I've left it for as long as an hour to see if it'd time out first or do something). I've tried reducing the code to force it not to do any includes except the main one. So I could test a much smaller script and it still gives me the problem. Yet if I do a very simple page (like with <? phpinfo() ?>) there is no problems at all. I'm reading through other bugs trying to find similarities with various functions I use and other bugs to see if I can narrow this down. ------------------------------------------------------------------------ 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/14529 -- Edit this bug report at http://bugs.php.net/?id=14529&edit=1