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 and
> make it pretty short so that the refreshes happen quicker, but that
> depends on your connection speed. The second telnet window is a window
> that tails your access log (tail -f). It sounds boring, but by watching
> the two, you should have an idea as to when the problem happens.
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!
> 2) Open up and hack Apache::SizeLimit and have it do a stack dump
> (Carp::croak) of what's going on... there may be some clue there.
Apache::GTopLimit is an advanced one :) (you are on Linux, right?) but
Apache::SizeLimit is just file
3) try running in single mode with 'strace' (probably not a good idea for
a production server), but you can still strace all the processes into a
log file
4) Apache::Leak ?
_______________________________________________________________________
Stas Bekman mailto:[EMAIL PROTECTED] http://www.stason.org/stas
Perl,CGI,Apache,Linux,Web,Java,PC http://www.stason.org/stas/TULARC
perl.apache.org modperl.sourcegarden.org perlmonth.com perl.org
single o-> + single o-+ = singlesheaven http://www.singlesheaven.com
