Dkr Posted September 28, 2021 Share Posted September 28, 2021 hi dos anyone have any idea why i got this, it isn't the first time the server is crashed with a kernel panic my server: os: 6.9.2 mb: Supermicro A2SDi-8C-HLN4F Version 1.00 ram: 64 GiB DDR4 Single-bit ECC and a few containers crashplan plex node-red Jirafeau unifi controler i hope someone can help /DKR Quote Link to comment
Dkr Posted September 30, 2021 Author Share Posted September 30, 2021 Hi again, it just happened again, this time without docker running /DKR Quote Link to comment
JorgeB Posted September 30, 2021 Share Posted September 30, 2021 Enable syslog server and post that log after a crash together with the diagnostics. Quote Link to comment
Dkr Posted October 25, 2021 Author Share Posted October 25, 2021 (edited) i got this from syslog how can i get dianostic when the server is crashed? [code removed] /DKR Edited October 26, 2021 by Dkr Quote Link to comment
JorgeB Posted October 25, 2021 Share Posted October 25, 2021 Please post the complete syslog, you can get the diags after rebooting, in this case it's mostly to see the hardware in use. Quote Link to comment
Dkr Posted October 25, 2021 Author Share Posted October 25, 2021 I used my second server as a syslog server and copied the whole log. should i just use the normal tool -> diagnostics? /DKR Quote Link to comment
JorgeB Posted October 25, 2021 Share Posted October 25, 2021 Meant attach the file here, instead of copy/past, diags are the normal diagnostics. Quote Link to comment
Dkr Posted October 26, 2021 Author Share Posted October 26, 2021 hi A fresh crash (server1) with syslog (server2) and diag /DKR server-2-syslog-192.168.124.130-20211026-2043.zip server1-diagnostics-20211026-2316.zip Quote Link to comment
JorgeB Posted October 27, 2021 Share Posted October 27, 2021 Those call traces are usually the result of having dockers with a custom IP address, 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
Dkr Posted October 29, 2021 Author Share Posted October 29, 2021 hi it fix it THANKS /DKR 1 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.