daemian Posted May 17 Share Posted May 17 (edited) Good Afternoon, Have an Unraid install that has been going strong for many many years. Have run into issues a few times here and there, but typically its been related to a specific docker (most recently it was Frigate). It has been solid for 9 months or so, until this past Sunday night when it crashed without warning. I brought it back up, and its been crashing ever since. I had to re-add all of my dockers (the page ended up empty), which i never completely finished as its continued to have issues. I tried not running Frigate as that was the culprit in the past, but its still crashing. I also tried safemode, and it also crashed. I ram a memory test, and it passed. I was on 6.12.6 and at one point in this process decided to upgrade to 6.12.10.s Same issue with both Here is the diagnostics and last 2 syslog files (both from crashes). Any ideas what might be going on? Thanks in Advanced! syslog syslog-previous ur01.marx.local-diagnostics-20240517-1543.zip Edited May 17 by daemian Quote Link to comment
JorgeB Posted May 18 Share Posted May 18 May 17 15:32:38 ur01 kernel: macvlan_broadcast+0x10a/0x150 [macvlan] May 17 15:32:38 ur01 kernel: ? _raw_spin_unlock+0x14/0x29 May 17 15:32:38 ur01 kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot. Quote Link to comment
daemian Posted May 19 Author Share Posted May 19 Thanks JorgeB, I made the chagne to ipvlan, saved, rebooted and started the array. A few hours it crashed again the same as before. I verified it its still set to ipvlan after bringing it back up. another syslog and diagnostics is attached. Thank you for your help! ur01.marx.local-diagnostics-20240518-2259.zip syslog Quote Link to comment
JorgeB Posted May 19 Share Posted May 19 It's still showing macvlan call traces, post the output of docker network ls Quote Link to comment
daemian Posted May 20 Author Share Posted May 20 root@ur01:~# docker network ls NETWORK ID NAME DRIVER SCOPE 26b57be4530c br0 macvlan local 202e09e3a3ce bridge bridge local a30031a6206f host host local 91776a234133 none null local It does seems to still be using macvlan for br0. For reference, here is my settings page: Quote Link to comment
Solution JorgeB Posted May 20 Solution Share Posted May 20 Try recreating the docker image, then check to see if macvlan is still being used: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks Quote Link to comment
daemian Posted May 20 Author Share Posted May 20 Thanks JorgeB, I followed the process to delete the docker image and recreate it, i am now seeing ipvlan in the output. This are now running again, ill report back as time goes by and we see if its stable or the problem persists. root@ur01:~# docker network ls NETWORK ID NAME DRIVER SCOPE ac212ad490b6 br0 ipvlan local 86ec9a039786 bridge bridge local db1ff75c54d7 host host local fbfefb6d9d64 none null local Thanks! 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.