My Fedora 8 system (x86_64, kernel 2.6.23.9-85) started to spontaneously reboot this week. From what I've read, it's most likely a motherboard or power supply failure. Is there anything I can do with Fedora to help troubleshoot this?
<br><br>/var/log/messages doesn't seem to tell me anything useful. The last reboot came around 9:20. <br><br>Jan 6 08:50:44 MainPC yum: Updated: mythtv-setup - 0.20.2-170.fc8.x86_64<br>Jan 6 08:55:37 MainPC ntpd[2154]: synchronized to
<a href="http://216.14.98.234">216.14.98.234</a>, stratum 2<br>Jan 6 09:20:23 MainPC rsyslogd: [origin software="rsyslogd" swVersion="1.19.11" x-pid="2015"][x-configInfo udpReception="No" udpPort="514" tcpReception="No" tcpPort="0"] restart
<br>Jan 6 09:20:23 MainPC kernel: rklogd 1.19.11, log source = /proc/kmsg started.<br><br>Is there anything I can do to enable more logging of this issue? Here's my rsyslog.conf:<br><br># Log all kernel messages to the console.
<br># Logging much else clutters up the screen.<br>#kern.* /dev/console<br><br># Log anything (except mail) of level info or higher.<br># Don't log private authentication messages!
<br>*.info;mail.none;authpriv.none;cron.none /var/log/messages<br><br># The authpriv file has restricted access.<br>authpriv.* /var/log/secure<br><br># Log all the mail messages in one place.
<br>mail.* -/var/log/maillog<br><br><br># Log cron stuff<br>cron.* /var/log/cron<br><br># Everybody gets emergency messages
<br>*.emerg *<br><br># Save news errors of level crit and higher in a special file.<br>uucp,news.crit /var/log/spooler<br><br># Save boot messages also to
boot.log<br>local7.* /var/log/boot.log<br><br><br>