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.
PROTECTED]
> Subject: Re: Apache children hanging
>
>
> > Is there any equivalent procedure for debugging core
> > dumps? I've tried this and it doesn't work because
> > the process is not running. When I process dies it
> > would be nice to know where
Original Message-
> From: Doug MacEachern [mailto:[EMAIL PROTECTED]]
> Sent: 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
> > % s
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
[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.
---
ustavo 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
TED]]
Sent: 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)
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 exi
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 http://www.
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)
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 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
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 $pid_of_spin
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 fi
> "BL" == Ben Li <[EMAIL PROTECTED]> writes:
BL> Yes , I'm always get into this trouble , a gnu/linux redhat 6.1
BL> with last kernel and patch . About 280k hits per day , down every
BL> two days . Even sometimes a watchdog can reboot it , but sometims
BL> not . Seemly modperl is too compl
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
> thing
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
> PerlCh
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 b
> % 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
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.
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
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
Tha
22 matches
Mail list logo
