that up
and running with the latest Apache, using Apache::DBI has solved the
problem of the ridiculously large SQL connections, but now I'm having
problems with hanging processes.
Apparently when a child process doesn't finish properly it is still
running on and on in memory. Apache reports it's
cript.
I hope this is helpful to others, but I still am looking for more
answers to this!
Thanks,
Jeremy
-Original Message-
From: Jeremy Rusnak [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 20, 2001 6:11 PM
To: [EMAIL PROTECTED]
Subject: Hanging processes (all of a sudden!)
Hi
That got it. I cannot thank you enough. The sites are smokin' now.
Recap for interested parties:
* Solaris 2.7
* mod_perl 1.21
Observed bugs:
* occassional httpd processes stop responding
* they stay in 'run' state (via 'top')
* only print 'brk(...)' on
"%s\n", $sv ? ((XPV*) ((SV*)$sv)-sv_any)-xpv_pv : "undef"
end
and run:
(gdb) perl_get_sv("Apache::Constants::AUTOLOAD")
what does that print?
gdb'd several different hanging processes to make sure that this is repeatable. The
only changes were expected (eval
(gdb) perl_get_sv("Apache::Constants::AUTOLOAD")
Apache::Constants::OPT_EXECCGI
what I was about to suggest trying is already in the modperl cvs Changes:
preload Apache::Constants::OPT_EXECCGI() for Apache::{Registry,PerlRun}
thanks to Chris Remshaw for spotting this w/ Apache::DProf
so try
On Fri, 10 Dec 1999, Tony Demark wrote:
I am having a problem with hanging httpd processes. I have done some AV
searches as well as investigated the list archives and did not find any
conclusive answer to this problem. If I missed it, can someone point me in the
right direction? If any
Doug,
Tried what you suggest, but with seemingly disappointing results. (below) The
hangs seem to come _after_ the logging phase - the heap just keep growing and
the process takes up all available CPU, but it doesn't seem to be doing
anything!
This is really getting dis-heartening.
Thanks,
On Tue, 14 Dec 1999, Tony Demark wrote:
Doug,
Tried what you suggest, but with seemingly disappointing results. (below) The
hangs seem to come _after_ the logging phase - the heap just keep growing and
the process takes up all available CPU, but it doesn't seem to be doing
anything!
In message [EMAIL PROTECTED], Doug MacEac
hern writes:
On Tue, 14 Dec 1999, Tony Demark wrote:
Doug,
Tried what you suggest, but with seemingly disappointing results. (below) Th
e
hangs seem to come _after_ the logging phase - the heap just keep growing an
d
the process takes up all
Hi --
I have been getting some similar large processes myself. They are not
"hanging", but rather they just "plumped" up all of a sudden. I was
using the LWP code to fetch pages for users and found that if I set the
"max_size" for the request read I got rid of the "plumpers". Are you
doing
10 matches
Mail list logo
