Nothing. The logs simply stop when the machine does and are no longer written
even though the kernel is operable enough to respond to pings and initiate
TCP sessions.
My experience is that this is related to running out of memory, and have replicated it several times on boxes with limited memory. To test I had two ssh sessions open running `watch uptime` and `watch free`, and then hammered the box -- the load shot up and free memory was rapidly shrinking toward 0 and then the box froze.
I would have to agree, check out memory usage. I had the same exact thing happening to a server of mine. The cause was the server running out of memory. I had accidentally removed the swap partition out of fstab...
The only other time I had something like that happen was when one of my co-workers was pinging the complete 172.16.0.0/12 network.
) ...including the broadcast addresses. :^( Most of the machines had dual nics in the same physical network, and they were getting a huge arp request flood.
The arp tables filled up and that was that, no log entries or nothing.
The machines would seem to crash.
I believe that the current kernels handle that better now, but hey who knows for sure.
You mentioned that your switch is a ProCurve.
Which model is it? We use the 5300 series, and they log problems on the ports when the switch notices them.
Check out the switch logs, sometimes it can really help.
Regards, Scott
-- [email protected] mailing list
