From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.3)
Description of problem:
Customer runs a very simple script:
Script fails with error:
'failed to open stream: HTTP request failed! '
Script runs correctly in command line, but fails when run as a script
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Copy script
2. Run from web
Actual Results: Worked fine for me, customer can't get it to work.
Expected Results: Should show the text:
I have spoken with Joe Orton about this:
I asked customer to recompile with '--enable-debug' (as recommended here:
), but still had issue
Can you confirm whether the customer has configured httpd with a large
number of log files, and is running the server with an increased
ulimit -n? That is key as to whether this has anything to do with the
upstream bug you reference.
The customer does indeed have a large number of logfiles and has
modified their ulimit -n.
How does this affect the prognosis/potetnial fix?
Thank you for your time,
Yes, thank you, that confirms that this is problem described in the
upstream bug report. I will make test packages available shortly
which should work around the issues reported.
Packages which include a workaround for this issue are available for
test purposes from the following location:
Please note that even with this workaround, there are still many
places where PHP does not correctly handle fd numbers greater than
1024 and may behave unreliably in such configurations: notably
socket_select and stream_select, also any use of the curl extension.
We applied the rpms last night and they seemed to fix the problem.
Thank you all for the help.
Is this fix going to be in future releases?
Thanks for testing this out. This fix is scheduled for inclusion in a
future RHEL3 update.
Sorry I hit reload.
Just getting myself added so I know when the patch is released. :)
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.