On Wednesday 25 April 2007 17:51, James D. Parra wrote: > ... > >> Some piece of hardware or kernel software could be in a corrupt, >> inconsistent or otherwise erroneous state. >> >> You could just reboot the server in question and chalk it up to >> cosmic rays. If it happens again soon (or immediately), then start >> trying to diagnose the fault. Otherwise, fuhgetaboutit... > > ~~~~~ > > Ouch! Well, a reboot did occur and that didn't resolve the problem > and without anything obvious in the logs I can't, at this moment, > diagnose the fault. This is an important server & I can't just forget > about it.
The problem could lie within a router or switch. They have complex internal state that can become messed up, too. Reboot everthing in sight... > ~James Could you, by any chance, send your mail with the usual quoting conventions? It's tedious to have to fix it by hand. RRS -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
