Bluehost my favorite dysfunctional web hosting company strikes again. Abssorb and Tvuolo were patiently biting nails, waiting for 28 hours, while the technical staff fiddled with box329 attempting to make their server operational. After 28 frustrating hours box329 was briefly up just to tease the clients with the fact that they will have harmful amounts of data loss before the server went down again.
In the same post Abssorb quotes one of Matt Heaton’s blogs Reliability, reliability, relibility…
3 – Proactive administration vs reactive administration – Sometimes we find ourselves in the reactive mode. Fix it when their is a problem. This isn’t right. We have set concrete plans in place that will make it so that each time a server goes down we have the information to know exactly what caused it and how to fix it so next time the same thing doesn’t happen. Many large hosts get caught up in the “reset the server” mode, and don’t really fix the problem for the long term. We will strive to fix it for the long term.
Abssorb follows with the comment, “Looks like that ‘Concrete’ had some crap in it, cos it hasn’t set.”
Folks we have all heard the “How many engineers does it take to change a light bulb joke?” Well how many Sys Admins does it take to fix box329 at Bluehost? Perhaps Bluehost should consider farming out this type of work to one of their competitors whom are a bit more competent than their in house “Technical Department”.
I am beginning to think a Linux virus does exist and it is called a Bluehost system administrator.
Hey Matt Heaton, Bluehost is “unreliable, unreliable, unreliable…”