Another Friday Server Meltdown?

[rockygreen11]

Oh I see, Jxsin is also funny man now too... Lol. You are all actually cool in my book... We love the same game!

[GiantInMaine]

Trion should be paying me for all the info I relate back to the community BTW Trion, I am looking for work *hint hint*

If you worked for them you wouldn't have the time to relate stuff back to the community though. You'd be too busy getting the servers running

[Iceberg]

If you worked for them you wouldn't have the time to relate stuff back to the community though. You'd be too busy getting the servers running

Which translates to running to the local pet store for hamsters.

[rockygreen11]

I'm in! Yes... The food is going to be epic!!! Lol.

[JxSiN]

If you worked for them you wouldn't have the time to relate stuff back to the community though. You'd be too busy getting the servers running

I've had my share of fixing electronics in the military. I'll stick to my main skillset which is gathering, deciphering, and reporting information back to the people who need it. It would be great to actually be able to do that in English. If I have to hear or read anymore Arabic than I have to now that I am a civilian, I will go crazy

[Thomas1975]

Last week they had to replace a blade on the server. Not sure if it is the same problem this week

Blade Servers are designed to stay running if one blade goes out, so this does not account for everyone being booted this week or last. sorry another spin job!

[JxSiN]

Blade Servers are designed to stay running if one blade goes out, so this does not account for everyone being booted this week or last. sorry another spin job!

Dude, Blade was the hamster. He will be missed. Have some condolences.

[Shtakotaco]

http://publib.boulder.ibm.com/infoce..._problems.html

Here I found something for you Trion now fix the server.

[JxSiN]

Honestly, often times the issue is so technical that trying to communicate what happened would be at great risk of misrepresenting the issue!

For this particular issue, swapping server blades was required, which is the reason it took a bit longer than we would have liked. At first, it seemed like a simple reboot would solve the problem. When that didn't help, we had to call in a larger team to take a look. Anyone that knows about server engineering knows that doing an entire blade swap is not something you want to do before you've ruled out the simpler options! So once we did that, the ops guys swapped the blades and all was well.

Here is the quote for what happened last weekend.

[dahanese]

We are back up and running - confirmed by the team! Thanks guys.