- Joined
- Aug 23, 2009
- Messages
- 21,870
- Reaction score
- 39,615
All,
There was a network outage last night (5/21) in the area of 8PM to 9PM JST but we have yet to get an explanation of what occurred. Both physical machines that power TAG were knocked off the public internet and became unreachable for about 30min based on what we could tell.
Our hands-on technician for whatever reason decided a forced reboot (one server but not the other) was in order, which caused a number of problems with synchronization... This was repaired by myself and everything seems to be back to normal now. The second server is still showing an uptime of 480 days, so it was definitely not power-cycled for a forced reboot.
Since the technician on-site did not follow our instructions (which did not include a reboot), we have filed a complaint about the activity to try and prevent this from occurring again.
Anyone that could not browse the site during our prime traffic hours, we are sorry for the outage.
Thank you for your understanding.
(to be honest, I don't know why ANY qualified tech thinks a hard reboot is a sane maneuver when a request says NOTHING about a reboot... the request specifically dealt with packet loss and network connectivity issues.)
There was a network outage last night (5/21) in the area of 8PM to 9PM JST but we have yet to get an explanation of what occurred. Both physical machines that power TAG were knocked off the public internet and became unreachable for about 30min based on what we could tell.
Our hands-on technician for whatever reason decided a forced reboot (one server but not the other) was in order, which caused a number of problems with synchronization... This was repaired by myself and everything seems to be back to normal now. The second server is still showing an uptime of 480 days, so it was definitely not power-cycled for a forced reboot.
Since the technician on-site did not follow our instructions (which did not include a reboot), we have filed a complaint about the activity to try and prevent this from occurring again.
Anyone that could not browse the site during our prime traffic hours, we are sorry for the outage.
Thank you for your understanding.
(to be honest, I don't know why ANY qualified tech thinks a hard reboot is a sane maneuver when a request says NOTHING about a reboot... the request specifically dealt with packet loss and network connectivity issues.)