Auth servers hacked by blizzard ?
- Thread starter movah
- Start date
- Status
Vetolavman
New Member
- Joined
- Oct 10, 2012
- Messages
- 22
- Reaction score
- 0
seriously, this is to much! what is up with you people? are you trolling or are you just blind? theres 25 other posts about this today just read one of them or just go directly to the one linked on every single thread! jesus christ
Don't spread nonsense ..
Read this : http://www.thebuddyforum.com/buddy-...141-official-server-issues-oct-18-2012-a.html
Read this : http://www.thebuddyforum.com/buddy-...141-official-server-issues-oct-18-2012-a.html
Ill tell yall what I tell everyone else.
Ok everybody lets walk down to the View attachment 54050
and talk to the View attachment 54051 sitting outside.
For 15 gold he will give you a View attachment 54052
to keep blizzard from finding you and killing you.
and also keep us safe from teh View attachment 54053
Ok everybody lets walk down to the View attachment 54050
and talk to the View attachment 54051 sitting outside.
For 15 gold he will give you a View attachment 54052
to keep blizzard from finding you and killing you.
and also keep us safe from teh View attachment 54053
Nice...
just saw that "OFFICIAL"
[OFFICIAL] Server Issues (Oct. 18 2012)
These issues include Authentication failed and GB2 node issues.
Standing by
just saw that "OFFICIAL"
[OFFICIAL] Server Issues (Oct. 18 2012)
These issues include Authentication failed and GB2 node issues.
Standing by
And here's the latest announcement.
UPDATE (4:30 PM GMT):
Originally Posted by Apoc
The servers are back up for now, and we've finally tracked down the root of the issue.
Non-technical answer: There is a bug in a 3rd party library we use that causes all SQL connections to randomly stop, which causes our auth servers to be unable to "sync" with eachother, and retrieve data when required. This causes them to basically stop responding due to failsafes to avoid bigger issues (such as melting server hardware).
Technical answer:
We use MySQL's .NET Connector to handle our SQL connection (and queries) on the auth servers. There is currently a bug in the entity framework support that will cause connections to stop working after what seems like a set amount of time, or number of requests to the DB server. We've identified the issue, and are going to make changes today and tomorrow to remove the entity framework from our server software. This should resolve the problem for good, at the cost of some maintenance annoyances. We're not sure of what exactly is the cause in the MySQL connector code-base, but we do know that is where the issue originates. Unfortunately, this is one of those times where relying on a 3rd party implementation (that has been tested to work perfectly) can cause a nightmare. We must be hitting some usage case that hasn't been tested, or found a new bug in the provider.
TL;DR; We found the problem, and we'll be fixing it ASAP. Servers are up for right now, but may go back down again later today. Please bear with us!
I'm glad they finally tracked down the problem and are taking the steps to fix it. Thanks guys for all the work. Also if you guys need a spot to host some files like HB releases or something to relieve the server of a small amount of traffic at least Id be glad to set you up an FTP account or whatever you need on my server. The server is hosted in Canada and I am able to pull about 4 megabytes per second from it on downloads. ( 4 MB/s down maxes my connection at home so I'm not sure what it is actually capable of )
UPDATE (4:30 PM GMT):
The servers are back up for now, and we've finally tracked down the root of the issue.
Non-technical answer: There is a bug in a 3rd party library we use that causes all SQL connections to randomly stop, which causes our auth servers to be unable to "sync" with eachother, and retrieve data when required. This causes them to basically stop responding due to failsafes to avoid bigger issues (such as melting server hardware).
Technical answer:
We use MySQL's .NET Connector to handle our SQL connection (and queries) on the auth servers. There is currently a bug in the entity framework support that will cause connections to stop working after what seems like a set amount of time, or number of requests to the DB server. We've identified the issue, and are going to make changes today and tomorrow to remove the entity framework from our server software. This should resolve the problem for good, at the cost of some maintenance annoyances. We're not sure of what exactly is the cause in the MySQL connector code-base, but we do know that is where the issue originates. Unfortunately, this is one of those times where relying on a 3rd party implementation (that has been tested to work perfectly) can cause a nightmare. We must be hitting some usage case that hasn't been tested, or found a new bug in the provider.
TL;DR; We found the problem, and we'll be fixing it ASAP. Servers are up for right now, but may go back down again later today. Please bear with us!
I'm glad they finally tracked down the problem and are taking the steps to fix it. Thanks guys for all the work. Also if you guys need a spot to host some files like HB releases or something to relieve the server of a small amount of traffic at least Id be glad to set you up an FTP account or whatever you need on my server. The server is hosted in Canada and I am able to pull about 4 megabytes per second from it on downloads. ( 4 MB/s down maxes my connection at home so I'm not sure what it is actually capable of )
Last edited:
- Status