Re: How to figure out why a computer rebooted?
> Obviously if I get home and the digital clocks are flashing, I'll know
> there was a brief power cut. But is there any way to determine from
> the computer's own evidence why it restarted?
Look at this part of your second log, where you shut it down yourself:
> Nov 12 12:58:19 argon gdm: Master halting...
> Nov 12 12:58:19 argon shutdown: shutting down for system halt
> Nov 12 12:58:19 argon init: Switching to runlevel: 0
> Nov 12 12:58:24 argon xfs: terminating
> Nov 12 12:58:25 argon xfs: terminating
> Nov 12 12:58:27 argon chronyd: chronyd exiting on signal
> Nov 12 12:58:27 argon rpc.statd: Caught signal 15, un-registering and exiting.
> Nov 12 12:58:27 argon exiting on signal 15
This is stuff put out by various processes as you go to run level 0
(shutdown), stuff *not* present in the log snippet you gave from
the other machine. So it didn't go down through a normal system
procedure -- it died abruptly, and then rebooted. Typically, as
you note, this is because of a power issue (and depending on whether
your machine has e.g. a good UPS with a conditioner, etc, it need
not be a failure; I've had bad power quality briefly where the
digital clocks in the room didn't go to flashing 12, but the
computer power supply allowed the motherboard power to drop enough
for the motherboard to quit, then reboot shortly after). I've
also seen other times when this has happened because of hardware
problems. I've never seen it because of an OS or other software
issue -- for that, I'm more likely to get hard lockups or, I
guess, PANICs -- but maybe someone will chime in with a counter-
example. But whatever the source, it died instantaneously, and
in such circumstances the system doesn't get much of an
opportunity to say "I'm going down because of X". So the only
suggestion I'd have would be to look at the logs for any sign
of growing hardware issues, which could be located (in the logs)
nowhere near the actual shutdown. And check what you're doing
about your power quality.