Bug #14401 Updated: Wrong include_path from Apache <Directory> config

ID: 14401 Updated by: vogel@folz.de Reported By: vogel@folz.de -Status: Feedback +Status: Open Bug Type: Apache related Operating System: Linux i386 PHP Version: 4.0.x ... 4.2.1 New Comment: Well, the php4-200207170000 snapshot (which was in the php4-latest tarball) does not build as an RPM. The most important problem (and the show stopper for now) is that the pear installation does not honor the INSTALL_ROOT variable. This defeats building the RPM as a non-root user. Please look at the spec file from Redhat's SRPMs (we use 7.0, 7.1 and 7.2) if you don't know what I mean. Other problems: o ext/imap does not build (configure: error: build test failed. Please check the config.log for details. Looks like a bug in configure: there's no -lc-client in the gcc command line in config.log.) o ext/pgsql does not build (seems fixed in the php4-200207170600 snapshot, will try tomorrow). o DOM support needs libxml version 2.4.14 (says configure), but I have only 2.4.2 and must stay with this, at least at the moment. Previous Comments: ------------------------------------------------------------------------ [2002-07-16 14:18:59] sniper@php.net Try this snapshot: http://snaps.php.net/php4-latest.tar.gz ------------------------------------------------------------------------ [2002-07-16 09:40:54] jflemer@php.net There is another bug w/ include_path (#15374), and a temporary work around was to put this before any include: ini_set('include_path', ini_get('include_path')); Though if you have problems with prepend files, there probably isn't any place you could put this where it would get executed in time. =/ ------------------------------------------------------------------------ [2002-07-10 08:38:41] vogel@folz.de Upgrading to apache-1.3.26 made it worse again. Recompiling the php-4.2.1 module with apache-1.3.26 installed did not improve the situation. We have to restart the apache daemon daily to keep the error rate at a bearable, but still annoying, level. ------------------------------------------------------------------------ [2002-06-18 05:15:44] vogel@folz.de Well, it took some time, but this problem now happened even with version 4.2.1. 4.2.0 and 4.2.1 improved the situation very much: It took 20 days after installation of php-4.2.1 until it happened the first time a few days ago, and since then there are only a few events per day. With late 4.1.x releases the auto_prepend_file seemed to get unuseable for us. Since the first 4.2.1 occurance of the problem, the error rate increased slowly and is now near 50 % when hitting files that use the auto_prepend_file feature. I have to restart the Apache server now, so that our people can access this service again. Background is still the same: apache-1.3.22 and php as a DSO module, both self compiled and used in a redhat-7.0 environment, using the redhat spec files for apache and php. ------------------------------------------------------------------------ [2002-03-28 05:56:47] vogel@folz.de This problem is still present with 4.1.2 and gets more and more annoying with every new release. For some unknown reason a repeated browser "reload" did help in most cases with versions before 4.1.2, but now this almost never gets around the problem. I've changed Version from 4.1.0 to "4.0.x to 4.1.2" and Category from "Configuration issue" to"Apache related" now; maybe I'll get some more response this way (got nothing so far; are we the only ones in the whole world with such a setup?!?). I'm really willing to help to resolve this issue, but I need some guidance on what the developers need. Maybe this problem seems a real corner case to them, but to us it means that we'll have to split up a service that worked on a single virtual host with previous php versions (admitted, not always, but "often enough") into many virtual hosts with the current version of php (4.1.2). Please don't get me wrong (I don't want to put pressure on anybody), I just want to make it clear: If and when we'll have converted our setup, then we'll no longer be able to support anybody tracking down this bug. I think I've said all the important things: the include_path use, that it seems to be strongly related to the auto_prepend_file feature, and that this setup sometimes does work well and sometimes not, without any apparent reason for the change of behaviour. If you have questions about any other details of our setup, then *please* ask. ------------------------------------------------------------------------ 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/14401 -- Edit this bug report at http://bugs.php.net/?id=14401&edit=1