90002 Error Booting Players from Ultros

[Malzian]

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.

[Scbass00]

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

[TruebladeNuke]

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

[Malzian]

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.

[RaineAmorie]

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

[Scbass00]

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

[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...

[Scbass00]

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

[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

[Malzian]

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.