Re: Running Mod-Perl on Solaris 2.8
On Wed, 28 Mar 2001, G.W. Haywood wrote: > Hi there, > > On Tue, 27 Mar 2001, Melissa Matthews wrote: > > > We have installed mod_perl-1.25 under apache-1.3.14 and Solaris 8, > > > Whenever I browse my test page www.my.com/perl/test.pl, I > > get a Netscape pop-up message stating: > > > > "The document contained no data. > > This often indicates that a child segfaulted. > > > The apache error_log provides the message: > > > >[] [notice] child pid 19616 exit signal Segmentation Fault (11)" > > Yup. I had a problem with XML::Parser, which seg faulted only when run from apache. It may be a similar problem, perhaps? Expat has caused problems for many... Walk through your script and see where it seg faults, if it seg faults in the script... -- Jonathan Gardner [EMAIL PROTECTED] (425)820-2244 x123
Re: Running Mod-Perl on Solaris 2.8
Hi there, On Tue, 27 Mar 2001, Melissa Matthews wrote: > We have installed mod_perl-1.25 under apache-1.3.14 and Solaris 8, > Whenever I browse my test page www.my.com/perl/test.pl, I > get a Netscape pop-up message stating: > > "The document contained no data. This often indicates that a child segfaulted. > The apache error_log provides the message: > >[] [notice] child pid 19616 exit signal Segmentation Fault (11)" Yup. > All the evidence leads me to assume that their is something basic that I am > missing. A LoadModule directive? 73, Ged.
Running Mod-Perl on Solaris 2.8
Title: Running Mod-Perl on Solaris 2.8 We have installed mod_perl-1.25 under apache-1.3.14 and Solaris 8, but have not been completely successful in configuring httpd.conf correctly for mod_perl modules. Whenever I browse my test page www.my.com/perl/test.pl, I get a Netscape pop-up message stating: "The document contained no data. Try again later, or contact the server's administrator." I seem to get this for any file I try irrespective of whether it exists. The apache error_log provides the message: "[] [notice] child pid 19616 exit signal Segmentation Fault (11)" The httpd.conf file was modified in the following way to accommodate mod_perl: AddModule mod_perl.c (very first directive after ClearModuleList) . Alias /perl/ /usr/local/apache_1.3.14/lib/perl/ PerlModule Apache::Registry SetHandler perl-script PerlHandler Apache::Registry PerlSendHeader On Options +ExecCGI allow from all The following was added to define the test.pm perl module: PerlModule ModPerl::test4 SetHandler perl-script PerlHandler ModPerl::test4 All the evidence leads me to assume that their is something basic that I am missing.
