MediaTemple (gs) service at fault: 500 error or too slow DB connection
I'd like to know whether MediaTemple staff attends to this forum.
Approximately a day ago the (gs) (GridServer) service started to fail, in two ways:
- too long MySQL connections, they often break prior to SQL queries are finished
- 500 Internal Server Error is returned after a long timeout
SSH service works fine. Web and DB services operate poorly.
No response is posted to users forums to the threads about this, no email announces/whatever about this situation.
I would be very glad to know whether the Support is aware of the failures and whether anything is being done to fix it. The service was next to excellent a day ago. Now I am losing visitors and customers seeing 500 ISE for hours. Sites loading for 10-15 seconds aren't a good sight as well (they loaded for approx. a second a day ago).
Migrating or staying it your choice, But what I am telling you is that, its not a new problem. users face this and mediatemple guys know it. even wikipedia says same thing
Originally Posted by Wikipedia
Media Temple's primary business is website hosting for more than 200,000 websites from 40 countries on Grid-Service. Its grid hosting system uses a network of servers that work together as a team. Unlike traditional shared hosting, grid hosting can cope well with spikes in traffic as it can assign more servers to help carry the load. The service was launched on October 17, 2006.
Grid-Service shared hosting has come under criticism for service outages. Intermittent service availability has been a frequent problem. In one case, periodical downtime occurred between April 29, 2008 and May 28, 2008, until engineers made substantial changes to the system's storage architecture.
Grid-Service is scheduled to be replaced by a Cluster-Server in 2009. The new storage system is being designed to eliminate the main source of service instability that Grid-Service suffered from.