500 internal server error - SITE DOWN


#1

I signed over to dreamhost two days ago for a year…and this is the 2nd time my site is down for an extended period (3-4 hours now). I was assured when signing over (I gave the specifications for my database - size, operations etc) that dreamhost would have no difficulty in hosting my site. In fact the only reason I switched from my previous host is because I was having database issues with them. I contacted dreamhost letting them know of my difficulties and they said this site would run great on dreamhost.

Why did the sales team say that it would be ok if I’m now being sent this link and NO support as Gracie said this morning: “Unfortunately, we can’t troubleshoot code as we are not web developers.”

http://wiki.dreamhost.com/Mysql#MySQL_limitations_due_to_shared_hosting

support sent me the above but it does nothing to explain why I’m experiencing a site that won’t stay online for long.

why waste peoples time with a service that is slow and unusable?

I specifically asked if I would violate resource limits and was told that my database size was perfectly ok for dreamhost. Now I sign over, my site is down the majority of the time, I’ve handled over my credit card details…and no support?

THIS IS THE ONLY REASON I SWITCHED TO DREAMHOST. It was your sales people who assured me I should change so that I could get my site working again.

Very frustrating


Internal Server Error

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

Please contact the server administrator, webmaster@findgoodmusic.com 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.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.


[hr]
LOG OF COMMUNICATION BEFORE SIGN OVER. After reading this perhaps you will understand why its like a cold slap in the face to be given no support and sent a link to mysql_restrictions.


Hello Kias,

I’m happy to help today. Based on the information you’re provided you
should have no issue with hosting the site using our shared hosting plan.

There has been a changed though in the max db size, that is now 3GB per
db and not 4GB as was previously mentioned. That said you are free to
have multiple dbs under that limit. Again based on the information you
have provided it would likely take you a good long while to have the be
an issue for you.

I hope that helps a bit. If you need anything else or have any other
questions please let me know.

Thanks,

Christopher P

On Mon, 10 Jun 2013, you wrote:

Hi there,

So please confirm that my current specs:

700mb mysql database with 1.5 million rows, each with 50 values each (all

text tho no blob data)

50mb of html file space with the /img directory for site

would be suitable for the $3.95 shared hosting plan on dreamhost? my site

gets an average of 70 unique visitors per day but this could rise drastically

down the track…

my current host which charges me $3.95 is now threatening to ban my site

saying that my 700mb database is violating their fine print concerning

limitations on the amount of ram being used. They won’t give me any clear

answers about what is going wrong and why mysql access keeps getting blocked

until i email them. Apparently my database is violating many of the fine

print terms…but I’ve been reading online, and 700mb is not a huge

database… by any means…its getting there, but medium is considered 2gb by

many. And with only 70 visits a day, I highly doubt my site is actually

using up all their memory. They have a restriction on timeout for a

database, eg tonight i tried to delete a row from this database… their

server took too long or so and then they banned me once again from being able

to access phpmyadmin.

Please get back to me, if we confirm there would be no problems as long as I

keep this database under 4gb? I can’t see it going over 2 to be honest, but

it might.


#2

the site has been down for six hours today :frowning: It only just came back on…surely there must be a quicker solution for internal 500 errors than this. I tried to log back in ssh which i could access last night, and it just kept freezing out just like the site.


#3

ok sites back up… im indexing my database fields… lets see if that helps…


#4

If you couldn’t log in to SSH then it seems the problem was more than a database issue.