ID:               24666
 Updated by:       [EMAIL PROTECTED]
 Reported By:      dhunter at uta dot edu
-Status:           Open
+Status:           Feedback
 Bug Type:         Apache related
 Operating System: Solaris 8
 PHP Version:      4.3.2
 New Comment:

Take at a look @ your apache's primary error log file, see if there are
any messages from php or reports of crashed apache children.


Previous Comments:
------------------------------------------------------------------------

[2003-07-22 22:26:14] dhunter at uta dot edu

I've had php logging on the entire time. That's the reason I haven't
been able to track this down. We have been using php extensively for a
long time and I've never experienced this before. When a page prints
blank the access log entry is:

www.uta.edu 64.12.96.203 - - [22/Jul/2003:21:59:00 -0500] "GET
/uta/current HTTP/1.1" 200 5 "http://www.uta.edu/"; "Mozilla/4.0
(compatible; MSIE 5.0; AOL 8.0; Windows 98; DigExt)"

The same page should report 22430 bytes like the following:

www.uta.edu 67.66.182.19 - - [22/Jul/2003:22:09:57 -0500] "GET
/uta/current HTTP/1.1" 200 22430 "-" "Mozilla/5.0 (X11; U; Linux i686;
en-US; rv:1.4b) Gecko/20030516 Mozilla Firebird/0.6 StumbleUpon/1.73"

What could have changed between 4.3.1 and 4.3.2 that could cause this.

------------------------------------------------------------------------

[2003-07-21 18:03:13] [EMAIL PROTECTED]

Try to enable logging of php errors and see if the php error contains
any errors that could explain the cause for the blank pages.

------------------------------------------------------------------------

[2003-07-20 17:35:31] dhunter at uta dot edu

Thanks for the input. I wasn't able to reproduce the error in debug
mode. Maybe increased traffic increases the frequency of occurrence.
Here is what I have done. I rebuilt all of the web server components,
apache, ssl, php, using a newer version of gcc (3.2.3), and I removed
some of php's configuration options. As I mentioned I wasn't able to
reproduce the problem in apache's debug mode, and gdb didn't have
anything to report. The problem continues to occur with the rebuilt
components, so I am continuing to use 4.3.1 for now. I'll build the
snapshot and see if the error is still present. 
Summary:
- plain html pages are ok.
- php pages randomly print blanks regardless of code.
- occurs with apache 1.3.27 or 1.3.28, and php 4.3.2 on sparc solaris
8
- php 4.3.1 works great

------------------------------------------------------------------------

[2003-07-16 21:05:01] [EMAIL PROTECTED]

Oopps, made a slight mistake, run it like:

# gdb httpd
(gdb) run -X -DSSL


------------------------------------------------------------------------

[2003-07-16 21:01:24] [EMAIL PROTECTED]

Could you try if you can reproduce this when you run apache like this:

# gdb httpd -X

(if you need SSL, add -DSSL there)

You should test the snapshot on separate instance/machine.
e.g. have another apache with PHP build from the snapshot
running in other port. (separate development server would be best
choice though :)



------------------------------------------------------------------------

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/24666

-- 
Edit this bug report at http://bugs.php.net/?id=24666&edit=1

Reply via email to