Complete GoDaddy Failure

Permalink
The site I'm working on, quesclamation.com, no longer wants to work at all. I have the newest Concrete5 installed there, and I have caching on. I already did the usual API and jQuery edits on it, to no avail. Either pages load with excruciating slowness, or they completely fail to load at all. Any idea what's going on, and what I can do to resolve the issue? Thanks so much in advance. :)

 
Brainakazariua replied on at Permalink Reply
Brainakazariua
I see it results in a 500 Internal server error.

The error usually points towards the read-write-execute rights on files/folders or to the files/folders having a wrong user/group appointed to them.

In this case I suggest you check those or contact your hosting provider to check them for you.
MatthewMaldonado replied on at Permalink Reply
I contacted GoDaddy in regards to that situation, and they report nothing out of the ordinary. Are they just crazy, or is there something else happening with my Concrete5 installation?
Brainakazariua replied on at Permalink Reply
Brainakazariua
I've been looking a bit further on your site. I see that going tohttp://www.quesclamation.com/concrete/... results in a nice 404 page.

Can you make sure your site is in the root of your site and not in some subdirectory of it.
Also try to get a hold of the error log and check that or post it here for us to check it.
MatthewMaldonado replied on at Permalink Reply
The site's definitely in the root. Here's what the error log is showing me right now:

[Mon Jan 17 09:42:01 2011] [error] [client 173.164.52.81] FastCGI: server "/var/chroot/home/content/q/u/e/quesclobang/html-x-httpd-php5" stderr: Set Area
[Mon Jan 17 09:43:02 2011] [error] [client 173.164.52.81] FastCGI: comm with (dynamic) server "/var/chroot/home/content/q/u/e/quesclobang/html-x-httpd-php5" aborted: (first read) idle timeout (60 sec)
[Mon Jan 17 09:43:02 2011] [error] [client 173.164.52.81] FastCGI: incomplete headers (0 bytes) received from server "/var/chroot/home/content/q/u/e/quesclobang/html-x-httpd-php5"
[Mon Jan 17 09:43:03 2011] [error] [client 173.164.52.81] FastCGI: comm with (dynamic) server "/var/chroot/home/content/q/u/e/quesclobang/html-x-httpd-php5" aborted: (first read) idle timeout (60 sec)
[Mon Jan 17 09:43:03 2011] [error] [client 173.164.52.81] FastCGI: incomplete headers (0 bytes) received from server "/var/chroot/home/content/q/u/e/quesclobang/html-x-httpd-php5"
[Mon Jan 17 09:55:37 2011] [error] [client 173.164.52.81] FastCGI: comm with (dynamic) server "/var/chroot/home/content/q/u/e/quesclobang/html-x-httpd-php5" aborted: (first read) idle timeout (60 sec)
[Mon Jan 17 09:55:37 2011] [error] [client 173.164.52.81] FastCGI: incomplete headers (0 bytes) received from server "/var/chroot/home/content/q/u/e/quesclobang/html-x-httpd-php5"
[Mon Jan 17 10:10:08 2011] [error] [client 173.164.52.81] FastCGI: comm with (dynamic) server "/var/chroot/home/content/q/u/e/quesclobang/html-x-httpd-php5" aborted: (first read) idle timeout (60 sec)
[Mon Jan 17 10:10:08 2011] [error] [client 173.164.52.81] FastCGI: incomplete headers (0 bytes) received from server "/var/chroot/home/content/q/u/e/quesclobang/html-x-httpd-php5"
[Mon Jan 17 10:10:13 2011] [error] [client 173.164.52.81] FastCGI: comm with (dynamic) server "/var/chroot/home/content/q/u/e/quesclobang/html-x-httpd-php5" aborted: (first read) idle timeout (60 sec)
[Mon Jan 17 10:10:13 2011] [error] [client 173.164.52.81] FastCGI: incomplete headers (0 bytes) received from server "/var/chroot/home/content/q/u/e/quesclobang/html-x-httpd-php5"
[Mon Jan 17 10:14:49 2011] [error] [client 173.164.52.81] FastCGI: server "/var/chroot/home/content/q/u/e/quesclobang/html-x-httpd-php5" stderr: Set Area
Brainakazariua replied on at Permalink Reply
Brainakazariua
Seems like a header problem. This might be server related or caused by your theme.
Can you possibly open the dashboard and try a different theme to see if that solves the problem?
MatthewMaldonado replied on at Permalink Reply
I tried reverting to the default them, with no apparent result. =(
Brainakazariua replied on at Permalink Reply
Brainakazariua
Alright, I've been looking around a bit on this forum, seems there are more people having problems with fastCGI. It usually times out, I suggest you increase the timeout so it won't kill php before it can run.

another option is that the pretty urls are causing the problem as stated in this topic:http://www.concrete5.org/community/forums/usage/mod_rewrite_on_goda...
MatthewMaldonado replied on at Permalink Reply
Alright, that seems to have resolved the 500 errors, but the whole thing is still slow as sin. Any ideas on how to oil the wheels on this thing?
Brainakazariua replied on at Permalink Reply
Brainakazariua
For the speed I suggest you try out the steps in this How-to written by Andrew:http://www.concrete5.org/documentation/how-tos/developers/five-easy...
lostsoul replied on at Permalink Reply
lostsoul
Nothing you do on a Godaddy server will speed up your site. Godaddy is a total failure with C5. Trust me on this. I lost count of how many postings I wrote looking for help.

The only this I say is use BlueHost or A2Hosting. Get away from Godaddy.
carlos123 replied on at Permalink Reply
I agree that GoDaddy is a terrible host but if I may suggest...ask them if your MySQL database is on a grid based server or not. If it is not insist that they move it to a grid based server (grid being one where requests are actually served up by multiple servers or a grid).

That should speed up your site substantially all other things being equal.

They don't seem to like moving database to grid (perhaps because they are concerned that everyone will do this...I don't know) but I had a client whose site was real slow and we solved that by doing what I suggest.

Carlos
lostsoul replied on at Permalink Reply
lostsoul
I did ask in the past all that but like you said they don't like doing that. Mostly because they don't have grid for regular hosting and they don't want to set those up.

You have to take in to account that GD markets to users who tend not to know anything about server technologies. Trust me on this, those of us that actually know server tech. Most of the time we know more then their server tech.
carlos123 replied on at Permalink Reply
If you insist such that if you don't get it, that you will have no choice but to consider moving to another host like Hostgator (far better in my experience) I think GoDaddy will put you on grid based MySQL "server".

It's either that or they will lose a customer.

Incidentally...I am just thinking outloud...I've been thinking of offering a C5 move service to Hostgator for cheap (given that they give me $50/$75 for every new customer I get them). Is there a way to offer such a thing here on this forum?

Carlos
hpatel replied on at Permalink Reply
I just had to move a site to BlueHost from Go Daddy. Client was using GD to host but I couldn't take the slow load time.