SV: [PHP4BETA] SV: [PHP-DEV] PHP 4.0 Bug #3497 Updated: Apache 1.3.11 gets SIGSEGV immediately qafter start
| From: | Johan Ekenberg | Date: | Thu, 17 Feb 2000 21:24:31 +0000 |
| Subject: | SV: [PHP4BETA] SV: [PHP-DEV] PHP 4.0 Bug #3497 Updated: Apache 1.3.11 gets SIGSEGV immediately qafter start | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-10412@lists.php.net to get a copy of this message | ||
> i'm pretty sure that the SIGSEGV is the parent apache-process
> is fixed in CVS!
>
> tc
Thies:
Unfortunately I was never able to run the "16 feb CVS" long enough to
verify this. The children started segfaulting pretty badly, mostly
on different MySQL related stuff, but also when getting pictures,
cgi's - you name it. Some users started reporting the well known
"PHP Fatal error: Maximum execution time of 20 seconds exceeded
in [no active file] on line 0" error.
At this time I bailed out and returned to beta 2. Unfortunately I
can't take the time to do serious debugging on these servers
since they're in heavy production use, and it's hard to emulate
the high load on a test server.
What's more, as you yourself reported, the PHP_AUTH_USER/PHP_AUTH_PW
vars where out of order. I never saw a reply to your post about that,
did it get corrected?
Sorry for this very unprecise report but I can't afford to have
the servers running in degraded mode for a longer time to do precise
debugging. Bad thing too. When the PHP_AUTH_* stuff gets fixed I wan't
to make another try, running for a few minutes, look up what produces
segfaults, put back the old server (beta2) and start the current CVS
on a different port to try to reproduce the crasches.
Isn't it a strange thing that beta 2 is the stablest version I can find?
Somewhere mid December things started to go bad with mysql_*() that
produces crasches on my machines. Apart from an occasional parent
apache-process total crash, beta 2 seems quite stable and functional here.
I've got a surveillance script running every minute that fires up Apache
again when parent-pid crashes happen - every few hours or so.
All the best and thanks to all the developers for not giving up!
---
For the record:
http://bugs.php.net/bugs.php3?id=2866
http://bugs.php.net/bugs.php3?id=3108
System is Linux Slackware-4 (libc5) running SMP (2xPIII) kernel 2.2.14.
Apache 1.3.9, mod_ssl-2.4.9, mod_perl-1.21
MySQL is 3.23.8 --static.
---
/Johan Ekenberg