Hi, ok, will check the logs,
however it is doubtful that they will contain any
clues of a system that just stops responding.
But there is some sstate (?) or someting
in linux I think that can be used to check system calls (?
typically)
and if those can be saved over the boot and if
there is any way to find the last entries before the halt and
reboot.....
And possilby find what activity was initiated, if
from Apache, or general system services that made the hickup.
As to backup, yes, there is no very loss-sensitive
info on the disk. And yes, if you imply with "interresting,,," that
there could be problems by just moving a disk with
configuration between computers, yes, that is relevant.
And yes, the problem might arise from that, however
why would it run such long time before stalling. Well there could
be some "safekeeping" activity that is
scheduled with long period, that tries to reach some of the Hw that has
become
missconfigured from the
possible difference/missmatch in memory/addresses that might come from just
plugging
a configured system into another Hw. But still I
would like to find cause and find remedy. There is a bit of
configuration
work done in setting up the server, which
would be nice not having to repeat (lazy ? :)
georgp
|