On 09/11/2015 10:31 AM, Mike Kershaw wrote: > On Thu, Sep 10, 2015 at 02:08:07PM -0400, James E. LaBarre wrote: >> I have a system that has decided it wants to do spontaneous shutdowns. At >> first I had seen it was shutting down while I was booting it up (can't tell >> at which point it failed then, since it's on a KVM and I had it switched to >> the other machine while it booted). Afterwards I was able to get it to boot >> all the way into the Mate desktop, and used it for about 10 minutes one >> time, about 30 min the next. One time I actually got a popup asking whether >> I wanted to do a reboot, suspend, or shutdown, but it then just shut off >> before I could even respond. Afterwards it just shuts down without any >> warning. >> >> I'd like to set up some sort of monitoring/logging on it to see if I could >> catch what fails, since I couldn't see anything obvious in the logs in >> /var/log. >> >> I'd think it might be a temperature failure, so I expect I'd need to run >> some thermal monitoring. > > I'd agree - thermal panic, power supply problem, or dodgy ram seem > good guesses. > > You probably need to get console on a serial port:
Agree; good thought > http://www.electronicsfaq.com/2013/04/redirecting-kernel-messages-dmesg-out.html Assuming the system runs systemd, setting up a console port likely has to be done a little differently. https://wiki.freedesktop.org/www/Software/systemd/Debugging/ https://wiki.archlinux.org/index.php/Working_with_the_serial_console > because you may not be booted enough for logging. > > It's also possible you may be able to use some platform-specific > diagnostic tools to pull previous error codes. > > -m -- Chris -- Chris Knadle [email protected] _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org https://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) Vassar College * Oct 7 - Understanding Systemd Nov 4 - Imposter Syndrome Dec 2 - Distributed Filesystems And Ceph
