falkfyrebeard Posted April 6, 2022 Share Posted April 6, 2022 A bit at the end of my rope here. I keep getting kernal panic errors after 7-8 days of uptime. I've seen others have had this issue due to RAM timings but I don't use custom timings. I've been running 6.9.2 on my 1920x since it came out but this just started about 5 weeks ago out of the blue. I've done multiple days of memtests and deactivated a few plugins that FCP said were no longer supported. Does anyone have an suggestions on how to move forward? I think maybe it is network related. I install a 10Gb NIC about 4 months ago. I do have a custom "proxynet" for my docker containers per SpaceInvaderOne's videos. See Attached Diagnostics file 20220405.zip Quote Link to comment
Vr2Io Posted April 6, 2022 Share Posted April 6, 2022 (edited) Try save syslog to flash or setup remote syslog server and redirect the dmesg to display for monitoring, at local console type setterm -blank 0 dmesg -Tw --level=err,warn >> /dev/tty0 & Edited April 6, 2022 by Vr2Io Quote Link to comment
falkfyrebeard Posted April 6, 2022 Author Share Posted April 6, 2022 (edited) 11 hours ago, Vr2Io said: Try save syslog to flash or setup remote syslog server and redirect the dmesg to display for monitoring, at local console type setterm -blank 0 dmesg -Tw --level=err,warn >> /dev/tty0 & Got it set up logging to my other UnRaid server. Never know when it will act up again. Seen 2 days seen 13. Thanks for your help. I'll update when I have more information. Edited April 6, 2022 by IMITLLC Updated Quote Link to comment
falkfyrebeard Posted April 18, 2022 Author Share Posted April 18, 2022 On 4/5/2022 at 8:36 PM, Vr2Io said: Try save syslog to flash or setup remote syslog server and redirect the dmesg to display for monitoring, at local console type setterm -blank 0 dmesg -Tw --level=err,warn >> /dev/tty0 & Finally got it to act up and get a capture. Looking at it I still can't figure out the issue at this point. syslog attached syslog-192.168.11.4.log Quote Link to comment
JorgeB Posted April 19, 2022 Share Posted April 19, 2022 See if this applies to you, if yes, upgrading to v6.10 and switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/ Quote Link to comment
falkfyrebeard Posted April 19, 2022 Author Share Posted April 19, 2022 4 hours ago, JorgeB said: See if this applies to you, if yes, upgrading to v6.10 and switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/ Thanks. I'll give it a shot. I do run two Pi-Holes on it with static ips. I was leery of going to 6.10 on it due to beta and so many containers running but my virtualization server has been doing fine on it. 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.