Odd message, Apache 2.0.43 and PHP (latest snap)

msborg

System: RedHat 8, new build of Apache 2.0.43, and the latest snap of PHP4. Configured and built everything according to the instructions at http://www.php.net/manual/en/install.apache2.php, but when I try to run apache, I get the following error:

httpd: module "/usr/src/build/144344-i386/BUILD/php-4.2.2/sapi/apache2filter/sapi_apache2.c" is not compatible with this version of Apache (found 20020628, need 20020903).
Please contact the vendor for the correct version.

There is no /usr/src/build, nor is there a 144... directory. And the version of the file being referenced (sapi_apache2.c) says it was created 2002-11-10, which should be recent enough. That tells me that something isn't referencing the right files. I just wish I knew how to point 'em in the right direction.

Has anyone seen this error before, or have a clue as to what is causing it?

dalecosp

You might look for this path under the dir built when the package was untarred, the one that's called 'php 4.2.2'/.....

The other thing you might do is attempt to locate this line in httpd.conf and see if there's a better place to point it...

Note that these are all shots in the dark, but if Apache won't boot with it, you're going to have to get a lib it likes....

msborg

That's the odd thing about this: there is no /usr/src/build/ directory, no directory named php-4.2.2. Nothing at all like the error message.

I ran make clean, configure, make, make install as instructed, but I keep getting the same error. I found some pages on Google with the same error, but they were all running Windows.

msborg

Never mind.

Turns out that the LoadModule line in httpd.conf was pointing to an old version of libphp4.so. Once I changed it to point to the new version, the error message went away. 🙂

Sure was an odd message, though!

dalecosp

I'm a *BSD guy, myself, but in the 'ports' system there's a dir called 'work' which is usually the {$BUILDDIR} in the makefile, and inside that dir will be a "name-version.x.x" folder with an entire build/install tree under it. In there are such things as to which that message referred...

The only time I've seen anything like it is when trying to load a DSO into Apache that was configured for the wrong server, such as a mod_php built for compatibility with mod_ssl trying to load into a non-SSL aware apache....

Glad to hear it's working 🙂