OK, looks like my guess (sincere hope) was right, the server is back up after about 11 minutes and has not been rebooted. In any case, it would be nice to know for future reference what our options (and expenses) would be if in fact we continue to have trouble. At less than 4 days of uptime since the fatal weekend it's too soon to completely breathe easy.

Ken

P.S. I've setup secondary dns services with zoneedit.com and have contacted those in control of squeak.org and squeakland.org registrations to add them as additional dns secondaries. This won't 'fix' us, but will help when the server is down in the future to keep some services up and even perhaps redirect to another server if it looks like downtime is going to be extended. This was a suggestion from Goran, for the record.

On Sat, 2008-10-25 at 18:35 -0500, Ken Causey wrote:

On the assumption that this is the result of the server locking up again and not a local network issue (which a traceroute suggests to me it might be):

What would it cost us to have the remote console system connected to our server for a couple of weeks to a month cost us? At this point it seems like this is going to be required to track down the cause.

Ken

On Sun, 2008-10-26 at 01:30 +0200, noreply@hetzner.de wrote:

...

Notification for 85.10.195.197:

==> PING <== State is now: ERROR (01:30h 2008.10.26) State before: OK (was 3 days) Service params: Service uptime: 95.66% Check output:

...

PING 85.10.195.197 (85.10.195.197) 56(84) bytes of data. --- 85.10.195.197 ping statistics --- 20 packets transmitted, 0 received, 100% packet loss, time 9539 ms

In case of any question regarding the Hetzner Server Monitoring, please do not reply to this email address - use support@hetzner.de instead.