Troubleshooting php/apache on tru64
Didier Godefroy <[email protected]> Mon, 03 Nov 2008 14:06:12 +0100
| Newsgroups | gmane.os.tru64.managers |
|---|---|
| Message-ID | <C534B5D4.2417B%[email protected]> |
Hello whoever is left on this list, I hope enough of us are still on this mailing list to continue helping eahc other. I have a problem with php on a tru64 system. I have two systems, that are mostly the same, with 5.1b and they both have an apache 2.0 with php 4.4.x setup already running right now. Without taking this existing setup offline, I am trying to get apache 2.2 (2.2.10 now) working and if possible with php5. On one of the systems, after many attempts, I finally got apache2.2 working and a php 5.2.5 working with it. I put that on port 81 for testing while the existing setup is on port 80, so they coexist just fine. However on that other system, even after finally getting apache2.2 working, php won't work at all, in any version, I tried it with several php4.4 versions and php5.2 versions, even latest dev versions and still nothing. The CLI works fine but not as a module. What happens is that if I start apache without the php module enabled, apache starts normally and it works fine. But when I enable the php module, it won't start. If I start apache with the disabled php module and then let it run while I enable the php module before doing a gentle restart, the it's like php wasn't there (either php4 or php5). There is no core dump to be found, no errors reported in any log, the only message in a log is the normal apache suexec message that says it's enabled, and nothing else. I tried not compiling anything extra, turning off whatever could be turned off to get a minimal version, even disabling the cli and cgi. I have php compiled with debug, actually here is my configure line: configure --prefix=$APACHEROOT \ --with-apxs2=$APACHEROOT/bin/apxs \ --with-config-file-path=$APACHEROOT/cf \ --enable-debug \ --with-experimental-zts \ --disable-cgi \ --disable-cli \ --disable-posix \ --enable-static \ --enable-sigchild \ --enable-memory-limit ($APACHEROOT is of course defined above) This actually was able to work fine on that other system, with php5.2.5. So what could I try to trace what the real problem is? Since there is no crash, no core dump, no errors reported in any way, what can I use to troubleshoot and get to the origin of the cause???? Systems are of course all alphas, with tru64 5.1b. Using the cc compiler and some extensions sometimes force me to use g++ because I don't have cxx. Any hints would be appreciated, -- Didier Godefroy mailto:[email protected]