Hello everyone, This could be a bit off topic, please kindly forgive me if it is so, I am seeking for tips on debugging perl script that is running under mod_perl.
We use mod_perl heavily here, and lately I notice some apache children for some reason chew up large amount of cpu (indeed all cpu). Using apache's server-status i can tell it is one of the new script we have deployed that caused the probloem, but trouble is, the script is big, where should I start looking. What I usually do is to use strace, lsof to see if I can get some hints as of what's the process is doing, but this time, running strace on the httpd process simply return nothing, and lsof doesn't offer much tips either. checking /proc/<processID>/fd/ I found the process has opened some socket binding to some inode, I used netstat -nape to try to find what those inode were binded to, but I couldn't find anything. I think my senior has nailed the problem by reviewing the source, but I wonder if there's something I could have done more/better in analysing the problem. Is the method/tool chain I'm using appropiate? is there anything inside mod_perl I can turn on/off/tweak so I can get more knowledge of running mod_process? Any advice would be much appreicated. Tor. -- 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
