90002 Error Booting Players from Ultros

Going by the increasing logon queue it appears to spreading.

Same on Hyperion. :/

Got it on Exodus returning from a dungeon, looks like a Primal Data Center thing.

10105 error on Hyperion for like 10 mins now

Same thing on Excalibur

Same, Ultros!

Lamia's getting it too. Think it might be hitting Primal in general.

another primal data center problem again it seems? it happens on Bryn as well...

Same, Ultros

Famfrit too looks like a system wide tap possibly, but someones definitely doing something they shouldnt

Happening on Leviathan as well. Clearly a Primal DC thing.

this looks like it might be an attack watch your accounts closely guys

I thought it was just me ): o well to warframe!

Quote:

---

Originally Posted by Scbass00

this looks like it might be an attack watch your accounts closely guys

---

What gives you any indication? Lol

Quote:

---

Originally Posted by Scbass00

this looks like it might be an attack watch your accounts closely guys

---

Quote:

---

Originally Posted by A-Shock

What gives you any indication? Lol

---

Probably not a direct attack against our accounts. More likely someone is DDoSing and overwhealming the lobby server. The sudden queues and disconnects are an indication that this is the case.

Connection being lost on Lamia too; getting both errors at different login attempts 10105 and 90002

Got booted out and 9002 error trying to get back in. Says world is full over and over.

Same issue on Lamia got kicked, tried logging in, now in que get to loading screen and then kicked again with both the above errors mentioned. Was at excellent connection status and now at poor. Tried rebooting FF14 launcher etc...no go. Tried logging in to different character...no go.... if it does make it to load screen always get dc'd saying connection to server lost.

Same thing here on Diabolos. What's weird is that even changing Data Center is still showing poor connection

http://forum.square-enix.com/ffxiv/t...81#post3558681

Guess we just have to wait for them to fix it.

same on leviathan and got error 10105 when i tried to log back in

Yes, issue with Primal Server: http://forum.square-enix.com/ffxiv/t...81#post3558681

Funny, I'm on Goblin on Aether and I'm getting constant 20002 errors and am unable to log in.

What's worse, no idea of when it will be fixed :/

Same on Behemoth - have the Devs said anything yet about a server crash/reboot/anything??

Quote:

---

Originally Posted by Danotte

http://forum.square-enix.com/ffxiv/t...81#post3558681

Guess we just have to wait for them to fix it.

---

The put that up 10 - 15 minutes after the problem started. I WISH we had support at work that would be on top of a system problem that fast.

Quote:

---

Originally Posted by Chickychick_Jones

Same on Behemoth - have the Devs said anything yet about a server crash/reboot/anything??

---

Look up a few posts....

Quote:

---

Originally Posted by Danotte

Yes, issue with Primal Server: http://forum.square-enix.com/ffxiv/t...81#post3558681

---

New error window says "All worlds are currently undergoing maintenance. Please try logging in later." I am somewhat comforted as it looks like something on the server end and not mine/ours. And it appears they know about it since this is a new message.

Quote:

---

Originally Posted by A-Shock

What gives you any indication? Lol

---

well it wouldn't be a direct attack, it looks like a Main Frame, since theyre saying "software" issue that leads me to believe 1 of 2 things either:
A: someone screwed up the codeing (not likely)
B: someone got in and changed a few strings of code causing it to come down

also don't overwhelm the servers with trying to reconnect, it kills the server's processing power and will eventually cause it to fail, and will have to restart which takes about 4 hours for a medimum sized server, they'll probably look at the backups of the code right before the crash and determine what exactally happened

Quote:

---

Originally Posted by Scbass00

well it wouldn't be a direct attack, it looks like a Main Frame, since theyre saying "software" issue that leads me to believe 1 of 2 things either:
A: someone screwed up the codeing (not likely)
B: someone got in and changed a few strings of code causing it to come down

---

Nah, since it's not a direct attack most likely it's a program that froze or something of the like and they need to restart it... which may entail putting it into maintenance mode, shutting the processes down and reloading them. It's fairly standard and they really wouldn't have anyone going in and doing any code changes on a Saturday.

Quote:

---

Originally Posted by Malzian

Nah, since it's not a direct attack most likely it's a program that froze or something of the like and they need to restart it... which may entail putting it into maintenance mode, shutting the processes down and reloading them. It's fairly standard and they really wouldn't have anyone going in and doing any code changes on a Saturday.

---

I was implying an outside change to the code

Oh. I thought it was just me at first. But then I come in here and it's confirmed to be a Primal server problem overall. I was getting slammed by this while trying to enter Leviathan, and then after a bit, I started getting a message saying they just took down the servers.

Welp, to a different game then. :P

Quote:

---

Originally Posted by Scbass00

I was implying an outside change to the code

---

Possible but highly unlikely. Someone would have had to have broken into SE's system to do that and if you're the type of person to push into a system like that generally you're going to try and be silent about it and look to see if you can get to user account info. I really think it was just an internal process that locked up or something, it's the simplest and most plausible explanation that doesn't require something extraordinary to have happened.

Same on Bryn. Getting 10105 errors, looks like the instance server took a poop.

Quote:

---

Originally Posted by Malzian

Possible but highly unlikely. Someone would have had to have broken into SE's system to do that and if you're the type of person to push into a system like that generally you're going to try and be silent about it and look to see if you can get to user account info. I really think it was just an internal process that locked up or something, it's the simplest and most plausible explanation that doesn't require something extraordinary to have happened.

---

very true, youre most likely right, the connection servers probably just went down causing the mainfraim to try and reboot it to prevent data loss after doing a quick hotswap backup, and the main frame just decided to take it offline to avoid any detrimental effects, at first tho it was starting to look like a tap, but I think you do have a point. It does look like it was an issue with the smaller connection servers and not the SuperServers that run the software strings

I got booted when I completed a duty and was on the loading screen. I hope I don't have to complete the duty again...

Quote:

---

Originally Posted by Machaivelli

I got booted when I completed a duty and was on the loading screen. I hope I don't have to complete the duty again...

---

most likely will, servers didn't have time to back up your data most likely

SuperServer> SuperServer's MainFrame> MainFrame>Data Server> Back Up Server> another Data Server (main)> hundreds of Connection Servers> Your ISP Router> Your Device

issue is in one of the 2 main data servers either b4 or after backup

Quote:

---

Originally Posted by Scbass00

SuperServer> SuperServer's MainFrame> MainFrame>Data Server> Back Up Server> another Data Server (main)> hundreds of Connection Servers> Your ISP Router> Your Device

issue is in one of the 2 main data servers either b4 or after backup

---

Wow... um... where did you learn Network Architecture? Because no one uses the term MainFrame anymore and none of these systems are organized the way you're describing them. Most of the systems in a datacenter work in tandem. The way you put it there is a little bit outdated and there is no such thing as a 'SuperServer'. Mostly what you have now are several servers working in parallel distributing the data which is pulled from and written to a RAID storage system and you start your connection with a login server (which is probably what has crashed here) and are then shunted over to the actual instance servers. You do often have a backup server, but that never really gets activated unless something catastrophic happens to your RAID.