The 02.10.18 at 17:44, Gregory Sawyer wrote:
Incidently, hitting my old ISP's site from Mac OS X will consistantly bring the SuSE box down. Every time. I can hit other sites just fine, but the ISP's site apparently is doom. Further, I can hit the ISP from my SuSE box without any ill effect, it only happens when I hit it from Mac OS X.
Try to do it while the suse is displaying console-10, you know, the one with error logs. It might be able to report something there. Also, have a look at /var/log/firewall - it is the file kernel messages go to, but it could show nothing, depending on how bad is the crash.
As to the dissapearing disk, I don't know :-?
Thanks Carlos, for the suggestion - I'll try the console-10 lurk later. I did peek at the logs last night but couldn't find anything -- apparently the loggers weren't able to flush to disk.
But I did just grep through /var/log/firewall, and I discovered that the ZIP drive was throwing nasty parity errors every morning at around 00:15, which is coincident with a cron script that I know runs at that time. That would be also about the same time this morning that my ex-ISP's site first crashed the machine.
Too many write errors could bring the system down, it happened to me. It tries to write something, but it can't; if the problem is the root (/) it fails again when trying to log that... and anyways, the system is too busy trying to cope: it seems to be unable to do anything else.
These started on the morning of the 16th -- on the 15th I compiled and installed the latest release of CUPS along with the CUPS folk's version of GhostScript -- and CUPS has taken the system down a couple of times as well in a similar manner. Just one more thing to convolute this insanity.
:-( -- Cheers, Carlos Robinson