What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Authentication failed!

Status
Not open for further replies.
S

Sachpah

New Member
Joined
Aug 27, 2012
Messages
5
Reaction score
0
Honorbuddy v2.5.6419.500 started.
Logging in...
Authentication failed!


fix your bot ffs, tired of getting this message, and dont tell me to spam it, doesnt work.

and I re-downloaded it, not working..
 
Tusik said:
Servers down. Please read the announcements.
Click to expand...

Stop talking trash, Seriously get educated before making bullshit replies, read the topic! http://www.thebuddyforum.com/buddy-...141-official-server-issues-oct-18-2012-a.html it's suppose to be fixed.

Apoc said:
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!
Click to expand...
 
chuck lee how about you educate yourself .

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!
 
@chemical

'MAY' that does not mean it will happen or will not happen, seriously before trying to pick shit down on me, go back to school, I know wtf I am talking about
 
As the other have posted, this outage was to be expected.
We ask for everyone's patience while it is being fixed.
 
Auth servers seem down for me right now, hopefully they're fixing this issue? :/
 
Status
Not open for further replies.
Back
Top