On Tue, 13 Jun 2000, Paul G. Weiss wrote:
Yes, that much I knew, however when you do that you
can't use curinfo from .gdbinit, because the process
is not running.
% gdb httpd core
that's worked with curinfo for me in the past.
On Mon, 12 Jun 2000, Ken Williams wrote:
[EMAIL PROTECTED] (Blue) wrote:
there is a procedure in the mod_peril SUPPORT document that works if you
Uh-oh - is mod_peril a Microsoft product or something? =)
Perhaps the DSO version of mod_perl should be called mod_peril.
sorry, it's a joke
: Thursday, June 01, 2000 6:27 PM
To: John Armstrong
Cc: Gustavo Duarte; [EMAIL PROTECTED]
Subject: Re: Apache children hanging
% gdb httpd $pid_of_spinning_process
% source modperl_x.xx/.gdbinit
% curinfo
oops, that should be:
% gdb httpd $pid_of_spinning_process
(gdb) source modperl_x.xx
On Thu, 1 Jun 2000, Jay Jacobs wrote:
With that previous thread of Apache children hanging up the server it made
me think of an issue I see quite frequently in development... When I stop
the mod_perl server, it won't exit properly (or fast) :
[warn] child process 8530 still did not exit
Doug MacEachern [EMAIL PROTECTED] writes:
% gdb httpd $pid_of_spinning_process
% source modperl_x.xx/.gdbinit
% curinfo
oops, that should be:
% gdb httpd $pid_of_spinning_process
(gdb) source modperl_x.xx/.gdbinit
(gdb) curinfo
Is this magic in the guide? I'm on the bus
On Fri, Jun 02, 2000 at 09:06:02AM +0100, David Hodgkinson wrote:
Doug MacEachern [EMAIL PROTECTED] writes:
% gdb httpd $pid_of_spinning_process
% source modperl_x.xx/.gdbinit
% curinfo
oops, that should be:
% gdb httpd $pid_of_spinning_process
(gdb) source
Eric Cholet [EMAIL PROTECTED] writes:
I've added it to SUPPORT, and it will be added to the guide soonish.
Cool. One of those things you hope you never need...
--
Dave Hodgkinson, http://www.hodgkinson.org
Editor-in-chief, The Highway Star
John Armstrong wrote:
I have had this problem to varying degrees in all of my high traffic
mod perl installations. The thing that saves me is Apache::Resource.
In my httpd.conf I put :
PerlModule Apache::Resource
PerlSetEnv PERL_RLIMIT_DATA 32
PerlSetEnv PERL_RLIMIT_CPU 640
Steve Reppucci wrote:
This is *exactly* the symptoms we see, and we're just about always up to
date with Apache/Perl/modperl releases.
We've spent a fair amount of time trying to isolate the cause of these,
but haven't been able to point the finger at any one cause. Some of the
things
Now if only I had known this two years ago... Awsome tidbit though. Thanks!
you can find out which line of Perl code is triggering a spin, by
attaching to the process with gdb;
% gdb httpd $pid_of_spinning_process
% source modperl_x.xx/.gdbinit
% curinfo
should show you the
Someone just pointed out that this should probably go into the guide or
FAQ somewhere. Just a thought...
On Thu, 1 Jun 2000, Doug MacEachern wrote:
% gdb httpd $pid_of_spinning_process
% source modperl_x.xx/.gdbinit
% curinfo
oops, that should be:
% gdb httpd
On Fri, 2 Jun 2000, Ian Struble wrote:
Someone just pointed out that this should probably go into the guide or
FAQ somewhere. Just a thought...
On Thu, 1 Jun 2000, Doug MacEachern wrote:
% gdb httpd $pid_of_spinning_process
% source modperl_x.xx/.gdbinit
% curinfo
oops,
Hi there people,
I have inherited a web server running mod_perl and I am experiencing a
somewhat critical problem: http processes sometimes get into an infinite
loop, using 100% cpu time, and given enough time bring the machine to a
halt.
I've done a lot of testing, and there isn't a specific
I have had this problem to varying degrees in all of my high traffic
mod perl installations. The thing that saves me is Apache::Resource.
In my httpd.conf I put :
PerlModule Apache::Resource
PerlSetEnv PERL_RLIMIT_DATA 32
PerlSetEnv PERL_RLIMIT_CPU 640
PerlChildInitHandler Apache::Resource
On Thu, 1 Jun 2000, Gustavo Duarte wrote:
there to see if it stops the problem (the code isn't too clean - lots of
global variables, not written under strict, etc, but "it works").
looks like a global variable is exactly what your problem is. somebody is
creating an Apache::SubRequest object
you can find out which line of Perl code is triggering a spin, by
attaching to the process with gdb;
% gdb httpd $pid_of_spinning_process
% source modperl_x.xx/.gdbinit
% curinfo
should show you the filename:line_number where Perl is stuck.
% gdb httpd $pid_of_spinning_process
% source modperl_x.xx/.gdbinit
% curinfo
oops, that should be:
% gdb httpd $pid_of_spinning_process
(gdb) source modperl_x.xx/.gdbinit
(gdb) curinfo
This is *exactly* the symptoms we see, and we're just about always up to
date with Apache/Perl/modperl releases.
We've spent a fair amount of time trying to isolate the cause of these,
but haven't been able to point the finger at any one cause. Some of the
things we've determined:
- The same
18 matches
Mail list logo
