Re: [PHP4BETA] Segfault with large Apache
| From: | Khimenko Victor | Date: | Tue, 04 Jan 2000 05:10:29 +0000 |
| Subject: | Re: [PHP4BETA] Segfault with large Apache | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-8894@lists.php.net to get a copy of this message | ||
3-Jan-00 23:05 you wrote:
> I'm trying to get up a development server at work with all sorts of
> general goodies, since most of our web stuff is all over the place. I got
> Apache 1.3.9 and mod_ssl 2.4.9 (openssl 0.9.4), compiled in as DSO's.
> I added in mod_perl 1.21 just fine as a DSO, and it works great.
> It's a fairly beefy server, and we have Postgres, Mysql, Oracle 8i, and
> DB2 all installed (all latest versions). The configure script run for php4
> was:
[skipped]
> The architecture is intel x86, 128M of ram, SCSI, etc, running Mandrake
> Linux 6.1 (RedHat derivitave).
> Are there any known problems with my current setup? I'd rather not
> downgrade to php3, and I need all the database drivers for development.
> Any ideas?
Check libraries used in build process of all modules. Use gcc from RedHat
(Mandrake's gcc is BUGGY). If you ended up with two dbm libraries linked in
(Mandrake as well as RedHat includes THREE different INCOMPATIBLE versions:
Berkeley DB1, Berkeley DB2 & GDBM; you should include only one of them;
it's especially hard due perl usage - if perl is linked with both Berkeley DB
and GDBM then at least make sure that libperl.so is loaded after all other
modules: perl does not need neither Berkeley DB not GDBM but build process
links them both to executable) it can be your problem.