KD-DSO Posted November 20 Share Posted November 20 I've been dealing with kernel panics and freezes over the last several weeks. Syslogs have not proven helpful. "Fix Common Problems" plugin has not show errors. Everything is updated. Disabling various Docker containers is proving unhelpful. Looking for any suggestions or help. Quote Link to comment
JorgeB Posted November 20 Share Posted November 20 Enable the syslog server and post that after a crash together with fresh diags. Quote Link to comment
KD-DSO Posted November 20 Author Share Posted November 20 Syslog attached. This is from today after another kernel panic. No idea why the timestamp is so far off. syslog Quote Link to comment
KD-DSO Posted Wednesday at 03:10 PM Author Share Posted Wednesday at 03:10 PM (edited) Exactly. I do not understand what is happening. The only real indication of panic I get is displayed on my monitor. Edited Wednesday at 03:11 PM by KD-DSO Quote Link to comment
JorgeB Posted Wednesday at 03:18 PM Share Posted Wednesday at 03:18 PM They should also be logged, was that the persistent syslog form the syslog server you posted? Doesn't look like it, normal syslog starts over after every boot. Quote Link to comment
KD-DSO Posted Thursday at 03:44 AM Author Share Posted Thursday at 03:44 AM That's the Syslog I pulled from /boot/logs. Should I be looking elsewhere? Quote Link to comment
JorgeB Posted Thursday at 11:13 AM Share Posted Thursday at 11:13 AM 7 hours ago, KD-DSO said: Should I be looking elsewhere? Did you activate the mirror to flash drive option in the syslog server? Quote Link to comment
KD-DSO Posted Friday at 01:49 AM Author Share Posted Friday at 01:49 AM (edited) I did last week, yes. System crashed again. Same messages on monitor as shown above. Syslog did not update. Want to confirm the syslog should be writing to /boot/logs/syslog when mirror to flash is enabled? I am going to try ingesting it into an external splunk server as well. Edited Friday at 02:10 AM by KD-DSO Quote Link to comment
KD-DSO Posted Friday at 02:27 AM Author Share Posted Friday at 02:27 AM Seemed I had a seperate logging issue not helping anything. Deleted all rsyslog.* files in /boot/config/ and the log file at /boot/log/syslog. After reboot I now have logs in /boot, through the GUI and at Splunk. Hopefully that helps in troubleshooting the main issue. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.