Re: Problem with modperl
Hello Escario, Tuesday, April 10, 2001, 6:41:49 PM, you wrote: EJ Hello, EJ I've compiled mod_perl as a Apache module with apxs after I installing EJ apache. EJ So I load mod_perl with this in the httpd.conf : EJ LoadModule Perllibexec/modperl.so EJ Next apache restart correctly ... EJ When I try to get any of the web page, Netscpe return me : EJ This document contains no data ... EJ but why ? EJ thanks I've got similiar effects. It helped me USE_LARGEFILES=0 (at perl Makefile.PL of mod_perl) as I compiled earlier Perl without large files. I use Apache 1.3.19, mod_perl 1.25, perl 5.6. -- Best regards, Mirek mailto:[EMAIL PROTECTED]
Re: Problem with modperl
Hi there, I've had similar problems before with a stock install of Redhat 6.x and their installation of apache + mod_perl (dso) + php It's been a long time now but if my memory serves me correctly (probably not) loading mod_perl before php in the httpd.conf file worked (in some instances). Read the guide regarding mod_perl as dso. You should probably try to compile it into apache. Escario Julien wrote: Here's exactly the line in httpd.conf : LoadModule perl_modulelibexec/libperl.so I'm gone on http://perl.apache.org/guide/ but nothing is said on my case. I forgot a detail : I'm using mod_vhost_alias , is mod_perl compatible ? On apache restart here's what I get in error_log : [Tue Apr 10 19:45:15 2001] [notice] SIGHUP received. Attempting to restart [Tue Apr 10 19:45:16 2001] [notice] Apache/1.3.19 (Unix) mod_perl/1.25 PHP/4.0.4pl1 configured -- resuming normal operations And now when trying to get a doc : [Tue Apr 10 19:46:23 2001] [notice] child pid 1500 exit signal Segmentation fault (11) [Tue Apr 10 19:47:23 2001] [notice] child pid 1503 exit signal Segmentation fault (11) So it's because Apache is SegFaulting ? Why can I solve this problem ? "G.W. Haywood" wrote: Hi there, On Tue, 10 Apr 2001, Escario Julien wrote: This document contains no data ... but why ? Could be lots of reasons. Often it's because Apache is segfaulting. Look in the error_log, it might tell you. Have you read the guide? http://perl/apache.org/guide 73, Ged. -- Daniel Bohling NewsFactor Network
Re: Problem with modperl
Hi there, On Tue, 10 Apr 2001, Escario Julien wrote: This document contains no data ... but why ? Could be lots of reasons. Often it's because Apache is segfaulting. Look in the error_log, it might tell you. Have you read the guide? http://perl/apache.org/guide 73, Ged.
Re: Problem with modperl
Here's exactly the line in httpd.conf : LoadModule perl_modulelibexec/libperl.so I'm gone on http://perl.apache.org/guide/ but nothing is said on my case. I forgot a detail : I'm using mod_vhost_alias , is mod_perl compatible ? On apache restart here's what I get in error_log : [Tue Apr 10 19:45:15 2001] [notice] SIGHUP received. Attempting to restart [Tue Apr 10 19:45:16 2001] [notice] Apache/1.3.19 (Unix) mod_perl/1.25 PHP/4.0.4pl1 configured -- resuming normal operations And now when trying to get a doc : [Tue Apr 10 19:46:23 2001] [notice] child pid 1500 exit signal Segmentation fault (11) [Tue Apr 10 19:47:23 2001] [notice] child pid 1503 exit signal Segmentation fault (11) So it's because Apache is SegFaulting ? Why can I solve this problem ? "G.W. Haywood" wrote: Hi there, On Tue, 10 Apr 2001, Escario Julien wrote: This document contains no data ... but why ? Could be lots of reasons. Often it's because Apache is segfaulting. Look in the error_log, it might tell you. Have you read the guide? http://perl/apache.org/guide 73, Ged.
Re: Problem with modperl
Hi again, On Tue, 10 Apr 2001, Escario Julien wrote: I forgot a detail : I'm using mod_vhost_alias , is mod_perl compatible ? It probably isn't the problem, I use it too. But don't take my word for it. [Tue Apr 10 19:46:23 2001] [notice] child pid 1500 exit signal Segmentation fault (11) So it's because Apache is SegFaulting ? Yup. Why can I solve this problem ? Look in the file .../mod_perl/SUPPORT in your filesystem. You need to reduce everything to its simplest and work up from there. There's a good debugging section in the Guide. I'd start by compiling static instead of DSO, that's been known to cause problems in the past, but you might want to search the List archives for mention of the combination of modules etc. that you are using. There may be someone on the list who has more experience of your setup, I've never used PHP. You *did* compile your Perl with the same compiler that you used for mod_perl etc... didn't you? 73, Ged.
