Database Error: Lost connection to MySQL server during query

[[unplugged]]

I have been noticing this error not only on my SMF1 test site, but on two other sites I help with. I have only noticed it starting today. The error message is exactly the same for all three sites, and makes it rather difficult to navigate as you have about a 10% chance of actually making it to the page.

Database Error: Lost connection to MySQL server during query
File: /Sources/Security.php
Line: 279

Same line number on all three sites. All three sites are running SMF1.1.6.  As far as I know, they are all three on different hosts/servers, too.

Anyone else getting these errors? Any solution? Thanks in advance.

[70charger_boy]

I'm getting these errors, too.  I have no idea how to fix it. 

[FullDraw]

The main Sponsor of my site cannot even get on the site to try to login anymore because of these errors.  This is only the second person to have reported these kind of errors since I started the site in Feb.

Database Error: Lost connection to MySQL server during query
File: /home/content/f/o/b/fobnation/html/SMF/Sources/Security.php
Line: 279Database Error: MySQL server has gone away
File: /home/content/f/o/b/fobnation/html/SMF/Sources/Load.php
Line: 2015
__________________

[TroyG]

I have had 4 people yesterday report the same problem to me. Here is what they are getting. Any Ideas?

Database Error: Lost connection to MySQL server during query
File: /home/content/b/r/i/briananddaniel/html/simplemachinesforum/Sources/Security.php
Line: 279

And Line: 600

[jepot5]

Hope it's just a server timed out error

[Adish - (F.L.A.M.E.R)]

Are you all 3 over a same host ? if so, then it maybe the host who may have restarted his Phpmyadmin, and hence causing these errors.

[karlbenson]

Mysql Gone Away / Lost connection to server during query

http://dev.mysql.com/doc/refman/5.0/en/gone-away.html

If you are receiving an error that Mysql has "gone away" or lost connection to the server during query it is probably because either the server has timed out or the server closed the connection part way through loading the page.

In order to resolve the problem you may need to increase these two values in mysql.ini or my.cnf (different Operating Systems use different files) , and restart mysql.
wait_timeout = 28800
connect_timeout = 28800
(Figures used are the default values in seconds = 8hours).

This error is usually occurs on cheap shared servers where the above values have been changed from default and set far too low. (In an attempt to keep database server very responsive, but to the expense of basic usability).

If you don't have access to change these settings (most likely if you are on Shared Hosting), then you'll need to ask your host to do.

However some hosts may refuse to increase the values.  In that case the only solution therefore would be to find a better host.

[[unplugged]]

I don't think my situation is host related. I have 3 sites, my main site (which has no problems) and two test sites that share a database, yet only test site 1 has issues. I would think that if it were a MySQL setting, then it would affect both sites. The only difference between the two sites is the version of SMF. Test site 1 is running SMF 1.1.6 (and is the one with issues), and test site 2 is running SMF 2.0 Beta 4.

I really appreciate everyone's time on looking at this problem. Thank you.

[jmcrey]

I'm haveing users of my forum report this problem to me as well.  I never get it myself but users are.  One of my users says he has the same problem when going to a different site that uses SMF.

This only started happening when I upgraded to 1.16.

I use Godaddy as my hosting site so I doubt it is a cheap server issue.

Any thoughts?  (My users are getting frustrated)

[karlbenson]

jmcrey, Actually Godaddy shared hosting is a prime example of cheap hosting (bordering on overselling)

[tromero]

I am also experiencing this issue as reported by three different users.  I'm anxious to learn of a fix as well.

[[unplugged]]

I have 4 sites, all of which use GoDaddy, yet only one site has this database problem. Two sites are running SMF 2.0 Beta 4 with no problems at all. One site is running SMF 2.0 Beta 3.1 with no problems at all. The problem site is only the one running SMF 1.1.6, so I really don't think GoDaddy is the issue.

[dracius]

See this thread http://www.simplemachines.org/community/index.php?topic=262218.40 for more details.

I'm going to see about changing my hosting this weekend and get this problem resolved once and for all. Does anyone have any hosting recommendations however?

[JimM]

There have been lots of post like this lately.  Oversold hosting is usually the problem.  SunKing, according to myIPneighbors.com you have 662 neighbors sharing your IP address.  That is oversold and overloaded!

@FullDraw - you have 666 sites being hosted with your same IP.

See the pattern?

[[unplugged]]

That would make perfect sense why I was having problems, except for the fact that all four sites are on the same host. In fact, I only use two databases. So the problem site is on the same database as a non-problem site. I also help with several other sites that are experiencing this as well. The common denominator among all of the problem sites is SMF 1.1.6. I have yet to see this error arise on any version of SMF 2.0.
I am not saying that less-than-par hosts don't cause problems, I am simply saying that in these particular cases, I really do not feel the host(s) are the issue.

[guyske]

The same problem started when updating to 1.6, on a test site 1.5 on the same account (server) i don't have any problems...
There are 3 databases on my account, all tree aprox 500 users and between 35.000 and 55.000 postings.
The two sites on 1.6 bingo, the one still 1.5 no problems.

Databasefout: MySQL server has gone away
Bestand: /home/XXXXXXXXX/public_html/XXXXXXXXX/Sources/Post.php
Regel: 1994

Bestand: /home/xxxxxx/public_html/xxxxxxxx/Sources/Subs-Post.php
Regel: 1467

Databasefout: MySQL server has gone away
Bestand: /home/xxxxxxxxxx/public_html/xxxxxxxxx/Sources/Post.php
Regel: 1994

I even have the feeling that it is only happening at a limited number of users.

Problem is temporarily solved after repairing or optimization.

[FullDraw]

There have been lots of post like this lately.  Oversold hosting is usually the problem.  SunKing, according to myIPneighbors.com you have 662 neighbors sharing your IP address.  That is oversold and overloaded!

@FullDraw - you have 666 sites being hosted with your same IP.

             See the pattern?

Thanks for the info Jim...

I was told by another source that in godaddy's case they could have the wait timeout variable set too low. I checked mine and it is set @ 30. But I could not figure out a way to change it in the configuration.

[[unplugged]]

4 sites all on GoDaddy....only 1 site with problems....it's not GoDaddy.

[dark green]

I also had this start happening right after moving to 1.1.6.

Site is pretty useless right now...

Looking at the php it looks like that line is checking to see if I'm banned? I note that if I clear all cookies (so no PHP session record) the problem doesn't happen, and once I log in it doesn't happen anymore. It seems like an issue with checking to see if people are banned and it seems to be highly correlated to 1.1.6 - could there be problems in first retrieving the session info or in the DB structure associated with that?

[SlammedDime]

Do you use Cox as your ISP?  And GoDaddy for your hosting?