OddOod Posted May 24, 2022 Share Posted May 24, 2022 Every 2-12 days my unraid server crashes out. No warning, one moment everything is fine and the next it's totally non-responsive. No SSH, no gui, no video out, nothing. The infuriating thing is that I then cannot get a log. I have rlog set up, but nothing seems to be majorly amiss there and I'm not sure if it's safe to post a full rlog dump. I'm kind of at loose ends. Quote Link to comment
trurl Posted May 24, 2022 Share Posted May 24, 2022 attach diagnostics to your NEXT post in this thread 1 Quote Link to comment
OddOod Posted May 24, 2022 Author Share Posted May 24, 2022 Happily, does that help post reboot? shirt-diagnostics-20220523-2136.zip Quote Link to comment
JorgeB Posted May 24, 2022 Share Posted May 24, 2022 5 hours ago, OddOod said: does that help post reboot? It allows us to see the hardware used and sometimes there are some known issues, in your case start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173 1 Quote Link to comment
OddOod Posted May 24, 2022 Author Share Posted May 24, 2022 Thanks for holding my hand. If this doesn't work should I respond here or should I open a new thread? Quote Link to comment
trurl Posted May 24, 2022 Share Posted May 24, 2022 8 minutes ago, OddOod said: respond here 1 Quote Link to comment
JorgeB Posted May 24, 2022 Share Posted May 24, 2022 Also, if that doesn't help enable the syslog server and post that after a crash. 1 Quote Link to comment
OddOod Posted June 3, 2022 Author Share Posted June 3, 2022 I had another crash. I The docker.log file is over 60 gigs so I included the last 10000 lines of itcrash20220603.7z Quote Link to comment
JorgeB Posted June 3, 2022 Share Posted June 3, 2022 2022-06-01T19:11:33-05:00 shirt kernel: macvlan_broadcast+0x116/0x144 [macvlan] 2022-06-01T19:11:33-05:00 shirt kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 and switching to ipvlan should 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/ 2 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.