Hello everyone,
This might be a bit off topic, please kindly forgive me, I am seeking some tips on debuging mod_perl script, I have a mod_perl enabled apache server running all kinds of perl scripts. Lately after a pitty major script update, I notice some apache children would chew up all CPU, using strace on the process would return no result (strace stall and nothing is show on the screen), checking /proc/<processID>/fd I find the process opened some socket but those Inode listed can not be seen in netstat -nape. This is not the first time I encounter such problem, it's always some problem deep within the code that didn't handle some unexpected case properly, and it always take forever to hunt them down caus' I have little clue what is happening. It would definitly make my life a lot easier if I can find out more of the problem so I can at least make a guess where to start looking into.
I would very much love to learn the way to...
1) Find out what the process is dong exactly that need so much CPU cycle.
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?
3) What can I do to find more on those socket listed in /proc/<processID>/fs are for? what are they pointing to?
Any advice would be much much appreciated.
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
