After update today 500 errors on entire server!!

lynnette

Member
Mar 27, 2004
19
0
151
Just checking the logs now. Just the normal scripts/upcp everything was fine before it. No manual changes made.
 

lynnette

Member
Mar 27, 2004
19
0
151
The logs are just showing Premature End of Script Headers and Invalid method in request \x16\x03\x01
 

lynnette

Member
Mar 27, 2004
19
0
151
Found this error message at the very start of the other errors:

Request exceeded the limit of 10 internal redirects due to probable configuration error Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace

But that was at the start and not since.

Also rebuilt apache with no difference
 
Last edited:

lynnette

Member
Mar 27, 2004
19
0
151
Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.
==========================================
Just when we are trying to get to the websites
 

lynnette

Member
Mar 27, 2004
19
0
151
Well its fixed, rebuilt apache without mod suphp then rebuilt it again with and now it all works.
 

thewebhosting

Well-Known Member
May 9, 2008
1,199
1
68
Well its fixed, rebuilt apache without mod suphp then rebuilt it again with and now it all works.
Great to here your issue is resolved. Basically, suPHP is more secure for running PHP applications. It will prevent 777 permissions to files and folders. With suPHP 777 is equivalent to 755. It was giving 500 error because of 777 permissions of your website files and folders.
 

lynnette

Member
Mar 27, 2004
19
0
151
Great to here your issue is resolved. Basically, suPHP is more secure for running PHP applications. It will prevent 777 permissions to files and folders. With suPHP 777 is equivalent to 755. It was giving 500 error because of 777 permissions of your website files and folders.
We have always had suphp on our server with no problems, so it wasn't a permissions issue. We had to rebuild apache without it and then rebuild it again with it, so all I can assume is there was a problem with suphp.
 

gmartins

Registered
Nov 13, 2008
2
0
51
Explanation of the solution

Form some reason, apache can't handle suphp logs greatest than 2 GB.
So if you are experiencing this kind of problem, please go and check your:

/usr/local/apache/logs/suphp_log

If is more than 2 GB, sure it is the cause of the problem.
Rename it, so cPanel creates it again, clean :)

And all is working again !

Bye!!

German.:)
 

ModServ

Well-Known Member
Oct 17, 2006
337
5
168
Egypt
cPanel Access Level
Root Administrator
I totally agree with gmartins. suPHP log can handle a maximum of 2GB, So when you removed and installed again the logs rotated so the site worked well. From WHM go to Apache Configuration then Log Rotation then enable suphp_log and click save, That will rotate it automatically to not face this problem again.