All of a sudden all .php files inside my server causes INTERNAL SERVER ERROR.

I'm not sure whether it's related, however it began as i was upgrading yummy.

Even blank .php files may cause the mistake. I have moved My website content and tryed merely a empty .php file but still it provides the same error.

There is no .htaccess files also.

What must i do? =/

(Other sites in the same server will work fine)

Apache and php logs does not appear to become upgrading. Apache's last come from today, there is however nothing associated with the problem. PHP's last come from APRIL

UPDATE

I simply found each domain features its own Apache log.

Here what's during this site

[Thu Jul 28 22:04:02 2011] [error] [client 173.245.56.24] Premature end of script headers: cgi_wrapper
[Thu Jul 28 22:04:02 2011] [error] [client 173.245.56.168] suexec policy violation: see suexec log for more details
[Thu Jul 28 22:04:02 2011] [error] [client 173.245.56.168] Premature end of script headers: cgi_wrapper
[Thu Jul 28 22:04:02 2011] [error] [client 103.22.200.144] suexec policy violation: see suexec log for more details
[Thu Jul 28 22:04:02 2011] [error] [client 103.22.200.144] Premature end of script headers: cgi_wrapper
[Thu Jul 28 22:04:02 2011] [error] [client 103.22.200.150] suexec policy violation: see suexec log for more details
[Thu Jul 28 22:04:02 2011] [error] [client 103.22.200.150] Premature end of script headers: cgi_wrapper
[Thu Jul 28 22:04:03 2011] [error] [client 173.245.56.168] suexec policy violation: see suexec log for more details
[Thu Jul 28 22:04:03 2011] [error] [client 173.245.56.168] Premature end of script headers: cgi_wrapper
[Thu Jul 28 22:04:04 2011] [error] [client 199.27.128.138] suexec policy violation: see suexec log for more details
[Thu Jul 28 22:04:04 2011] [error] [client 199.27.128.138] Premature end of script headers: cgi_wrapper
[Thu Jul 28 22:04:04 2011] [error] [client 103.22.200.246] suexec policy violation: see suexec log for more details
[Thu Jul 28 22:04:04 2011] [error] [client 103.22.200.246] Premature end of script headers: cgi_wrapper

I don't know, but sometimes it may be associated with permissions of the file. On the internet-host I personally use it'll provide a 505 if permission aren't set to 655 777 can give a 500 internal server error. My prediction is within the PHP distribution update with Yummy they did such like, but this is just a guess. In a nutshell look into the file permissions and when they aren't 655 then try altering these to that.

Try reading through the logs. Bare in your mind that lots of hosting when they're overloaded they throw 500 Internal Server Error even when there is no trouble with the php. It will happen my hosting that is shared account after i or someone else within the same server overcharges it

If awaiting the server to grew to become less busy or else you see no logs then you definitely should certainly speak to your hosting Support, this appear to become nothing related to PHP itself, a minimum of this is not on your side from it.

Usually such errors are triggered by endless loops ( either from .htaccess or php itself ). I recommend to test creating a clearOreasy php file and seeking for everyone it.

Another factor you might like to check are configurations associated with error confirming. While I don't know it has anything related to it, this might be triggered by something transformed in the manner the errors are reported ( as well as other modification in php.ini file).

P.S .. and yeah , as Ignacio stated : look at your error logs.