ID: 9850
Updated by: sniper
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Feedback
Bug Type: Apache related
Assigned To:
Comments:
1. delete config.cache
2. add --enable-debug into your configure line
3. after configure: 'make clean ; make ; make install'
4. then try generating gdb backtrace:
# gdb /path/to/httpsd
(gdb) run -X
And then (if) it crashes:
(gdb) bt
and copy/paste the output into this bug report using the
web interface.
--Jani
Previous Comments:
---------------------------------------------------------------------------
[2001-03-19 19:06:36] [EMAIL PROTECTED]
I am trying to upgrade from php-4.02 and have this problem. Below are the specs on my
system. It works
find with 4.02, but when I use the exact same procedure to build-4.04p1 the following
happens.
./configure, make and make install on php complete without errors. httpsd starts and
immediately dies
with no error messages and nothing has been found in any logs.
When I say it starts and dies I mean:
./httpsd start
gives an OK but
ps -aux|grep ht
shows no httpd processes running no matter how fast I type but
./httpsd start;ps -aux|grep ht
shows 10 httpd processes, but will have dies before they can be tested again.
The only variable would seem to be the difference between 4.02 and 4.04p1. After a
careful look at the
requirements and dependency I can't fine the cause. Unfotunately php.net doesn't seem
to make earlier
versions so I can't same how matters stand on 4.03 (Does anybody have this?).
The system is running Red Hat 6.2 with updates
linux kernel 2.2.17-14smp
Apache is RH secure server 3.1.2
glibc 2.1.3-22
The php configure command line use for both 4.02 and 4.04p1 is:
./configure --with-apxs --with-kerberos=/usr/kerberos/ --with-imap --with-mysql
--with-ldap
---------------------------------------------------------------------------
ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at http://bugs.php.net/?id=9850&edit=2
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
