Re: silent failure when I try to use PerlRequire in httpd.conf

1999-12-14 Thread Doug MacEachern
if you build with PERL_TRACE=1 and start the server like so: % setenv MOD_PERL_TRACE=1 % httpd -X you should get some helpful diagnotics. On Sat, 11 Dec 1999, Bill Marrs wrote: Hi, I've been using mod_perl successfully albeit minimally for a couple months now. I'm trying to tune

RE: silent failure when I try to use PerlRequire in httpd.conf

1999-12-14 Thread Gerald Richter
(gdb) bt #0 0x40308503 in boot_DBI () Looks like your Perl installation binaries (DBI in this case), doesn't match with Apache/mod_perl. So the best would be to compile everything Apache/Perl/mod_perl from the sources Gerald

Re: silent failure when I try to use PerlRequire in httpd.conf

1999-12-14 Thread Doug MacEachern
#1 0x403da306 in ?? () from /etc/httpd/modules/libperl.so broken record mod_perl+dso is not a stable mix, try linking mod_perl static /broken record

Re: silent failure when I try to use PerlRequire in httpd.conf

1999-12-13 Thread Bill Marrs
At 10:14 AM 12/11/99 -0800, Cliff Rayman wrote: Stas Bekman wrote: On Sat, 11 Dec 1999, Bill Marrs wrote: Hi, I've been using mod_perl successfully albeit minimally for a couple months now. I'm trying to tune performance and memory usage by consolidating some common

Re: silent failure when I try to use PerlRequire in httpd.conf

1999-12-13 Thread Cliff Rayman
are you sure that there are no other webservers currently running and on port 80? do the 'set args' gdb command with at least the -X parameter before executing run. when you start apache and it blows up, is apache using any other command line arguments such as -DSSL? if so, make sure you use

Re: silent failure when I try to use PerlRequire in httpd.conf

1999-12-13 Thread Bill Marrs
I'm sure there are no other servers. I'm actually stopping my live server to try this. I stop it, change the config file and start it - and it doesn't come up and no server is running. So, I put it back and start it and its OK again. I tried "set args -X" in gdb, and the result was that

Re: silent failure when I try to use PerlRequire in httpd.conf

1999-12-13 Thread Cliff Rayman
I am using PerlRequire successfully on both: Server: Apache/1.3.3 (Unix) mod_perl/1.16 mod_ssl/2.1.2 SSLeay/0.9.0b AND Server: Apache/1.3.9 (Unix) mod_perl/1.21 mod_ssl/2.4.8 OpenSSL/0.9.4 both on linux Linux Redhat 5.2 - kernal - 2.0.36 perl, version 5.005_02 built for i686-linux Are perl and

Re: silent failure when I try to use PerlRequire in httpd.conf

1999-12-13 Thread Stas Bekman
I'm using Red HAT rpms plus mod_perl built on top of that. Your theory about different compiler versions may be on the mark. Using the rpms was a real convenience, but maybe I'm paying for it a bit now. Grab one from http://perl.apache.org/distributions.html (you owe this one to David

silent failure when I try to use PerlRequire in httpd.conf

1999-12-11 Thread Bill Marrs
Hi, I've been using mod_perl successfully albeit minimally for a couple months now. I'm trying to tune performance and memory usage by consolidating some common Perl "use" directives in a PerlRequire statement. However, when I add this line to my Apache config file

Re: silent failure when I try to use PerlRequire in httpd.conf

1999-12-11 Thread Stas Bekman
On Sat, 11 Dec 1999, Bill Marrs wrote: Hi, I've been using mod_perl successfully albeit minimally for a couple months now. I'm trying to tune performance and memory usage by consolidating some common Perl "use" directives in a PerlRequire statement. However, when I add this line to

Re: silent failure when I try to use PerlRequire in httpd.conf

1999-12-11 Thread Cliff Rayman
Stas Bekman wrote: On Sat, 11 Dec 1999, Bill Marrs wrote: Hi, I've been using mod_perl successfully albeit minimally for a couple months now. I'm trying to tune performance and memory usage by consolidating some common Perl "use" directives in a PerlRequire statement. However,

Re: silent failure when I try to use PerlRequire in httpd.conf

1999-12-11 Thread Stas Bekman
make sure no server is running on port 80 or use an alternate config with an alternate port if you are on a production server. cd /usr/local/apache/bin # where ever your binary is gdb httpd set args -X -f /path/to/alternate/serverconfig_ifneeded.conf run it should blow up! then, bt