ID: 40967
User updated by: Webbed dot Pete at gmail dot com
-Summary: Please read the report... not one that needs php
script ;)
Reported By: Webbed dot Pete at gmail dot com
Status: Bogus
Bug Type: Reproducible crash
Operating System: Linux
PHP Version: 5.2.1
New Comment:
"It doesn't make much sense to keep the report in the current state"
I certainly agree! :)
"I can name you thousand reasons for this behaviour and all of
them has nothing to do with PHP."
Well, in this case it's clearly not the interpreter itself but MAY be
related to the PHP environment variables used for setup.
As you suggested, we'll ask our network to report any similar
situation(s).
Thanks much!
Previous Comments:
------------------------------------------------------------------------
[2007-04-03 21:10:15] [EMAIL PROTECTED]
500 Error is not PHP problem.
Please reopen the report when/if you have more information on the issue
and how to reproduce it.
It doesn't make much sense to keep the report in the current state,
because I can name you thousand reasons for this behaviour and all of
them has nothing to do with PHP.
------------------------------------------------------------------------
[2007-04-03 21:02:52] Webbed dot Pete at gmail dot com
Tony,
Sorry but the boilerplate response doesn't match the bug report.
I've already diagnosed the 'bug' as far as possible. Apparently the
real issue had more to do with a strange interaction with the run
environment more than with the code itself.
For now this might as well be placed on hold until someone else finds a
similar situation, because my host provider lost the 'buggy' version of
the php5-cgi-run script.
For now, my hope is that this report will at least help others track
down the problem when they see similar attributes.
------------------------------------------------------------------------
[2007-04-03 18:47:08] [EMAIL PROTECTED]
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves.
A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external
resources such as databases, etc. If the script requires a
database to demonstrate the issue, please make sure it creates
all necessary tables, stored procedures etc.
Please avoid embedding huge scripts into the report.
------------------------------------------------------------------------
[2007-04-02 09:06:51] Webbed dot Pete at gmail dot com
[To answer your question directly: the getarray() function retrieves an
array from an in-memory global cache var]
Actually, the getarray() function is immaterial; it's never called when
the system is set in "crash mode". I put a debug trace-to-file on the
line before and after the array_merge() call, and also as the first
element of the getarray() function. The debug trace inside getarray() is
never called while getarray() is embedded in the array_merge() call.
Now the good-yet-a-bit-frustrating news: we've resolved this issue, in
an unusual way. The solution may be informative to other hard to
track-down bugs.
Bottom line: the array_merge() problem went away when our webhost
company rebuilt the custom php5 cgi script that runs php5 in the
phpSuExec environment! How the execution environment can have any impact
on array_merge() is beyond me, but that's the facts.
How we found this. Told here for the benefit of others who may find
similarly troubling issues:
I discovered another 500 error that *did* point to execution
environment (crash on chdir() with 100% perfect permissions) and
reported it to our sitehost tech support, who escalated it to top tier
support.
The chdir() crash was recognized as a phpSuExec issue, specifically "a
problem with our php5 cgi script that launches PHP5 with custom
configuration options which resulted in premature end of script headers
errors."
Unfortunately, the corrupted cgi script was not saved for analysis.
They simply ran their rebuild-php5-environment script, overwriting the
whole thing.
In retrospect, they suspect an update to cPanel may have corrupted the
script. The conversation continues: if an update did this, then perhaps
other servers in their farm have the same problem and can be diff'd with
mine. They don't keep backups of these scripts since they can be
auto-gen'd.
I hope that helps! I'm still amazed that *anything* in the execution
environment can impact the operation of something as benign as
array_merge().
Pete
------------------------------------------------------------------------
[2007-04-01 22:51:22] judas dot iscariote at gmail dot com
Then tell use what the.. the getarray() function does **exactly**
------------------------------------------------------------------------
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/40967
--
Edit this bug report at http://bugs.php.net/?id=40967&edit=1
