Quote:
Originally Posted by raymor
I would yell at you too. The thing is, it's not a case of "oh apache is down maybe we
should restart that service". Rather it's a case of "Apache isn't responding within a
reasonable time, let's find out WHY so we can fix the actual problem." By restarting
it you made it a hundred times harder to find the problem as you're now asking them
to figure out what the problem WAS rather than what the problem IS. You should have
called them. Imagine a friend asks you to help with their web site. They email you
saying "the page didn't look right, so I deleted it - what was wrong with it?". It's
somewhat similar - you need to SEE the problem in order to diagnose it and fix it.
(Though sometimes a diagnosis can be made from log files.)
|
Ray is totally right here on all points.
Outside of all that, it IS asking a lot for a host to monitor your server if it truly does fall in the un-managed category. Here's why - simply put that does not work in scale with hundreds or thousands of servers. First, it has a monitoring system paging techs all the time when it's not supposed to be. If a server is truly unmanaged, there is no proper response from the host. You may have screwed the server up, rebooted it yourself, turned off a service intentionally.... you don't want a host rebooting something that you just rebooted. Case in point, managed should be managed and done by a clear set of standards and practices. Un-managed is just that, it's a server that's priced like an auto rental: it's your job to drive yourself.
Brad