On Tuesday 07 May 2002 11:03 am, Ben Parker wrote:
> Hey everybody - I wanted to throw in my 2 cents on this issue because
> even with all the responses still no one had said this yet.
> I use a variation of the cron monitoring system: I have a separate
> machine (or could feasibly be the Webware server) hit a protected
> HTTP page served by Webware which dumps stats from the box. I hit
> the page every 2 minutes, but some of the stats are refreshed every
> 10-20 minutes to conserve server resources. If anything goes wrong,
> I get emailed/paged, but I do NOT restart Webware automatically.
> The reason for this is that a crashed live AppServer should never
> happen, so when it does it usually means there is some seriously
> wrong code running, or something malicious going on, and I would
> rather identify the problem, restart manually, than restart in a
> chaotic situation. I just don't like running anything that could
> possibly mask a fatal error.
I do the same thing for StockAlerts.com. I made sure the monitoring
system was external to our network. One time the firewall was
misconfigured but our monitor was on our own network and therefore,
There is more than one reason users might not be able to reach your
site, so a URL fetch from a remote machine is always a good idea.