ID: 22416
Updated by: [EMAIL PROTECTED]
Reported By: jhalla at legion dot org
-Status: No Feedback
+Status: Duplicate
Bug Type: iPlanet related
Operating System: Solaris 8
PHP Version: 4.3.0
-Assigned To:
+Assigned To: wez
New Comment:
The issue is that the (brain-dead) solaris libc has a hard limit of 256
FILE*s.
It is not possible to fopen() more files than that (although open()
works just fine).
Duplicate of Bug #20274.
Previous Comments:
------------------------------------------------------------------------
[2003-03-13 12:44:39] fowler at csufresno dot edu
Still seeing it with php4-STABLE-200303121630.
------------------------------------------------------------------------
[2003-03-13 12:16:09] [EMAIL PROTECTED]
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.
------------------------------------------------------------------------
[2003-03-07 19:55:47] [EMAIL PROTECTED]
jflemer: Thats my guess.
You could try running the "ab" (apache bench) tool to stress test the
dev server and see if the fault occurs.
------------------------------------------------------------------------
[2003-03-07 11:34:39] [EMAIL PROTECTED]
Wez, I've just tried a recent snapshot (stable 200303051430), and I no
longer see this warning. However, without deploying this on a
production server, I cannot get the same hit rate, and the same
variation on php script execution. Do you think that this was just a
symptom of Bug #21713 (leaky descriptors on remote includes)?
------------------------------------------------------------------------
[2003-03-05 18:20:11] fowler at csufresno dot edu
4.3.2-dev (stable latest snap)
Still see it.
"failed to open stream: Too many open files in <b>Unknown</b> on line
0"
Anyone run pstack on the httpd, yet?
------------------------------------------------------------------------
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/22416
--
Edit this bug report at http://bugs.php.net/?id=22416&edit=1
