redspecter23 wrote: »
A highly trained goose. It turns out that even the fastest goose in the world can only travel so fast so 3 hours later, Bob had his cheese, ZOS had the button and we were back in the game!
Ceejengine wrote: »Coding is complex. Sometimes you need extra time to make sure whatever you're fixing is actually fixed.
ThoughtRaven wrote: »Ceejengine wrote: »Coding is complex. Sometimes you need extra time to make sure whatever you're fixing is actually fixed.
Haha. Yeah let me tell you how much faith I have that anything ZoS did actually "fixed" anything.
redspecter23 wrote: »It was a two step process. Turn it off and on again.
Step 1: Turn the servers off. This part went over flawlessly. Bob was successfully able to find the off switch and toggle it to the off position, effectively shutting off the servers.
Step 2: Turn it back on. Bob, being the evil genius that he is, removed the on/off button once he had turned it off and held it ransom. Without the button, nobody at ZOS was able to turn it back on. Once they identified this issue, they wanted to let us know right away so they extended the downtime. Then came time to meet Bob's demands. He insisted on a fancy wedge of cheese imported directly from Saskatchewan. ZOS with all the power of Microsoft backing them, arranged transport of the wedge via the fastest method possible. A highly trained goose. It turns out that even the fastest goose in the world can only travel so fast so 3 hours later, Bob had his cheese, ZOS had the button and we were back in the game!
PigofSteel wrote: »I think they need to really really really upgrade that hardware...
StabbityDoom wrote: »Are we going to be told what happened to cause the extra outage? Or what was changed in the maintenance, if anything?
redspecter23 wrote: »It was a two step process. Turn it off and on again.
Step 1: Turn the servers off. This part went over flawlessly. Bob was successfully able to find the off switch and toggle it to the off position, effectively shutting off the servers.
Step 2: Turn it back on. Bob, being the evil genius that he is, removed the on/off button once he had turned it off and held it ransom. Without the button, nobody at ZOS was able to turn it back on. Once they identified this issue, they wanted to let us know right away so they extended the downtime. Then came time to meet Bob's demands. He insisted on a fancy wedge of cheese imported directly from Saskatchewan. ZOS with all the power of Microsoft backing them, arranged transport of the wedge via the fastest method possible. A highly trained goose. It turns out that even the fastest goose in the world can only travel so fast so 3 hours later, Bob had his cheese, ZOS had the button and we were back in the game!
ArchangelIsraphel wrote: »
I'm pretty sure Bob also drops cheese into the server occasionally causing lag and other unfortunate issues. That, or he shuts the fans off and makes a grilled cheese on top of them.
trackdemon5512 wrote: »It was maintenance. Downtime is an estimate but doesn’t always ascribe to a set schedule. [snip]
[Edit for Baiting.]
Goregrinder wrote: »trackdemon5512 wrote: »It was maintenance. Downtime is an estimate but doesn’t always ascribe to a set schedule. [snip]
[Edit for Baiting.]
You are a smart one my friend. From all of us that work in IT or with SQL databases or any related field, we appreciate you for understanding this most basic concept. I can tell you probably encounter very few layer-8 issues in your life, so kudos!