sql server repeatedly going down - why? - GoFuckYourself.com

MrBottomTooth · 03-20-2011, 03:12 PM

What would cause an sql server to keep going down, usually daily?

Getting frustrated with seeing my sites go down constantly. Host fixes it when I email them, but then the same thing happens the following day.

Anyone experience this before?

MrBottomTooth · 03-20-2011, 03:26 PM

Quote:

Originally Posted by pornopete

get your programmer to look at it.

I don't have a programmer. this is just a shared hosting account at phatservers. Usually they have been great but this problem started up a couple weeks ago and they can't seem to lick it permanently.

Kiopa_Matt · 03-20-2011, 03:30 PM

Quote:

Originally Posted by MrBottomTooth

this is just a shared hosting account

And there's your problem. It's probably some other domain on the server with shitty software installed, sucking up the resources. Or something to that effect.

Go dedicated.

3xmedia · 03-20-2011, 03:33 PM

Quote:

Originally Posted by MrBottomTooth

I don't have a programmer. this is just a shared hosting account at phatservers. Usually they have been great but this problem started up a couple weeks ago and they can't seem to lick it permanently.

happened to me as well with that host. ask them to move your sites to another server.

baddog · 03-20-2011, 04:38 PM

Since it is a shared server, all you can do is your part to keep scripts updated, delete databases you don't use and stuff like that. If this just started happening I would think they would want to figure out who is causing it, so might mention it.

CashOnClick · 03-20-2011, 04:58 PM

What do you mean exactly by going down ? ... is it an error page that says there is to many active connections for the user ? or something else ?

There is several solutions to the problem but it all depends on you answering the above in order to tell you what the correct one is

Then I am pretty sure I can help.

P.S. I do know some shared hosts have been updating software as of late and know this is throwing up unexpected MySQL problems that did not exist before...

Quote:

Originally Posted by MrBottomTooth

What would cause an sql server to keep going down, usually daily?

Getting frustrated with seeing my sites go down constantly. Host fixes it when I email them, but then the same thing happens the following day.

Anyone experience this before?

MrBottomTooth · 03-20-2011, 05:07 PM

Quote:

Originally Posted by CashOnClick

What do you mean exactly by going down ? ... is it an error page that says there is to many active connections for the user ? or something else ?

There is several solutions to the problem but it all depends on you answering the above in order to tell you what the correct one is

Then I am pretty sure I can help.

P.S. I do know some shared hosts have been updating software as of late and know this is throwing up unexpected MySQL problems that did not exist before...

It is just a recent thing. Never had problems before.

On one site where I have phplist installed, it just brings up an error that says the sql server is not running.

If I try to reach a blog running wordpress, I'm pretty sure it gives a http error 500 internal server error.

There's never any mention of too many connections, etc.

They are able to fix it after I email them about it in a few minutes, but I can usually look forward to it going down again sometime the following day.

blackmonsters · 03-20-2011, 05:13 PM

Quote:

Originally Posted by pornopete

1. never use shared hosting.

I used shared hosting for 10 years without a problem except on phatsevers.

I would submit to the hun and get 100k hits/30Gigs per day on my shared server with
no problem when hosted else where.

It depends on the host.

You can share a 747 jet and kick ass or you can get a dedicated moped and go no where.
This all depends on the host.

Phatsevers kicked me off their shared servers when I was doing 1500 hits a day.

Go figure bro.

DangerX !!! · 03-20-2011, 06:25 PM

I had once such kind of problem and it appeared to be that there was not enough ram resources and this was causing system to automatically shut down MySQL. My host added more ram and server monitoring to ensure MySQL will always be up.

MrBottomTooth · 03-20-2011, 08:00 PM

Sounds like they have it fixed now. Something to do with forgetting to re-enable mysql monitoring after they fixed the original issue that was causing the downtime a week ago. (crosses fingers)

CashOnClick · 03-20-2011, 11:16 PM

That don't sound right to me...

The were able to fix it because in layman's terms they cleared the the list of requests for the user .. user being the the the username used in your site to access the database... The timeout for that to automatic clear is about 8 hours.

If you have a lot of say wordpress blogs running then you need to study your header and footer files for your theme you are running and hardcode certain elements like : Title, Keywords, Description, Canonical and anything else that can remain static without having to make a request from the database to look up the results to display.. that will cut down on a load of requests to start with... Also consider using caching for your blogs / sites pages that make use of MySQL

P.S. Also see if your host will up the number of requests to say 60 ... I think the default is about 30 ? ... If a combination of all the above does not fix the problem then you really need to get a dedicated server and make additional settings yourself in php.ini

03-20-2011, 03:12 PM	#1
MrBottomTooth Confirmed User Join Date: Sep 2009 Posts: 5,795	sql server repeatedly going down - why? What would cause an sql server to keep going down, usually daily? Getting frustrated with seeing my sites go down constantly. Host fixes it when I email them, but then the same thing happens the following day. Anyone experience this before? __________________ Get Paid Per Email Like The WEGCASH Days!!!!

03-20-2011, 06:25 PM	#9
DangerX !!! Confirmed User Industry Role: Join Date: Feb 2011 Location: La Isla Bonita Power Level: ❤❤❤❤❤❤❤❤❤❤ Posts: 886	I had once such kind of problem and it appeared to be that there was not enough ram resources and this was causing system to automatically shut down MySQL. My host added more ram and server monitoring to ensure MySQL will always be up. __________________ This is sig area!

03-20-2011, 08:00 PM	#10
MrBottomTooth Confirmed User Join Date: Sep 2009 Posts: 5,795	Sounds like they have it fixed now. Something to do with forgetting to re-enable mysql monitoring after they fixed the original issue that was causing the downtime a week ago. (crosses fingers) __________________ Get Paid Per Email Like The WEGCASH Days!!!!

03-20-2011, 11:16 PM	#11
CashOnClick Confirmed User Join Date: Mar 2010 Posts: 122	That don't sound right to me... The were able to fix it because in layman's terms they cleared the the list of requests for the user .. user being the the the username used in your site to access the database... The timeout for that to automatic clear is about 8 hours. If you have a lot of say wordpress blogs running then you need to study your header and footer files for your theme you are running and hardcode certain elements like : Title, Keywords, Description, Canonical and anything else that can remain static without having to make a request from the database to look up the results to display.. that will cut down on a load of requests to start with... Also consider using caching for your blogs / sites pages that make use of MySQL P.S. Also see if your host will up the number of requests to say 60 ... I think the default is about 30 ? ... If a combination of all the above does not fix the problem then you really need to get a dedicated server and make additional settings yourself in php.ini __________________ Cash On Click \| Pornstar Mega Sites \| $25 PPS \| 60% / 60% REVS Last edited by CashOnClick; 03-20-2011 at 11:22 PM..

03-20-2011, 04:38 PM	#5
baddog So Fucking Banned Industry Role: Join Date: Apr 2001 Location: the beach, SoCal Posts: 107,089	Since it is a shared server, all you can do is your part to keep scripts updated, delete databases you don't use and stuff like that. If this just started happening I would think they would want to figure out who is causing it, so might mention it.