Mysql Error Never Seen On My Site Before (too Many Connections).

QUOTE(pyost @ Jul 29 2006, 09:26 PM) Nope, you can use only those that are predefined in the AdSense control panel. As a matter of fact I saw Google ads which looked a bit customized, I don't know how they did it, but I think they just added javascript, but maybe this is special ads of somekind, they really pointed to google adsense links, can't remember the site, so maybe it is possible, you always can email google adsense team, but I don't know what they could answer, it is better to ask if it is possible and not if I can, I think

Comment/Reply (w/o sign-up)

The reason you received no help on the matter is because by the time someone noticed the post, the problem was gone. SO in order to reply to your particular post, "Please wait and do not refresh your website over and over and see how things are in about an hour if the problem hasn't already be resolved."

We all share the same MySQL server. The too many connections refers to everyones connections usually. While there is a cap on the number of connections each website may have at once, the entire server also has a cap which is not as large as all of the individual accounts put together so if 10% or more of the websites are at or near their maximum, then the server could be overwhelmed. I'm not sure what the exact figures are for these settings but this is usually what happens. This usually clears up in a few minutes unless we get a few impatient people trying to get the pages to load. Now not only did you have too many connections on the server to begin with, everybody is trying to refresh the error page to get the webpage to load correctly. Few people realize that by repeatedly trying to get the page to load they are actually making the problem worse. Most database connections last less than a secondso in order to have too many connections, there has to be a lot of connection requests all at the same second for the most part.

Probably the biggest cause of this error to begin with is poor script optimization. Basicaly Joe Blow writes a script that accesses the database in a sloopy way. As a result, his sloopy code on his rather poorly designed website can have the same impact on the server as Bill's really busy and well designed website. So Joe's site kills the server then Bill's users keep the server over taxed with their page refreshes and reloads.

OpaQue tries to identify websites on the server that have this kind of negative impact on the rest of the accounts and either work with the account holder to correct the problem or if need be remove the problem file.

So my suggestion to you is to create a backup page for your website that you can use to relieve the server burden. Some kind of "Technical Difficulties" message that you can set all of your webpages to redirect to via your .htaccess file. Then when this proble comes up, just switch over to your message page and that will prevent your users from continuing the connection flood on the database server.

Better yet, rewrite your scripts to respond better to the Too Many Connections Error. If this happens instead of telling the user right away, make the script sleep for a few seconds so they don't refresh right away. A five second pause for everyone on your site could be just what the server needs to get caught up. Using a random number between 5 and 10 seconds would also keep everyone from your website from having the opportunity to refresh at the same time.

One additional suggestion, let your user know what the problem and the solution is. If you tell your user that the problem is caused by too many connections at the same time and inform them that refreshing the page will only make the problem worse, they will be less likely to add to the problem. Kindly ask them to wait a minute before they try to refresh and most will at leat give it 10 seconds. Usually, the serve doesn't need a big break, just enough to get caught up and it will be fine.

For best results, you should use all of these techniques together. If everyone used just one of these suggestions, then the server would never be down. This is particularly true for a server pause when this error occurs since the server just needs a second or two without a connection request.

Hope this helps.

vujsa

 

 

 

Comment/Reply (w/o sign-up)

Was probably too many global wide connections. The home page only makes like 2 mysql_query's that are relativly simple select statements for one field of a row.

Comment/Reply (w/o sign-up)

i think the choking points of the database server is starting to become frequent..
i dont know what is going on but judging on the number of shared hostings here..

3 malfuntioning scripts specially if they are on cron can crashed the server almost instantly...
the negative impacts of shared hosting..

Comment/Reply (w/o sign-up)