Alan McKinnon <[email protected]> writes: > Remote logging and just leave it till the machine freezes again will > hopefully give you the useful logs you need to identify the > problem. To save disk space you can configure logrotate on the > remote logger to delete the previous days stuff - you don't need > logs from days where the box was working fine.
Thanks, that may be worth a try... I wonder if with rsyslog (my logger of choice) it may be possible to log to localhost as well as remote? I think I'll look into that too. > Another option is to look at the pattern here: one day out of the > blue a stable system developed problems and they still surface at > random times. This is one of the characteristics of failing > hardware. Have you done a full thorough hardware test, including > such things as memtest and smart? I agree that it sounds like hardware but even then some log tracks should appear right? (Maybe I'll see them with the remote logging suggestion) > . . . . . . . . . . . . . . . . . . . . . .Have you done a full > thorough hardware test Haven't done the memtest or smart But far as `full'; what other tests might I try? ps - I did find some reiserfs errors and currently running reiserfsck --rebuild-tree On that (now umounted) disk after a full backup, so maybe that is related and will cure the problem (fingers crossed hard)
