Bug #4049: Document Contains no data (different this time?)
| From: | marc at marcg dot net | Date: | Wed, 05 Apr 2000 14:59:10 +0000 |
| Subject: | Bug #4049: Document Contains no data (different this time?) | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-17644@lists.php.net to get a copy of this message | ||
From: marc@marcg.net
Operating system: Solaris 2.6
PHP version: 3.0.15
PHP Bug Type: Reproduceable crash
Bug description: Document Contains no data (different this time?)
I'm having the old "Document Contains No Data" problem
on Solaris 2.6 running Apache 1.3.12 w/ SSL, Jserv, and
PHP modules compiled (as DSO).
I have read the FAQ, and previous bug reports and think
this could be a different problem. I've increased the
number of file descriptors in the kernel to 1024. The
ulimit -a output looks like this:
core file size (blocks) unlimited
data seg size (kbytes) 2097148
file size (blocks) unlimited
open files 1024
pipe size (512 bytes 10
stack size (kbytes) 8192
cpu time (seconds) unlimited
max user processes 16389
virtual memory (kbytes) unlimited
I have about 175 (name based) virtual hosts and it
grows more every day. Each virtual host uses
up 3 file descriptors for log files since we write
both to the top level log and the specific virtual
host access log, and once to the specific virtual
host error log.
I can configure the virtual hosts down to 79 and
PHP works fine. I'm testing with a simple "hello
world" script. Anything above 79 virtual hosts
gives me the document contains no data.
I've compiled PHP with MySql, Oracle, Sybase, Postgres,
and xml support turned on. No error messages appear
in any of the log files.
I don't think the file descriptor limit is being reached
since it's set up to 1024.
Any ideas?
-Marc