there are hints in the SUPPORT doc on how to debug such problems. there
was also several "Hanging process" threads in the past weeks with more
tips, search in the archives for keywords gdb, .gdbinit, curinfo
if you can get more insight from those tips, we can help more.
On Sun, 9 Jan 2000,
Why, reinvent the wheel? I wrote Apache::VMonitor (grab from CPAN) that
does all this and more (all but tail -f) I use it all the time, saves me a
lot of time, since I don't have to telnet!
Ok - I will try to look into that when I get time.
2) Open up and hack Apache::SizeLimit and have
I'm looking for some help getting apache to run reliably. Apache 1.3.9
with
mod_perl 1.21 and Perl 5.005_03 is running on a dual P500 with 1 Gb of
RAM
running Redhat 6.1. We run about 5 sites off the box, most of which are
fairly high traffic, and use a lot of CGI and
MySQL 3.22.25 is
I'm looking for some help getting apache to run reliably. Apache 1.3.9 with
mod_perl 1.21 and Perl 5.005_03 is running on a dual P500 with 1 Gb of RAM
running Redhat 6.1. We run about 5 sites off the box, most of which are
fairly high traffic, and use a lot of CGI and
MySQL 3.22.25 is used with
Jan 2000 19:58:00 -
From: James Furness [EMAIL PROTECTED]
Reply-To: James Furness [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Memory leak/server crashes
I'm looking for some help getting apache to run reliably. Apache 1.3.9 with
mod_perl 1.21 and Perl 5.005_03 is running on a dual
Try using Apache::SizeLimit as a way of controlling your
processes. Sounds like a recursive page that performs infinite internal
requests.
Ok, sounds like a good solution, but it still seems to me I should be
eliminating the problem at the source. Any ideas as to how I could narrow
down the
"James Furness" [EMAIL PROTECTED] writes:
I'm looking for some help getting apache to run reliably. Apache 1.3.9 with
mod_perl 1.21 and Perl 5.005_03 is running on a dual P500 with 1 Gb of RAM
running Redhat 6.1. We run about 5 sites off the box, most of which are
fairly high traffic, and
]
Subject: Re: Memory leak/server crashes
Try using Apache::SizeLimit as a way of controlling your
processes. Sounds like a recursive page that performs infinite internal
requests.
Ok, sounds like a good solution, but it still seems to me I should be
eliminating the problem at the source
On Sun, 9 Jan 2000, Sean Chittenden wrote:
Yeah... two things I'd do:
1) Open two telnet sessions to the box. One for top that is
monitoring processes for your web user (www typically) and is sorting by
memory usage w/ a 1 second refresh. I'd change the size of the window
