the problem happens on MediaTemple's side. there's a misbehaving firewall at their end.
due to the nature of this issue (being a misbehaving firewall), it's not going to show up in our traditional monitoring metrics because, technically speaking, the server was functioning just fine during this time period. However, there was a marked decrease in traffic from about 4.30am PST until my first response to you. I also noted that the "uptime" on the host server was about 110 minutes when it was fixed, which would probably correlate to whenever the firewall error occurred (or at least took effect, after a reboot.) So I would imagine 110 minutes to be a good estimate regarding the length of time your database experienced latency. However, since the (gs) Grid-Service is set up to have many nodes connecting to each host server, it's possible many nodes were down for a much shorter period of time.
This firewall resides in our own datacenter, here in Los Angeles. It is an internal, (mt) Media Temple-controlled firewall, and we had to physically reset its configurations to bring it back to normal function. There isn't anything you can do to prevent this in the future, because this was a one-time problem within our own network. We apologize for the inconvenience,
This firewall resides in our own datacenter, here in Los Angeles. It is an internal, (mt) Media Temple-controlled firewall, and we had to physically reset its configurations to bring it back to normal function. There isn't anything you can do to prevent this in the future, because this was a one-time problem within our own network. We apologize for the inconvenience,
Leave a comment: