ZiNgA BuRgA Wrote:How long was it for?
Logs are showing me this:

Quote:Oct  6 16:43:07 zingaburga kernel: eth0: link down.
Oct  6 16:43:09 zingaburga kernel: eth0: link up.
Oct  6 16:43:15 zingaburga kernel: eth0: link down.
Oct  6 16:43:16 zingaburga kernel: eth0: link up.
Oct  6 16:43:34 zingaburga kernel: eth0: link down.
Oct  6 16:43:36 zingaburga kernel: eth0: link up.
Oct  6 16:43:51 zingaburga kernel: eth0: link down.
Oct  6 16:43:56 zingaburga kernel: eth0: link up.
Oct  6 16:45:55 zingaburga kernel: eth0: link down.
Oct  6 16:55:08 zingaburga shutdown[1521]: shutting down for system halt
Oct  6 16:55:24 zingaburga exiting on signal 15
Oct  6 19:37:53 zingaburga syslogd 1.4.1: restart.

I'm guessing the restart occurred because the host's connection was screwy (have a script which tries to reboot if there's no network connection).  What I don't get was why it took 2:42 to reboot... (anyone know more about Linux here? perhaps some logging quirk? unless the host decided to shut the system down, lol)
Web server logs show connections at 16:43:05 and 19:38:22, so should be fairly indicative of when people weren't able to access stuff.

I recall checking uptime about a week ago, and was up for like 87 days.  Weird quirk I guess >_>