Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

My web hosting company recently replaced suPHP with fcgi on my dedicated server because I needed opcode functionality. Since then I see loads of 500 errors in apache error and php error log is empty. I have no way to figure out whats the root cause. One reason I found out was time out so my hosting company changed FcgidConnectTimeout and FcgidIOTimeout to a value of 200. I believe there are no more timeout errors in my php script.

My question is how do I capture PHP error before 500 internal server error page display to user?

I am using Centos 5.8 server, WHM 11.34.0 (build 9), PHP 5.3.18 and Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_fcgid/2.3.6

share|improve this question
    
You get the PHP error logs from your hosting provider. –  Michael Hampton Nov 29 '12 at 17:07
    
I have setup error log filename in php.ini and all php error go there. –  Maximus Nov 29 '12 at 17:45
    
OK, so now you READ the error logs. –  Michael Hampton Nov 29 '12 at 17:46
    
@Michael, I think you haven't read my question! I have already setup it and there are no errors. Apache error log shows loads of 500 error but NOT PHP! –  Maximus Nov 29 '12 at 22:50
    
If PHP isn't throwing the errors, then Apache is, and you look at Apache's error log. –  Michael Hampton Nov 30 '12 at 2:03

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.