Clear questions and runnable code get the best and fastest answer |
|
PerlMonks |
Apache becomes unresponsive running mod_perlby Anonymous Monk |
on Jan 15, 2018 at 15:57 UTC ( [id://1207290]=perlquestion: print w/replies, xml ) | Need Help?? |
Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:
Please help.
Apache becomes unresponsive when it encounters an error (as reported in the error logs with an associated 500 HTTP error in the access log). I'm running Apache 2.2.29 in a windows environment with mod_perl (Apache/2.2.29 (Win32) mod_apreq2-20090110/2.8.0 mod_perl/2.0.7 Perl/v5.16.3 ). When a request results in an error all subsequent requests fail. The Apache service is still up and running but requires a restart for requests to begin to process again. I've begun by trying to fix any code that would result in an error but it's difficult to account for them all. Could mod_perl be somehow caching error responses? Is there a way to have Apache recover by itself? (This is an old legacy system which I'm trying to support). Any help would be most appreciated. Here is a sample of one of the errors encountered:
Discipulus added code tags to the error
Back to
Seekers of Perl Wisdom
|
|