ID: 14401 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open -Bug Type: *Configuration Issues +Bug Type: Apache related Operating System: Linux i386 -PHP Version: 4.1.0 +PHP Version: 4.0.x ... 4.1.2 New Comment:
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. Previous Comments: ------------------------------------------------------------------------ [2002-02-19 04:18:44] [EMAIL PROTECTED] Status update: o The problem persists with php-4.1.1. o The problem is _not_ a concurrency, but more like a caching problem: It does happen even with only one current user of this server, but only if this user requests files from different subdirectories. o This is the only virtual host where we use varying include_paths and we really need auto_prepend_file there, so I cannot say if it happens without auto_prepend_file. (I haven't had the time to set up a new virtual host for testing this.) o From Feb. 01, 2002 until yesterday (Feb. 18), and with php-4.1.1 installed at the end of Jan. 2002, it happens in about 25 % of the requests of files where the auto_prepend_file feature is active. ------------------------------------------------------------------------ [2002-01-16 10:59:08] [EMAIL PROTECTED] Having looked somewhat deeper into this issue I want to add that the include path problem seems limited to include files that get loaded via the auto_prepend_file directive. Explicit "include" or "require" statements seem to work as they should. But please take this with a grain of salt, because this may be a result of the fact that files with auto_prepend_file-loaded headers have far more hits than those with explicit "include"s. ------------------------------------------------------------------------ [2001-12-10 08:51:33] [EMAIL PROTECTED] We have a virtual host here where the include_path varies per directory. We configure this in the Apache config (php as a DSO module) like this: <Directory /var/www/html/dir1> php_value include_path ".:/var/www/html/dir1/lib" </Directory> <Directory /var/www/html/dir2> php_value include_path ".:/var/www/html/dir2/lib" </Directory> (and many more) We have tried this with many versions of Apache 1.3.x and php-4.0.x (up to apache-1.3.22 / php-4.1.0RC3) and all combinations exhibit the same problem: If there are two or more concurrent users that access different directories of this virtual host, one or more of them get pages with php errors, because the php scripts don't get the include files they need. The error messages show clearly that the include files were searched via a wrong include_path, i.e. one out of the other <Directory ..> sections of the same virtual host. We used both standard Redhat 7.x apache and php RPMs, as well as self-compiled RPMs based on Redhat's SRPMs, all with the same result/problem. If you need more specific information, please ask. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=14401&edit=1
