Urbanpixels Posted February 4, 2020 Share Posted February 4, 2020 (edited) Hi Guys, Im new to unraid so please forgive any things which maybe obvious. Im having issues assigning a separate IP (same subnet as the server) to a docker container using br0 When docker containers use HOST everything is peachy. When using Custom: br0 i get issues almost instantly. The main server is 192.168.1.10 and /24 Dockers which are host and ports are OK however if i want to make a docker container with and IP of 1.20 im getting trace warnings for macvlan within a few minutes and eventually hard crashes. The call traces go away instantly if a container is shutdown or removed which uses it's own IP via br0. Im using 6.8.2 but i've had the issue since i started using Unraid on 6.8.0. My network adapter is a 10gig interface which unraid has set up as bond0 Ive included one excerpt from the log below. I've seen other threads on here about this issue but none seem to fix it. Only suggest to use another physical nic fro the docker in question. I came from Freenas using the jails and it was never an issue to use seperate IP addresses per jail? Jan 12 12:40:45 Urbanpixels kernel: CR2: 000019013158a000 CR3: 0000000001e0a005 CR4: 00000000003606f0 Jan 12 12:40:45 Urbanpixels kernel: Call Trace: Jan 12 12:40:45 Urbanpixels kernel: <IRQ> Jan 12 12:40:45 Urbanpixels kernel: nf_nat_used_tuple+0x2e/0x49 [nf_nat] Jan 12 12:40:45 Urbanpixels kernel: nf_nat_setup_info+0x5fd/0x666 [nf_nat] Jan 12 12:40:45 Urbanpixels kernel: ? ipt_do_table+0x5da/0x62a [ip_tables] Jan 12 12:40:45 Urbanpixels kernel: nf_nat_alloc_null_binding+0x71/0x88 [nf_nat] Jan 12 12:40:45 Urbanpixels kernel: nf_nat_inet_fn+0x9f/0x1b9 [nf_nat] Jan 12 12:40:45 Urbanpixels kernel: ? br_handle_local_finish+0xe/0xe Jan 12 12:40:45 Urbanpixels kernel: nf_nat_ipv4_in+0x1e/0x62 [nf_nat_ipv4] Jan 12 12:40:45 Urbanpixels kernel: nf_hook_slow+0x3a/0x90 Jan 12 12:40:45 Urbanpixels kernel: br_nf_pre_routing+0x303/0x343 Jan 12 12:40:45 Urbanpixels kernel: ? br_nf_forward_ip+0x362/0x362 Jan 12 12:40:45 Urbanpixels kernel: nf_hook_slow+0x3a/0x90 Jan 12 12:40:45 Urbanpixels kernel: br_handle_frame+0x27e/0x2bd Jan 12 12:40:45 Urbanpixels kernel: ? br_pass_frame_up+0x14a/0x14a Jan 12 12:40:45 Urbanpixels kernel: __netif_receive_skb_core+0x464/0x76e Jan 12 12:40:45 Urbanpixels kernel: ? __kmalloc_node_track_caller+0x11b/0x12c Jan 12 12:40:45 Urbanpixels kernel: __netif_receive_skb_one_core+0x35/0x6f Jan 12 12:40:45 Urbanpixels kernel: netif_receive_skb_internal+0x9f/0xba Jan 12 12:40:45 Urbanpixels kernel: process_responses+0xd4d/0xee4 [cxgb3] Jan 12 12:40:45 Urbanpixels kernel: ? enqueue_task_fair+0xba/0x557 Jan 12 12:40:45 Urbanpixels kernel: napi_rx_handler+0x1f/0x5f [cxgb3] Jan 12 12:40:45 Urbanpixels kernel: net_rx_action+0x107/0x26c Jan 12 12:40:45 Urbanpixels kernel: __do_softirq+0xc9/0x1d7 Jan 12 12:40:45 Urbanpixels kernel: irq_exit+0x5e/0x9d Jan 12 12:40:45 Urbanpixels kernel: do_IRQ+0xb2/0xd0 Jan 12 12:40:45 Urbanpixels kernel: common_interrupt+0xf/0xf Jan 12 12:40:45 Urbanpixels kernel: </IRQ> Jan 12 12:40:45 Urbanpixels kernel: RIP: 0010:cpuidle_enter_state+0xe8/0x141 Jan 12 12:40:45 Urbanpixels kernel: Code: ff 45 84 f6 74 1d 9c 58 0f 1f 44 00 00 0f ba e0 09 73 09 0f 0b fa 66 0f 1f 44 00 00 31 ff e8 e0 99 bb ff fb 66 0f 1f 44 00 00 <48> 2b 2c 24 b8 ff ff ff 7f 48 b9 ff ff ff ff f3 01 00 00 48 39 cd Jan 12 12:40:45 Urbanpixels kernel: RSP: 0018:ffffffff81e03e80 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffd7 Jan 12 12:40:45 Urbanpixels kernel: RAX: ffff888436a1fac0 RBX: ffff888436a2a000 RCX: 000000000000001f Jan 12 12:40:45 Urbanpixels kernel: RDX: 0000000000000000 RSI: 000000002aaaaaaa RDI: 0000000000000000 Jan 12 12:40:45 Urbanpixels kernel: RBP: 00002e3c05b1e5ca R08: 00002e3c05b1e5ca R09: 000000000000156b Jan 12 12:40:45 Urbanpixels kernel: R10: 0000000008a03324 R11: 071c71c71c71c71c R12: 0000000000000006 Jan 12 12:40:45 Urbanpixels kernel: R13: ffffffff81e5b1a0 R14: 0000000000000000 R15: ffffffff81e5b3f8 Jan 12 12:40:45 Urbanpixels kernel: do_idle+0x17e/0x1fc Jan 12 12:40:45 Urbanpixels kernel: cpu_startup_entry+0x6a/0x6c Jan 12 12:40:45 Urbanpixels kernel: start_kernel+0x44e/0x46c Jan 12 12:40:45 Urbanpixels kernel: secondary_startup_64+0xa4/0xb0 Jan 12 12:41:12 Urbanpixels kernel: rcu: INFO: rcu_bh self-detected stall on CPU Jan 12 12:41:12 Urbanpixels kernel: rcu: 3-....: (1903655 ticks this GP) idle= urbanpixels-diagnostics-20200204-1353.zip Edited February 4, 2020 by Urbanpixels Quote Link to comment
bonienl Posted February 4, 2020 Share Posted February 4, 2020 Please provide complete diagnostics. See Tools -> Diagnostics Quote Link to comment
Urbanpixels Posted February 4, 2020 Author Share Posted February 4, 2020 Sure it can be found on the link below - https://www.dropbox.com/s/r3bxlxovm7rpzgo/urbanpixels-diagnostics-20200204-1353.zip?dl=0 Quote Link to comment
Urbanpixels Posted February 7, 2020 Author Share Posted February 7, 2020 Hi Guys, So I've had a bit of an update with my issues. I reinstalled all my dockers which were causing issues and overnight the system crashed but not in the same way as before. I could not access my webGUI at all. I was given a NGINX error 500 after a few seconds. I can access SSH all my dockers are working and shares are still accessible which is not the same as before. I've attached a new log file which shows some Macvlan issues around 2am on the 7th Feb. I gave a restart command with powerdown -r but this didn't do anything. I had to run it as Sudo which did restart the box albeit uncleanly and triggered a parity check. If anybody has any ideas it would be appreciated. Without Pihole and Homebridge running the installation is Solid. Only when i use dockers will different IP's to the unraid box do these issues occur TIA urbanpixels-diagnostics-20200207-0752.zip Quote Link to comment
Urbanpixels Posted February 8, 2020 Author Share Posted February 8, 2020 The only thing i can seem to zero this issue down is the mellinox drivers which seem to have an issue with Macvlan. I've set up dockers Br0 to another nic on my system and so far no call traces within 48 hours. Using the 10gig for the dockers introduced them instantly. 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.