You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Grant <em...@gmail.com> on 2005/05/12 20:29:08 UTC
mod_perl causing seg faults in apache2?
Hello, I've been suffering from intermittent segmentation faults in my
apache2 error_log for quite a while now. It seems to be worst during
peak traffic hours. Here's what they look like:
[notice] child pid 13189 exit signal Segmentation fault (11)
I'm getting maybe 100 of these per day. If the user agent is
Firefox/Linux it will just stop loading the next page. If it's IE it
will display a 404-like browser page.
My consultant thinks it's a mod_perl problem. I'm running Gentoo
Linux along with apache-2.0.54 and mod_perl-1.99.17. All of my
software is 100% up-to-date as per the Gentoo portage tree. These
errors have been consistent across 3 different servers.
Does anyone have any ideas on this?
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Stas Bekman <st...@stason.org>.
Grant wrote:
>>>>mp2bug says:
>>>>
>>>>CGI : 3.05, 3.09
>>>>
>>>>so I uninstalled CGI and I'm left with:
>>>>
>>>>CGI : 3.05
>>>>
>>>>and Gentoo thinks there is no CGI installed. Could this be the
>>>>problem? Gentoo not properly removing CGI-3.05?
>>>
>>>I'm not using Gentoo, so I can't tell. May be you've installed it manually
>>>(perl Makefile.PL && make && make install), in which case Gentoo will
>>>certainly not see it.
>>>
>>>In any case you should upgrade to CGI-3.10, which has some mp2 related
>>>fixes in it.
>
>
> Looking over error_log more closely, the Registry.pm error is just
> something I get when I'm transitioning between 2.0.0rc5 and 1.99.17.
> The real problem is the bareword error. Could that be due to the old
> CGI package?
CGI.pm doesn't use those constants
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> > > mp2bug says:
> > >
> > > CGI : 3.05, 3.09
> > >
> > > so I uninstalled CGI and I'm left with:
> > >
> > > CGI : 3.05
> > >
> > > and Gentoo thinks there is no CGI installed. Could this be the
> > > problem? Gentoo not properly removing CGI-3.05?
> >
> > I'm not using Gentoo, so I can't tell. May be you've installed it manually
> > (perl Makefile.PL && make && make install), in which case Gentoo will
> > certainly not see it.
> >
> > In any case you should upgrade to CGI-3.10, which has some mp2 related
> > fixes in it.
Looking over error_log more closely, the Registry.pm error is just
something I get when I'm transitioning between 2.0.0rc5 and 1.99.17.
The real problem is the bareword error. Could that be due to the old
CGI package?
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> > mp2bug says:
> >
> > CGI : 3.05, 3.09
> >
> > so I uninstalled CGI and I'm left with:
> >
> > CGI : 3.05
> >
> > and Gentoo thinks there is no CGI installed. Could this be the
> > problem? Gentoo not properly removing CGI-3.05?
>
> I'm not using Gentoo, so I can't tell. May be you've installed it manually
> (perl Makefile.PL && make && make install), in which case Gentoo will
> certainly not see it.
>
> In any case you should upgrade to CGI-3.10, which has some mp2 related
> fixes in it.
Could the CGI package be to blame for the bareword error I'm seeing?
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Stas Bekman <st...@stason.org>.
Grant wrote:
> mp2bug says:
>
> CGI : 3.05, 3.09
>
> so I uninstalled CGI and I'm left with:
>
> CGI : 3.05
>
> and Gentoo thinks there is no CGI installed. Could this be the
> problem? Gentoo not properly removing CGI-3.05?
I'm not using Gentoo, so I can't tell. May be you've installed it manually
(perl Makefile.PL && make && make install), in which case Gentoo will
certainly not see it.
In any case you should upgrade to CGI-3.10, which has some mp2 related
fixes in it.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> > Hi Stas,
> >
> > I removed it with the Gentoo mechanism:
> >
> > emerge -C mod_perl
> >
> > What makes you think it wasn't removed properly? It is my current
> > 1.99.17 installation that has Registry.pm under Apache2. 2.0.0rc5
> > installed it to:
> >
> > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm
>
> Ah, OK, I thought your *current* was the one you have the problem with.
>
> > I don't understand why error_log said it couldn't find that module.
> > The above is in @INC. Maybe I should just try it again?
>
> Please do so.
>
> Your errors are very confusing, you said the error was that it couldn't
> find ModPerl/Registry.pm, but when I asked you where it is you said it's:
>
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/Apache2/ModPerl/Registry.pm
>
> which is wrong. It shouldn't be there if you have uninstalled 1.99.17
>
> and then you said:
>
> > and according to the logs the new one was installed here:
> > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm
>
> but apparently it is not there, so your log is wrong.
mp2bug says:
CGI : 3.05, 3.09
so I uninstalled CGI and I'm left with:
CGI : 3.05
and Gentoo thinks there is no CGI installed. Could this be the
problem? Gentoo not properly removing CGI-3.05?
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> May be you aren't loading it, while you think that you do. Please observe:
>
> % perl -le 'use warnings; use strict; use Apache2::Const; \
> sub foo {return Apache2::Const::OK }'
>
> % perl -le 'use warnings; use strict; \
> sub foo {return Apache2::Const::OK }'
> Bareword "Apache2::Const::OK" not allowed while "strict subs" in use at -e
> line 1.
> Execution of -e aborted due to compilation errors.
I see what you mean but I've got 'use Apache2::Const;' in
Interchange/Link.pm so I have no idea what's going on.
> Try:
>
> warn $INC{'Apache2/Const.pm'}
>
> somewhere in your code. It should show you the file that was loaded.
>
> If everything else fails, if you can use the problem reporting skeleton
> [1] and reproduce the problem with it (adjusting it by adding some minimal
> code). Please send it here and we will look at it).
>
> [1] linked from:
> http://perl.apache.org/docs/2.0/user/help/help.html#Problem_Description
I really appreciate your help. Something tells me further debugging
will be just as fruitless. I'll just have to wait until a newer
mod_perl shows up in portage. Hopefully my vistors aren't using IE.
Haha.
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Stas Bekman <st...@stason.org>.
Grant wrote:
[...]
>>>A weird thing: I'm getting those same bareword errors in error_log
>>>but I haven't even updated Interchange::Link yet. That module doesn't
>>>say "Apache2::Const:OK" anywhere in it and I'm still getting the same
>>>error.
>>
>>That means that you
>>- either still have pre-mp2-RC5 Apache2/Const somewhere.
>>- or the code that uses it didn't compile that constant. i.e., you (or
>>whoever wrote it) didn't do:
>>
>> use Apache2::Const -compile => 'OK';
>>
>>before using it.
>
>
> I replaced:
>
> use Apache::Const;
>
> with:
>
> use Apache2::Const -compile => 'OK';
>
> in Link.pm with the same results. How can I find out if I have an old
> Apache2/Const? I definitely only have these on the system:
>
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/auto/Apache2/Const
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/auto/Apache2/Const/Const.so
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/auto/Apache2/Const/Const.bs
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/Apache2/Const.pm
May be you aren't loading it, while you think that you do. Please observe:
% perl -le 'use warnings; use strict; use Apache2::Const; \
sub foo {return Apache2::Const::OK }'
% perl -le 'use warnings; use strict; \
sub foo {return Apache2::Const::OK }'
Bareword "Apache2::Const::OK" not allowed while "strict subs" in use at -e
line 1.
Execution of -e aborted due to compilation errors.
Try:
warn $INC{'Apache2/Const.pm'}
somewhere in your code. It should show you the file that was loaded.
If everything else fails, if you can use the problem reporting skeleton
[1] and reproduce the problem with it (adjusting it by adding some minimal
code). Please send it here and we will look at it).
[1] linked from:
http://perl.apache.org/docs/2.0/user/help/help.html#Problem_Description
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> >>Try:
> >>
> >>perl -le 'use warnings; use strict; use Apache2::Const; print
> >>Apache2::Const::OK'
> >>0
> >>
> >>Apache2::Const is one of the modules which will happily run from the
> >>command line.
> >>
> >>Please CC me in your replies to the list so we won't have to wait for 8
> >>hours to see your reply. emails are served with a huge delay since a few days.
> >
> >
> > I get:
> >
> > 0
>
> Good.
>
> > A weird thing: I'm getting those same bareword errors in error_log
> > but I haven't even updated Interchange::Link yet. That module doesn't
> > say "Apache2::Const:OK" anywhere in it and I'm still getting the same
> > error.
>
> That means that you
> - either still have pre-mp2-RC5 Apache2/Const somewhere.
> - or the code that uses it didn't compile that constant. i.e., you (or
> whoever wrote it) didn't do:
>
> use Apache2::Const -compile => 'OK';
>
> before using it.
I replaced:
use Apache::Const;
with:
use Apache2::Const -compile => 'OK';
in Link.pm with the same results. How can I find out if I have an old
Apache2/Const? I definitely only have these on the system:
/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/auto/Apache2/Const
/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/auto/Apache2/Const/Const.so
/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/auto/Apache2/Const/Const.bs
/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/Apache2/Const.pm
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Stas Bekman <st...@stason.org>.
Grant wrote:
>>>Ok I did everything including uninstalling 1.99.17 but I'm getting this error:
>>>
>>>Bareword "Apache2::Const::OK" not allowed while "strict subs" in use
>>>
>>>I guess that means it wasn't fully uninstalled? How can I check on that?
>>
>>No, if it wasn't installed, you would have not been able to load the
>>Apache2::Const module.
>>
>>Try:
>>
>>perl -le 'use warnings; use strict; use Apache2::Const; print
>>Apache2::Const::OK'
>>0
>>
>>Apache2::Const is one of the modules which will happily run from the
>>command line.
>>
>>Please CC me in your replies to the list so we won't have to wait for 8
>>hours to see your reply. emails are served with a huge delay since a few days.
>
>
> I get:
>
> 0
Good.
> A weird thing: I'm getting those same bareword errors in error_log
> but I haven't even updated Interchange::Link yet. That module doesn't
> say "Apache2::Const:OK" anywhere in it and I'm still getting the same
> error.
That means that you
- either still have pre-mp2-RC5 Apache2/Const somewhere.
- or the code that uses it didn't compile that constant. i.e., you (or
whoever wrote it) didn't do:
use Apache2::Const -compile => 'OK';
before using it.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> > Ok I did everything including uninstalling 1.99.17 but I'm getting this error:
> >
> > Bareword "Apache2::Const::OK" not allowed while "strict subs" in use
> >
> > I guess that means it wasn't fully uninstalled? How can I check on that?
>
> No, if it wasn't installed, you would have not been able to load the
> Apache2::Const module.
>
> Try:
>
> perl -le 'use warnings; use strict; use Apache2::Const; print
> Apache2::Const::OK'
> 0
>
> Apache2::Const is one of the modules which will happily run from the
> command line.
>
> Please CC me in your replies to the list so we won't have to wait for 8
> hours to see your reply. emails are served with a huge delay since a few days.
I get:
0
A weird thing: I'm getting those same bareword errors in error_log
but I haven't even updated Interchange::Link yet. That module doesn't
say "Apache2::Const:OK" anywhere in it and I'm still getting the same
error.
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> >>>It looks like my current 1.99.17 configuration has Registry.pm here:
> >>>
> >>>/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/Apache2/ModPerl/Registry.pm
> >>>
> >>>and according to the logs the new one was installed here:
> >>>
> >>>/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm
> >>>
> >>>Interchange::Link has always included this line which looks like the
> >>>"new" namespace:
> >>>
> >>>use ModPerl::Registry;
> >>>
> >>>Also, the Gentoo notes I got at the end of the emerge said to change:
> >>>
> >>>Apache::ModPerl::Registry => ModPerl::Registry
> >>>
> >>>Link.pm already seemed to use that "new" namespace, but it errored as above.
> >>>
> >>>How would I fix this? Would I see others like it if I fixed it?
> >>
> >>Grant, how exactly did you remove 1.99.17? You were supposed to remove the
> >>Apache2/ subdirectory and everything under it. Have you read:
> >>http://perl.apache.org/docs/2.0/rename.html
> >
> >
> > Hi Stas,
> >
> > I removed it with the Gentoo mechanism:
> >
> > emerge -C mod_perl
> >
> > What makes you think it wasn't removed properly? It is my current
> > 1.99.17 installation that has Registry.pm under Apache2. 2.0.0rc5
> > installed it to:
> >
> > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm
>
> Ah, OK, I thought your *current* was the one you have the problem with.
>
> > I don't understand why error_log said it couldn't find that module.
> > The above is in @INC. Maybe I should just try it again?
>
> Please do so.
>
> Your errors are very confusing, you said the error was that it couldn't
> find ModPerl/Registry.pm, but when I asked you where it is you said it's:
>
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/Apache2/ModPerl/Registry.pm
>
> which is wrong. It shouldn't be there if you have uninstalled 1.99.17
>
> and then you said:
>
> > and according to the logs the new one was installed here:
> > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm
>
> but apparently it is not there, so your log is wrong.
Well I was able to get mp2bug to report only CGI 3.05 by renaming some
files but my errors haven't changed. I even tried changing all
Apache2::Const::OK references to Apache2::OK and restarting apache2
but it still reports the same errors. I'm going to roll back.
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Stas Bekman <st...@stason.org>.
Grant wrote:
[...]
> Ok I did everything including uninstalling 1.99.17 but I'm getting this error:
>
> Bareword "Apache2::Const::OK" not allowed while "strict subs" in use
>
> I guess that means it wasn't fully uninstalled? How can I check on that?
No, if it wasn't installed, you would have not been able to load the
Apache2::Const module.
Try:
perl -le 'use warnings; use strict; use Apache2::Const; print
Apache2::Const::OK'
0
Apache2::Const is one of the modules which will happily run from the
command line.
Please CC me in your replies to the list so we won't have to wait for 8
hours to see your reply. emails are served with a huge delay since a few days.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> >>>It looks like my current 1.99.17 configuration has Registry.pm here:
> >>>
> >>>/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/Apache2/ModPerl/Registry.pm
> >>>
> >>>and according to the logs the new one was installed here:
> >>>
> >>>/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm
> >>>
> >>>Interchange::Link has always included this line which looks like the
> >>>"new" namespace:
> >>>
> >>>use ModPerl::Registry;
> >>>
> >>>Also, the Gentoo notes I got at the end of the emerge said to change:
> >>>
> >>>Apache::ModPerl::Registry => ModPerl::Registry
> >>>
> >>>Link.pm already seemed to use that "new" namespace, but it errored as above.
> >>>
> >>>How would I fix this? Would I see others like it if I fixed it?
> >>
> >>Grant, how exactly did you remove 1.99.17? You were supposed to remove the
> >>Apache2/ subdirectory and everything under it. Have you read:
> >>http://perl.apache.org/docs/2.0/rename.html
> >
> >
> > Hi Stas,
> >
> > I removed it with the Gentoo mechanism:
> >
> > emerge -C mod_perl
> >
> > What makes you think it wasn't removed properly? It is my current
> > 1.99.17 installation that has Registry.pm under Apache2. 2.0.0rc5
> > installed it to:
> >
> > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm
>
> Ah, OK, I thought your *current* was the one you have the problem with.
>
> > I don't understand why error_log said it couldn't find that module.
> > The above is in @INC. Maybe I should just try it again?
>
> Please do so.
>
> Your errors are very confusing, you said the error was that it couldn't
> find ModPerl/Registry.pm, but when I asked you where it is you said it's:
>
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/Apache2/ModPerl/Registry.pm
>
> which is wrong. It shouldn't be there if you have uninstalled 1.99.17
>
> and then you said:
>
> > and according to the logs the new one was installed here:
> > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm
>
> but apparently it is not there, so your log is wrong.
Ok I did everything including uninstalling 1.99.17 but I'm getting this error:
Bareword "Apache2::Const::OK" not allowed while "strict subs" in use
I guess that means it wasn't fully uninstalled? How can I check on that?
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Stas Bekman <st...@stason.org>.
Grant wrote:
>>>It looks like my current 1.99.17 configuration has Registry.pm here:
>>>
>>>/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/Apache2/ModPerl/Registry.pm
>>>
>>>and according to the logs the new one was installed here:
>>>
>>>/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm
>>>
>>>Interchange::Link has always included this line which looks like the
>>>"new" namespace:
>>>
>>>use ModPerl::Registry;
>>>
>>>Also, the Gentoo notes I got at the end of the emerge said to change:
>>>
>>>Apache::ModPerl::Registry => ModPerl::Registry
>>>
>>>Link.pm already seemed to use that "new" namespace, but it errored as above.
>>>
>>>How would I fix this? Would I see others like it if I fixed it?
>>
>>Grant, how exactly did you remove 1.99.17? You were supposed to remove the
>>Apache2/ subdirectory and everything under it. Have you read:
>>http://perl.apache.org/docs/2.0/rename.html
>
>
> Hi Stas,
>
> I removed it with the Gentoo mechanism:
>
> emerge -C mod_perl
>
> What makes you think it wasn't removed properly? It is my current
> 1.99.17 installation that has Registry.pm under Apache2. 2.0.0rc5
> installed it to:
>
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm
Ah, OK, I thought your *current* was the one you have the problem with.
> I don't understand why error_log said it couldn't find that module.
> The above is in @INC. Maybe I should just try it again?
Please do so.
Your errors are very confusing, you said the error was that it couldn't
find ModPerl/Registry.pm, but when I asked you where it is you said it's:
/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/Apache2/ModPerl/Registry.pm
which is wrong. It shouldn't be there if you have uninstalled 1.99.17
and then you said:
> and according to the logs the new one was installed here:
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm
but apparently it is not there, so your log is wrong.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> > It looks like my current 1.99.17 configuration has Registry.pm here:
> >
> > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/Apache2/ModPerl/Registry.pm
> >
> > and according to the logs the new one was installed here:
> >
> > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm
> >
> > Interchange::Link has always included this line which looks like the
> > "new" namespace:
> >
> > use ModPerl::Registry;
> >
> > Also, the Gentoo notes I got at the end of the emerge said to change:
> >
> > Apache::ModPerl::Registry => ModPerl::Registry
> >
> > Link.pm already seemed to use that "new" namespace, but it errored as above.
> >
> > How would I fix this? Would I see others like it if I fixed it?
>
> Grant, how exactly did you remove 1.99.17? You were supposed to remove the
> Apache2/ subdirectory and everything under it. Have you read:
> http://perl.apache.org/docs/2.0/rename.html
Hi Stas,
I removed it with the Gentoo mechanism:
emerge -C mod_perl
What makes you think it wasn't removed properly? It is my current
1.99.17 installation that has Registry.pm under Apache2. 2.0.0rc5
installed it to:
/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm
I don't understand why error_log said it couldn't find that module.
The above is in @INC. Maybe I should just try it again?
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Stas Bekman <st...@stason.org>.
Grant wrote:
[...]
> It looks like my current 1.99.17 configuration has Registry.pm here:
>
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/Apache2/ModPerl/Registry.pm
>
> and according to the logs the new one was installed here:
>
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm
>
> Interchange::Link has always included this line which looks like the
> "new" namespace:
>
> use ModPerl::Registry;
>
> Also, the Gentoo notes I got at the end of the emerge said to change:
>
> Apache::ModPerl::Registry => ModPerl::Registry
>
> Link.pm already seemed to use that "new" namespace, but it errored as above.
>
> How would I fix this? Would I see others like it if I fixed it?
Grant, how exactly did you remove 1.99.17? You were supposed to remove the
Apache2/ subdirectory and everything under it. Have you read:
http://perl.apache.org/docs/2.0/rename.html
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> >>>I tracked down an unofficial mod_perl-2.0.0rc5 ebuild and followed
> >>>this stuff to the letter:
> >>>
> >>>http://perl.apache.org/docs/2.0/rename.html
> >>>
> >>>but got nothing but 500s. You're right it doesn't make sense to track
> >>>down segfaults for old software, but upgrading right now seems
> >>>impossible. I'm backing way off this. Thanks for your help though.
> >>
> >>Or you could explain what the problems are, posting the relevant bits of
> >>your error_log so we could help you fix the problems. Mind you, 2.0.0 is
> >>planned to be released next week.
> >
> >
> > I would really love to get rid of those segfaults. My store gets
> > about 800 visitors/days and my error_log shows about 100 segs/day.
> > The segs look like 404s in IE so I must be losing a lot of business.
>
> You mean you are updating the live server with an untested code? or do you
> just say that that's what you have in production now?
Both actually. I only have one server and its been getting these
segfaults for years.
> > It looks like when I set up 2.0.0rc5 I was getting one type of error,
> > that stopped, and then another type of error. I bet that correlates
> > to me setting up 2.0.0rc5, starting to roll back to 1.99.17, and then
> > setting 2.0.0rc5 back up when I realized I needed to try removing
> > 1.99.17.
>
> when you get this kind of random behavior you should start the server in a
> single server mode, in which case you have only one process and all errors
> are seen right away. See the online docs for details.
>
> > The first type of error was like this:
> >
> > failed to resolve handler `Interchange::Link': Bareword
> > "Apache2::Const::OK" not allowed while "strict subs" in use at
> > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/RegistryCooker.pm
> > line 161.\nBareword "Apache2::Const::OK" not allowed while "strict
> > subs" in use at
> > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/RegistryCooker.pm
> > line 163.\nBareword "Apache2::Const::OK" not allowed while "strict
> > subs" in use at
> > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/RegistryCooker.pm
> > line 171.\nBEGIN not safe after errors--compilation aborted at
> > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/RegistryCooker.pm
> > line 201.\nCompilation failed in require at (eval 3) line
> > 3.\n\t...propagated at /usr/lib/perl5/5.8.5/base.pm line 85.\nBEGIN
> > failed--compilation aborted at
> > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm line
> > 25.\nCompilation failed in require at
> > /usr/lib/perl5/site_perl/5.8.5/Interchange/Link.pm line 27.\nBEGIN
> > failed--compilation aborted at
> > /usr/lib/perl5/site_perl/5.8.5/Interchange/Link.pm line
> > 27.\nCompilation failed in require at (eval 2) line 3.\n, referer:
>
> Hmm, we just saw this one a few days ago in another report. I've suggested
> that the user had a mixed mp2 build where the pre-RC5 install was getting
> in the way. Make sure that you nuke all mod_perl modules from
> /usr/lib/perl5/ and then do a fresh install. Any chance with that?
>
> I'm pretty sure you get this error because mp2-pre-RC5 didn't have
> Apache2::Const::OK, but it was Apache::OK.
I think that's exactly what it was. I removed 1.99.17 before
installing 2.0.0rc5 the second time, and that's when this other error
took its place.
> > and the second was like this:
> >
> > failed to resolve handler `Interchange::Link': Can't locate
> > ModPerl/Registry.pm in @INC (@INC contains:
> > /usr/lib/perl5/5.8.5/i686-linux /usr/lib/perl5/5.8.5
> > /usr/lib/perl5/site_perl/5.8.5/i686-linux
> > /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl
> > /usr/lib/perl5/vendor_perl/5.8.5/i686-linux
> > /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl .
> > /usr/lib/apache2/ /usr/lib/apache2/lib/perl) at
> > /usr/lib/perl5/site_perl/5.8.5/Interchange/Link.pm line 27.\nBEGIN
> > failed--compilation aborted at
> > /usr/lib/perl5/site_perl/5.8.5/Interchange/Link.pm line
> > 27.\nCompilation failed in require at (eval 2) line 3.\n, referer:
> >
> > What do you think?
>
> Well, where ModPerl/Registry.pm is? What find(1) says?
It looks like my current 1.99.17 configuration has Registry.pm here:
/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/Apache2/ModPerl/Registry.pm
and according to the logs the new one was installed here:
/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm
Interchange::Link has always included this line which looks like the
"new" namespace:
use ModPerl::Registry;
Also, the Gentoo notes I got at the end of the emerge said to change:
Apache::ModPerl::Registry => ModPerl::Registry
Link.pm already seemed to use that "new" namespace, but it errored as above.
How would I fix this? Would I see others like it if I fixed it?
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Stas Bekman <st...@stason.org>.
Grant wrote:
>>>I tracked down an unofficial mod_perl-2.0.0rc5 ebuild and followed
>>>this stuff to the letter:
>>>
>>>http://perl.apache.org/docs/2.0/rename.html
>>>
>>>but got nothing but 500s. You're right it doesn't make sense to track
>>>down segfaults for old software, but upgrading right now seems
>>>impossible. I'm backing way off this. Thanks for your help though.
>>
>>Or you could explain what the problems are, posting the relevant bits of
>>your error_log so we could help you fix the problems. Mind you, 2.0.0 is
>>planned to be released next week.
>
>
> I should have explained Interchange::Link. I bet the best way to do
> that is show you its config block in httpd.conf:
>
> <Location />
> SetHandler perl-script
> PerlResponseHandler Interchange::Link
> PerlOptions +GlobalRequest
> PerlSetVar InterchangeServer /usr/local/interchange/etc/socket
> </Location>
>
> I use the open-source Interchange shopping cart:
>
> http://www.icdevgroup.org
But I thought the error was indicating that you are using ModPerl::Registry?
failed to resolve handler `Interchange::Link': Can't locate
ModPerl/Registry.pm in @INC (@INC contains
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> > I tracked down an unofficial mod_perl-2.0.0rc5 ebuild and followed
> > this stuff to the letter:
> >
> > http://perl.apache.org/docs/2.0/rename.html
> >
> > but got nothing but 500s. You're right it doesn't make sense to track
> > down segfaults for old software, but upgrading right now seems
> > impossible. I'm backing way off this. Thanks for your help though.
>
> Or you could explain what the problems are, posting the relevant bits of
> your error_log so we could help you fix the problems. Mind you, 2.0.0 is
> planned to be released next week.
I should have explained Interchange::Link. I bet the best way to do
that is show you its config block in httpd.conf:
<Location />
SetHandler perl-script
PerlResponseHandler Interchange::Link
PerlOptions +GlobalRequest
PerlSetVar InterchangeServer /usr/local/interchange/etc/socket
</Location>
I use the open-source Interchange shopping cart:
http://www.icdevgroup.org
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Stas Bekman <st...@stason.org>.
Grant wrote:
>>>I tracked down an unofficial mod_perl-2.0.0rc5 ebuild and followed
>>>this stuff to the letter:
>>>
>>>http://perl.apache.org/docs/2.0/rename.html
>>>
>>>but got nothing but 500s. You're right it doesn't make sense to track
>>>down segfaults for old software, but upgrading right now seems
>>>impossible. I'm backing way off this. Thanks for your help though.
>>
>>Or you could explain what the problems are, posting the relevant bits of
>>your error_log so we could help you fix the problems. Mind you, 2.0.0 is
>>planned to be released next week.
>
>
> I would really love to get rid of those segfaults. My store gets
> about 800 visitors/days and my error_log shows about 100 segs/day.
> The segs look like 404s in IE so I must be losing a lot of business.
You mean you are updating the live server with an untested code? or do you
just say that that's what you have in production now?
> It looks like when I set up 2.0.0rc5 I was getting one type of error,
> that stopped, and then another type of error. I bet that correlates
> to me setting up 2.0.0rc5, starting to roll back to 1.99.17, and then
> setting 2.0.0rc5 back up when I realized I needed to try removing
> 1.99.17.
when you get this kind of random behavior you should start the server in a
single server mode, in which case you have only one process and all errors
are seen right away. See the online docs for details.
> The first type of error was like this:
>
> failed to resolve handler `Interchange::Link': Bareword
> "Apache2::Const::OK" not allowed while "strict subs" in use at
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/RegistryCooker.pm
> line 161.\nBareword "Apache2::Const::OK" not allowed while "strict
> subs" in use at
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/RegistryCooker.pm
> line 163.\nBareword "Apache2::Const::OK" not allowed while "strict
> subs" in use at
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/RegistryCooker.pm
> line 171.\nBEGIN not safe after errors--compilation aborted at
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/RegistryCooker.pm
> line 201.\nCompilation failed in require at (eval 3) line
> 3.\n\t...propagated at /usr/lib/perl5/5.8.5/base.pm line 85.\nBEGIN
> failed--compilation aborted at
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm line
> 25.\nCompilation failed in require at
> /usr/lib/perl5/site_perl/5.8.5/Interchange/Link.pm line 27.\nBEGIN
> failed--compilation aborted at
> /usr/lib/perl5/site_perl/5.8.5/Interchange/Link.pm line
> 27.\nCompilation failed in require at (eval 2) line 3.\n, referer:
Hmm, we just saw this one a few days ago in another report. I've suggested
that the user had a mixed mp2 build where the pre-RC5 install was getting
in the way. Make sure that you nuke all mod_perl modules from
/usr/lib/perl5/ and then do a fresh install. Any chance with that?
I'm pretty sure you get this error because mp2-pre-RC5 didn't have
Apache2::Const::OK, but it was Apache::OK.
> and the second was like this:
>
> failed to resolve handler `Interchange::Link': Can't locate
> ModPerl/Registry.pm in @INC (@INC contains:
> /usr/lib/perl5/5.8.5/i686-linux /usr/lib/perl5/5.8.5
> /usr/lib/perl5/site_perl/5.8.5/i686-linux
> /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl
> /usr/lib/perl5/vendor_perl/5.8.5/i686-linux
> /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl .
> /usr/lib/apache2/ /usr/lib/apache2/lib/perl) at
> /usr/lib/perl5/site_perl/5.8.5/Interchange/Link.pm line 27.\nBEGIN
> failed--compilation aborted at
> /usr/lib/perl5/site_perl/5.8.5/Interchange/Link.pm line
> 27.\nCompilation failed in require at (eval 2) line 3.\n, referer:
>
> What do you think?
Well, where ModPerl/Registry.pm is? What find(1) says?
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> > I tracked down an unofficial mod_perl-2.0.0rc5 ebuild and followed
> > this stuff to the letter:
> >
> > http://perl.apache.org/docs/2.0/rename.html
> >
> > but got nothing but 500s. You're right it doesn't make sense to track
> > down segfaults for old software, but upgrading right now seems
> > impossible. I'm backing way off this. Thanks for your help though.
>
> Or you could explain what the problems are, posting the relevant bits of
> your error_log so we could help you fix the problems. Mind you, 2.0.0 is
> planned to be released next week.
I would really love to get rid of those segfaults. My store gets
about 800 visitors/days and my error_log shows about 100 segs/day.
The segs look like 404s in IE so I must be losing a lot of business.
It looks like when I set up 2.0.0rc5 I was getting one type of error,
that stopped, and then another type of error. I bet that correlates
to me setting up 2.0.0rc5, starting to roll back to 1.99.17, and then
setting 2.0.0rc5 back up when I realized I needed to try removing
1.99.17.
The first type of error was like this:
failed to resolve handler `Interchange::Link': Bareword
"Apache2::Const::OK" not allowed while "strict subs" in use at
/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/RegistryCooker.pm
line 161.\nBareword "Apache2::Const::OK" not allowed while "strict
subs" in use at
/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/RegistryCooker.pm
line 163.\nBareword "Apache2::Const::OK" not allowed while "strict
subs" in use at
/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/RegistryCooker.pm
line 171.\nBEGIN not safe after errors--compilation aborted at
/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/RegistryCooker.pm
line 201.\nCompilation failed in require at (eval 3) line
3.\n\t...propagated at /usr/lib/perl5/5.8.5/base.pm line 85.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/vendor_perl/5.8.5/i686-linux/ModPerl/Registry.pm line
25.\nCompilation failed in require at
/usr/lib/perl5/site_perl/5.8.5/Interchange/Link.pm line 27.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.5/Interchange/Link.pm line
27.\nCompilation failed in require at (eval 2) line 3.\n, referer:
and the second was like this:
failed to resolve handler `Interchange::Link': Can't locate
ModPerl/Registry.pm in @INC (@INC contains:
/usr/lib/perl5/5.8.5/i686-linux /usr/lib/perl5/5.8.5
/usr/lib/perl5/site_perl/5.8.5/i686-linux
/usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.5/i686-linux
/usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl .
/usr/lib/apache2/ /usr/lib/apache2/lib/perl) at
/usr/lib/perl5/site_perl/5.8.5/Interchange/Link.pm line 27.\nBEGIN
failed--compilation aborted at
/usr/lib/perl5/site_perl/5.8.5/Interchange/Link.pm line
27.\nCompilation failed in require at (eval 2) line 3.\n, referer:
What do you think?
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Stas Bekman <st...@stason.org>.
Grant wrote:
> I tracked down an unofficial mod_perl-2.0.0rc5 ebuild and followed
> this stuff to the letter:
>
> http://perl.apache.org/docs/2.0/rename.html
>
> but got nothing but 500s. You're right it doesn't make sense to track
> down segfaults for old software, but upgrading right now seems
> impossible. I'm backing way off this. Thanks for your help though.
Or you could explain what the problems are, posting the relevant bits of
your error_log so we could help you fix the problems. Mind you, 2.0.0 is
planned to be released next week.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> >>>Fair enough. I don't have t/report or t/REPORT anywhere on my system
> >>>though. Could it be named something else or is there another utility?
> >>
> >>You are correct, Grant. My apologies, t/REPORT is created at build time
> >>and it's only useful for the test suite bug reports. For post installed
> >>mod_perl there is mp2bug script which does a similar thing. It's mentioned
> >> here:
> >>http://perl.apache.org/docs/2.0/user/help/help.html#Important_Information
> >>but I need to drop the META comment. I'll fix that shortly. Please let us
> >>know if you could find mp2bug and run it and send the info here. thanks.
> >
> >
> > I ran mp2bug and it looks like I am running 1.99.17.
>
> Cool.
>
> > I'm working on getting the core dump. I got some instructions from
> > the Gentoo list (re-compile with proper settings, add 'uname -c
> > unlimited' to the apache2 initscript, and restart) but I can't find
> > any "core" files even though I'm getting segs. I'll post the mp2bug
> > report along with the dump as soon as I have it, unless you'd like to
> > see the report now.
>
> See if this helps:
> http://perl.apache.org/docs/2.0/devel/debug/c.html#Getting_the_core_File_Dumped
>
> In any case, before you spend time on this you should upgrade to the
> newest mp2 first. Since it's possible that you hit a segfault that was
> fixed since then. In which case you are wasting your time.
Hey Stas,
I tracked down an unofficial mod_perl-2.0.0rc5 ebuild and followed
this stuff to the letter:
http://perl.apache.org/docs/2.0/rename.html
but got nothing but 500s. You're right it doesn't make sense to track
down segfaults for old software, but upgrading right now seems
impossible. I'm backing way off this. Thanks for your help though.
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Stas Bekman <st...@stason.org>.
Grant wrote:
>>>Fair enough. I don't have t/report or t/REPORT anywhere on my system
>>>though. Could it be named something else or is there another utility?
>>
>>You are correct, Grant. My apologies, t/REPORT is created at build time
>>and it's only useful for the test suite bug reports. For post installed
>>mod_perl there is mp2bug script which does a similar thing. It's mentioned
>> here:
>>http://perl.apache.org/docs/2.0/user/help/help.html#Important_Information
>>but I need to drop the META comment. I'll fix that shortly. Please let us
>>know if you could find mp2bug and run it and send the info here. thanks.
>
>
> I ran mp2bug and it looks like I am running 1.99.17.
Cool.
> I'm working on getting the core dump. I got some instructions from
> the Gentoo list (re-compile with proper settings, add 'uname -c
> unlimited' to the apache2 initscript, and restart) but I can't find
> any "core" files even though I'm getting segs. I'll post the mp2bug
> report along with the dump as soon as I have it, unless you'd like to
> see the report now.
See if this helps:
http://perl.apache.org/docs/2.0/devel/debug/c.html#Getting_the_core_File_Dumped
In any case, before you spend time on this you should upgrade to the
newest mp2 first. Since it's possible that you hit a segfault that was
fixed since then. In which case you are wasting your time.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> > Fair enough. I don't have t/report or t/REPORT anywhere on my system
> > though. Could it be named something else or is there another utility?
>
> You are correct, Grant. My apologies, t/REPORT is created at build time
> and it's only useful for the test suite bug reports. For post installed
> mod_perl there is mp2bug script which does a similar thing. It's mentioned
> here:
> http://perl.apache.org/docs/2.0/user/help/help.html#Important_Information
> but I need to drop the META comment. I'll fix that shortly. Please let us
> know if you could find mp2bug and run it and send the info here. thanks.
I ran mp2bug and it looks like I am running 1.99.17.
I'm working on getting the core dump. I got some instructions from
the Gentoo list (re-compile with proper settings, add 'uname -c
unlimited' to the apache2 initscript, and restart) but I can't find
any "core" files even though I'm getting segs. I'll post the mp2bug
report along with the dump as soon as I have it, unless you'd like to
see the report now.
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Stas Bekman <st...@stason.org>.
Grant wrote:
>>Grant, have you read:
>>http://perl.apache.org/docs/2.0/user/help/help.html#Reporting_Problems
>>(all the way to the end)?
>>
>>When you run t/REPORT it will tell you (and us) almost everything we need
>>to know.
>>
>>Then you configure your system to dump core files, you get the core
>>backtrace and you send it to us.
>>
>>If you aren't sure if you had mod_perl messed up, wipe it all and
>>reinstall from scratch.
>>
>>Feel free to ask more questions if something is not clear, but please read
>>the quoted above document first.
>>
>>Thank you.
>
>
> Fair enough. I don't have t/report or t/REPORT anywhere on my system
> though. Could it be named something else or is there another utility?
You are correct, Grant. My apologies, t/REPORT is created at build time
and it's only useful for the test suite bug reports. For post installed
mod_perl there is mp2bug script which does a similar thing. It's mentioned
here:
http://perl.apache.org/docs/2.0/user/help/help.html#Important_Information
but I need to drop the META comment. I'll fix that shortly. Please let us
know if you could find mp2bug and run it and send the info here. thanks.
> When I said I wasn't sure about my mod_perl installation, it's because
> the mod_perl.so file seemed to be installed to the wrong directory. I
> posted a bug about it here:
>
> http://bugs.gentoo.org/show_bug.cgi?id=92308
>
> I did copy it to the correct directory, but I should make sure I'm
> running 1.99.17 (Gentoo's latest) instead of my previous 1.99.11.
Ideally you should build mod_perl by yourself. Especially sinice 1.99_17
is a way too old. You should install the latest version.
http://perl.apache.org/download/index.html
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> Grant, have you read:
> http://perl.apache.org/docs/2.0/user/help/help.html#Reporting_Problems
> (all the way to the end)?
>
> When you run t/REPORT it will tell you (and us) almost everything we need
> to know.
>
> Then you configure your system to dump core files, you get the core
> backtrace and you send it to us.
>
> If you aren't sure if you had mod_perl messed up, wipe it all and
> reinstall from scratch.
>
> Feel free to ask more questions if something is not clear, but please read
> the quoted above document first.
>
> Thank you.
Fair enough. I don't have t/report or t/REPORT anywhere on my system
though. Could it be named something else or is there another utility?
When I said I wasn't sure about my mod_perl installation, it's because
the mod_perl.so file seemed to be installed to the wrong directory. I
posted a bug about it here:
http://bugs.gentoo.org/show_bug.cgi?id=92308
I did copy it to the correct directory, but I should make sure I'm
running 1.99.17 (Gentoo's latest) instead of my previous 1.99.11.
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Stas Bekman <st...@stason.org>.
Grant wrote:
>>>Hello, can you tell me anything else about getting those core dump
>>>files?
>>
>>Please read these:
>>http://perl.apache.org/docs/2.0/user/help/help.html#Reporting_Problems
>>http://perl.apache.org/docs/2.0/devel/debug/c.html#Analyzing_Dumped_Core_Files
>>
>>- Perrin
>
>
> Ok. Can you tell me how to be sure of which version of mod_perl I'm
> running? I had some installation trouble with 1.99.17 and I'd like to
> be sure that's what I'm running before I dig into this.
Grant, have you read:
http://perl.apache.org/docs/2.0/user/help/help.html#Reporting_Problems
(all the way to the end)?
When you run t/REPORT it will tell you (and us) almost everything we need
to know.
Then you configure your system to dump core files, you get the core
backtrace and you send it to us.
If you aren't sure if you had mod_perl messed up, wipe it all and
reinstall from scratch.
Feel free to ask more questions if something is not clear, but please read
the quoted above document first.
Thank you.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> > Hello, can you tell me anything else about getting those core dump
> > files?
>
> Please read these:
> http://perl.apache.org/docs/2.0/user/help/help.html#Reporting_Problems
> http://perl.apache.org/docs/2.0/devel/debug/c.html#Analyzing_Dumped_Core_Files
>
> - Perrin
Ok. Can you tell me how to be sure of which version of mod_perl I'm
running? I had some installation trouble with 1.99.17 and I'd like to
be sure that's what I'm running before I dig into this.
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Perrin Harkins <pe...@elem.com>.
Grant wrote:
> Hello, can you tell me anything else about getting those core dump
> files?
Please read these:
http://perl.apache.org/docs/2.0/user/help/help.html#Reporting_Problems
http://perl.apache.org/docs/2.0/devel/debug/c.html#Analyzing_Dumped_Core_Files
- Perrin
Re: mod_perl causing seg faults in apache2?
Posted by Grant <em...@gmail.com>.
> > Hello, I've been suffering from intermittent segmentation faults in my
> > apache2 error_log for quite a while now. It seems to be worst during
> > peak traffic hours. Here's what they look like:
>
> > [notice] child pid 13189 exit signal Segmentation fault (11)
>
> > My consultant thinks it's a mod_perl problem. I'm running Gentoo
> > Linux along with apache-2.0.54 and mod_perl-1.99.17. All of my
> > software is 100% up-to-date as per the Gentoo portage tree.
>
> The portage tree is somewhat out of date however. (As are most distributions
> as far as I can tell, when it comes to modperl2). So it's possible it's
> something that's already been fixed.
>
> > Does anyone have any ideas on this?
>
> Have you tried looking at the core dumps? Without more to go on, there's not
> much anyone can tell you.
>
> cf.
> http://perl.apache.org/docs/2.0/devel/debug/c.html#Analyzing_Dumped_Core_Files
Hello, can you tell me anything else about getting those core dump
files? I can enable debugging options in apache2, apr, and perl and
re-emerge (compile) them. I'm confused on what to do from there. Is
it possible that the files will be generated just from that?
- Grant
Re: mod_perl causing seg faults in apache2?
Posted by Malcolm J Harwood <mj...@liminalflux.net>.
On Thursday 12 May 2005 02:29 pm, Grant wrote:
> Hello, I've been suffering from intermittent segmentation faults in my
> apache2 error_log for quite a while now. It seems to be worst during
> peak traffic hours. Here's what they look like:
> [notice] child pid 13189 exit signal Segmentation fault (11)
> My consultant thinks it's a mod_perl problem. I'm running Gentoo
> Linux along with apache-2.0.54 and mod_perl-1.99.17. All of my
> software is 100% up-to-date as per the Gentoo portage tree.
The portage tree is somewhat out of date however. (As are most distributions
as far as I can tell, when it comes to modperl2). So it's possible it's
something that's already been fixed.
> Does anyone have any ideas on this?
Have you tried looking at the core dumps? Without more to go on, there's not
much anyone can tell you.
cf.
http://perl.apache.org/docs/2.0/devel/debug/c.html#Analyzing_Dumped_Core_Files