Re: debugging run away httpd process

[victor]

Hello Brian, thanks for your reply,
On Thu, Oct 14, 2004 at 12:07:17PM +0800, victor wrote:
 

2) Why strace doesn't return anything?  or is strace the appropiate tool 
to use at all?  is there any mod_perl module/option I should turn 
on/off/tweak to help me find out what the process is doing?
   

How are you invoking strace?
 

 As root I ran /usr/bin/strace -p <httpd process eating up all cpu>
 We have sorted out the problem on this part it turns out to be a 
special case which casued one of the regex run into infinite loop, so no 
system call hads been made at all.

 I just wonder is there any other tool out that beside strace I can use 
in such situtation?

3) What can I do to find more on those socket listed in 
/proc/<processID>/fs are for?  what are they pointing to?
   

What does 'lsof' show you?  I'm more used to that tool that any
vendor-specific one...
 

 I called lsof with option -p <the httpd process eating up all cpu> and 
grep for those inode number I collected from /proc, nothing returned.

 I am sorry I did not save a copy of the lsof output.  but is there any 
specific detail you are looking for/I should pay extra attention?

Tor.
--
<!---------------------------------------------
                          Victor
                          Development Engineer
                          Outblaze Ltd
---------------------------------------------->
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html