Jump to content

View more

Image of the Day

Adding some finishing touches...
Follow us for more
#screenshotsaturday #indiedev... by #MakeGoodGames https://t.co/Otbwywbm3a
IOTD | Top Screenshots

The latest, straight to your Inbox.

Subscribe to GameDev.net Direct to receive the latest updates and exclusive content.

Sign up now

Why SQL error

4: Adsense

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
7 replies to this topic

#1 polyfrag   Members   

Posted 28 April 2013 - 11:24 PM

Why is the site always broken and saying there's SQL errors?

#2 slicer4ever   GDNet+   

Posted 29 April 2013 - 05:47 AM



There was a more recent discussion on the topic, but I can't seem to locate it now.  But yes, depending on your time zone(for me it's midnight), ~15-30 mins every day the site is down.

Check out https://www.facebook.com/LiquidGames for some great games made by me on the Playstation Mobile market.

#3 Hodgman   Moderators   

Posted 29 April 2013 - 06:22 AM

~2:30pm every day for me...

#4 jbadams   Senior Staff   

Posted 29 April 2013 - 07:08 AM

We are investigating, but so far we've been unable to find the cause of this one -- seems to be some regular task carried out by our provider, but so far it's been non-obvious.

- Jason Astle-Adams

#5 Michael Tanczos   Staff Emeritus   

Posted 29 April 2013 - 07:40 AM

Here is a brief synopsis of what happens:


There is a period of about 5-10 minutes where our final system activity suddenly spikes and we see a HUGE IO load that pretty much brings most of the system to a halt.    During this time the SQL server cannot answer all queries and gets about 250 queries backed up and waiting to be answered.    For a brief time the IO fluctuates up and down enough to make it possible to answer some of the queries but very few of them.   What happens is that the HTTP part of the request is answered by our reverse proxy (that's the part that says the "Site is down") and sometimes by our site software (that's the part that says SQL Error).   When it's our site software the reason for the SQL Error is "Too Many Connections".   Largely the effect is caused by the reverse proxy cache being invalidated for being down more than a few minutes, the queries getting backed up in the SQL server, and the shear number of people hitting the "WTF is going on.. refresh this shit.. damn why isn't it working?!" button.    That last button slams our server because so many of the queries used to build the page aren't even being used because the page request gets abandoned.


TL;DR - It's caused by an as-of-yet unknown high disk IO problem (which we think may be our ISP backing up the server to be honest) caused by a period of people rapidly refreshing their browser in an attempt to help us fix the problem (while also overloading the server with too many database queries too quickly).


#6 JTippetts   Moderators   

Posted 29 April 2013 - 08:10 AM

Did you try turning it off then back on? Check to make sure the cable is plugged in. Maybe the intarweb hamsters need faster hamster wheels. I have three goats; do you want to try sacrificing one of them?

#7 Bacterius   Members   

Posted 29 April 2013 - 09:17 AM

~ 4:30pm here.

“If I understand the standard right it is legal and safe to do this but the resulting value could be anything.”

#8 polyfrag   Members   

Posted 30 April 2013 - 11:16 PM

Just happened to me. Started ~10:10 PM -8:00 (pacific time).

Edited by polyfrag, 30 April 2013 - 11:16 PM.

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.