Site Down - Need Help! 500 Internal Server Error

[orangefrog]

Well, it's been a while since I've been here. I launched a site over a year ago running CMS Made Simple and my client called me this week and told me that the site was down. Since I didn't host the site, I figured maybe the host reset the permissions or something simple and it would be an easy fix.

Three days later, I'm still trying to get the damn thing working. I can;t even access the admin due to the 500 internal server error. I'e tried installing the latest version, but it errors out during the second screen with a session test=1 error.

I'm pulling my hair out here! Anyone got any ideas what I can try? Really need to get this working...any help would be greatly appreciated.

So the domain is http://www.wadesurvey.com and the only visible is "Site down for maintenance". Outside of that, I can't access anything!

[calguy1000]

congratulations!!!

That's all I can say since you have provided absolutely no information for us to be able to help you with.

[orangefrog]

Well CalGuy, seems that time hasn't tempered you at all.

I wish I could tell you anything else but it's been so long I can't remember what version i installed. Also, since I can't get access to the admin, I can't get any other information. And, the page only loads the 'Site Down Message' message. So I can't even do a error trace.

And the host my client is with offers no support, no error logs and will not tell me anything other than the issue is on the 70th line "require_once($dirname.'/include.php');".

Other than that, I have nothing and can't get access to anything. Hell, I can't even install a new version of CMSMS.

[calguy1000]

the version of CMSMS is available by reading the version.php file. BTW, the only supported versions of CMSMS at this point are 1.11.2.1 and 1.11.3.

Of course if you can't get to that file, and/or can't get an error message, and/or can't get any hep out of your host then you have a very bad host. and there is still nothing that anybody can do to help.

I recommend you restore the backup (there is a backup right). To a new host where you can get the information you need. And just change the DNS information.

[orangefrog]

Version is 1.9.4.3. And yes the host sucks ass. Never ever use Shaw as a host!

I've already initiated the backup and still the same error. Ok, here's a question...What would be the reason that the site would only display "Site down for maintenance."?

[calguy1000]

two reasons:

1: there's a file callled SITEDOWN in the tmp/cache directory
(this usually only exists when you overwrite an existing install with the contents of a release).
or
2: An authorized administrator has enabled the sitedown behavior in 'global settings' and hasn't changed the message.

[orangefrog]

Ok, but why wouldn't I be able to log into the admin if it's only a setting that was changed? I deleted the SITEDOWN file on the server and it went to the 500 internal error which is the same error I get when I try and login.

[calguy1000]

a 500 error only tells you that there was an error.

In order to find out what the error is you need to look at the logs.

And again... I wish I had $1 for every time I've said this...
but have you tried enabling debug mode?

[orangefrog]

Oh, and I get this message when I try the install


"The website encountered an error while retrieving http://www.wadesurvey.com/install/index ... siontest=1. It may be down for maintenance or configured incorrectly."

[orangefrog]

And yes, I tried the debug mode and got nothing, just the Site Down For maintenance message.

My though is somewhere along the line the site is broken (like duh), but I think the host did something like reset the permissions or upgraded PHP or something simple, but enough to break the site.

[Jos]

maybe you could try debug mode after restoring the backup, and before trying to upgrade?

[orangefrog]

Ok, I've tried re-initiating the backup and nothing. I've tried upgrading and nothing. I can;t even execute a php info file. So, that tells me it's nothing to do with the site or CMSMS and something to do wit the crappy server it's on. I've contacted the support for the server and they are looking into. Hopefully these brain dead support idiots can finally figure something out. Thanks to every one for your help and I'll post what the problem is when they figure it out.

[gully]

So, that tells me it's nothing to do with the site or CMSMS and something to do wit the crappy server it's on. I've contacted the support for the server and they are looking into.

Something you might look into; your DNS for wadesurvey.com It appears VERY messy.

WHOIS says your nameservers are:

Code: Select all

Domain servers in listed order:
    NS1.SHAWHOSTING.CA  
    NS3.SHAWHOSTING.CA  
    NS2.SHAWHOSTING.CA

... yet a dig using NS1.SHAWHOSTING.CA reveals:

Code: Select all

12/01/12 14:30:30 dig wadesurvey.com @ NS1.SHAWHOSTING.CA
Dig wadesurvey.com@NS1.SHAWHOSTING.CA (209.235.133.79) ...
Authoritative Answer
 Query for wadesurvey.com type=255 class=1
  wadesurvey.com A (Address) 69.49.101.57
  wadesurvey.com MX (Mail Exchanger) Priority: 10 mx1c11.megamailservers.com
  wadesurvey.com MX (Mail Exchanger) Priority: 100 mx2c11.megamailservers.com
  wadesurvey.com MX (Mail Exchanger) Priority: 110 mx3c11.megamailservers.com
  wadesurvey.com NS (Nameserver) ns1.meganameservers.com
  wadesurvey.com NS (Nameserver) ns2.meganameservers.com
  wadesurvey.com NS (Nameserver) ns3.meganameservers.com
  wadesurvey.com SOA (Zone of Authority)
        Primary NS: ns1.meganameservers.com
        Responsible person: postmaster@meganameservers.com
        serial:1007
        refresh:86400s (24 hours)
        retry:3600s (60 minutes)
        expire:3600000s (410 days)
        minimum-ttl:86400s (24 hours)
  wadesurvey.com NS (Nameserver) ns1.meganameservers.com
  wadesurvey.com NS (Nameserver) ns2.meganameservers.com
  wadesurvey.com NS (Nameserver) ns3.meganameservers.com
  mx1c11.megamailservers.com A (Address) 69.49.101.234
  mx2c11.megamailservers.com A (Address) 69.49.101.235
  mx3c11.megamailservers.com A (Address) 69.49.101.236
  ns1.meganameservers.com AAAA (IPv6 Address) 2001:1810:9980:2:0:0:0:10
  ns1.meganameservers.com A (Address) 69.49.97.150
  ns2.meganameservers.com AAAA (IPv6 Address) 2001:1810:1000:2:0:0:0:10
  ns2.meganameservers.com A (Address) 209.235.143.97
  ns3.meganameservers.com AAAA (IPv6 Address) 2001:1810:4000:2:0:0:0:10
  ns3.meganameservers.com A (Address) 209.235.144.105

... more when you query ns1.meganameservers.com

Visit: http://dns.robtex.com/wadesurvey.com.html#summary

Problems 'might' reside in these DNS configs. Just a suggestion.

/gully

ps. http://web.archive.org/web/201102022018 ... urvey.com/

...and others. Probably not your real directories.

[orangefrog]

Well...Got it figured out. After asking the host repeatedly if anything had changed on the server or if any upgrades were done and getting no as an answer, I find out the little fu&*ers moved the site to a different server! Which, has a completely different root directory and everything else.

So, once figuring that out, I've had to re-install CMSMS due to corrupted files with the move. Oh, and they hadn't activated PHP on the new server when the moved the site either! So, that was another pain in the ass I had to tel them.

Anyway, long story short, if your site just dies for no reason, first check the root_path and make sure php is enabled before doing anything else. Boy will you save yourself a ton of time and headache!

Thanks again to all for you help and in put...especially you CalGuy. Man I miss this place...