hlcornish Posted August 18, 2011 Share Posted August 18, 2011 Backstory: Yesterday about lunch time, our entire site went down. It threw the "Internal Server Error". So we call the host, and they said it was a problem on our end. (Something we'd done or downloaded, or a file problem, etc.) Turns out the original creator of the site (one of the team) had an error log file writing on our live site that had gone bad, and was something like 400 GB large. When deleted and the files uploaded, the site shows back up. We thought that was the end of it...mistakenly. Our administration module (content management of sorts, OS commerce based) is still down in the same fashion. My cohort was in here until 9pm trying to fix it, and we still can't figure it out. html and htm files load fine. It's all the php files. The admin is on the same domain and host...and our main website is mainly PHP, but is working? Running out of ideas here...has anyone run into this with OS Commerce or PHP files therein? Here is our source code when viewed from internet explorer for the admin login page: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content="text/html; charset=windows-1252" http-equiv=Content-Type></HEAD> <BODY></BODY></HTML> Quote Link to comment Share on other sites More sharing options...
PFMaBiSmAd Posted August 18, 2011 Share Posted August 18, 2011 It would help if you posted the source code of the page that is being browsed to that is producing that output so that someone could see what the php code should be doing, because we don't have any idea even what version of OSC you are using or of what modifications you might have made to the source code. Quote Link to comment Share on other sites More sharing options...
hlcornish Posted August 18, 2011 Author Share Posted August 18, 2011 My apologies. I am not top of the heap here, and they don't want code posted. It seems I have wasted your time. Some kind of company policy...I guess we're supposed to muddle through. Quote Link to comment Share on other sites More sharing options...
PFMaBiSmAd Posted August 18, 2011 Share Posted August 18, 2011 The best recommendation when developing and debugging any php code is to have error_reporting set to E_ALL and display_errors set to ON in your master php.ini so that all the php detected errors will be reported and displayed. If output_buffering is on, you should turn it off so that any header() redirect statements won't cause any error messages to be hidden/discarded when the redirect occurs. Confirm using a phpinfo() statement that those two settings changed in case the php.ini that you are changing is not the one that php is using. Quote Link to comment Share on other sites More sharing options...
Doug G Posted August 18, 2011 Share Posted August 18, 2011 I read in the news last week there was some kind of hack attack going on against osCommerce sites. Perhaps something more for you to research. http://www.usatoday.com/money/industries/technology/2011-08-11-mass-website-hacking_n.htm Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.