Stan464 Posted March 7 Share Posted March 7 Hi All, Is the Macvlan issue still floating about, just rebooted my Server due to the WebUI becoming unrespponsive to ALL Comms (SSH, HTTP etc) found this in the Log 5 minutes after reboot. Mar 7 21:04:17 CTU-UNRAID-2 kernel: WARNING: CPU: 10 PID: 889 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Mar 7 21:04:17 CTU-UNRAID-2 kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap macvlan veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs cmac cifs asn1_decoder cifs_arc4 cifs_md4 dns_resolver nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls amdgpu gpu_sched drm_buddy radeon edac_mce_amd edac_core intel_rapl_msr intel_rapl_common iosf_mbi kvm_amd video i2c_algo_bit drm_ttm_helper ttm kvm drm_display_helper crct10dif_pclmul drm_kms_helper crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 wmi_bmof drm sha256_ssse3 sha1_ssse3 mpt3sas aesni_intel crypto_simd cryptd backlight Mar 7 21:04:17 CTU-UNRAID-2 kernel: agpgart i2c_piix4 r8169 syscopyarea ahci raid_class sysfillrect sysimgblt rapl i2c_core k10temp ccp scsi_transport_sas fb_sys_fops libahci realtek wmi button acpi_cpufreq unix Mar 7 21:04:17 CTU-UNRAID-2 kernel: CPU: 10 PID: 889 Comm: kworker/u64:9 Tainted: P O 6.1.74-Unraid #1 Mar 7 21:04:17 CTU-UNRAID-2 kernel: Hardware name: System manufacturer System Product Name/PRIME B350-PLUS, BIOS 5204 07/30/2019 Mar 7 21:04:17 CTU-UNRAID-2 kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan] Mar 7 21:04:17 CTU-UNRAID-2 kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Mar 7 21:04:17 CTU-UNRAID-2 kernel: Code: 44 24 10 e8 e2 e1 ff ff 8b 7c 24 04 89 ea 89 c6 89 04 24 e8 7e e6 ff ff 84 c0 75 a2 48 89 df e8 9b e2 ff ff 85 c0 89 c5 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 18 dd ff ff e8 93 e3 ff ff e9 72 01 Mar 7 21:04:17 CTU-UNRAID-2 kernel: RSP: 0018:ffffc900004b4d98 EFLAGS: 00010202 Mar 7 21:04:17 CTU-UNRAID-2 kernel: RAX: 0000000000000001 RBX: ffff88838be09400 RCX: 547d69d0ee32b74b Mar 7 21:04:17 CTU-UNRAID-2 kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88838be09400 Mar 7 21:04:17 CTU-UNRAID-2 kernel: RBP: 0000000000000001 R08: 4941756a7dbdf323 R09: da3bcc70157fb31a Mar 7 21:04:17 CTU-UNRAID-2 kernel: R10: 41b60faddf0c141a R11: ffffc900004b4d60 R12: ffffffff82a14d00 Mar 7 21:04:17 CTU-UNRAID-2 kernel: R13: 00000000000190fa R14: ffff88819d8b6d00 R15: 0000000000000000 Mar 7 21:04:17 CTU-UNRAID-2 kernel: FS: 0000000000000000(0000) GS:ffff8887fea80000(0000) knlGS:0000000000000000 Mar 7 21:04:17 CTU-UNRAID-2 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 7 21:04:17 CTU-UNRAID-2 kernel: CR2: 000014e593775eb0 CR3: 00000001ecbcc000 CR4: 00000000003506e0 Mar 7 21:04:17 CTU-UNRAID-2 kernel: Call Trace: Mar 7 21:04:17 CTU-UNRAID-2 kernel: <IRQ> Mar 7 21:04:17 CTU-UNRAID-2 kernel: ? __warn+0xab/0x122 Mar 7 21:04:17 CTU-UNRAID-2 kernel: ? report_bug+0x109/0x17e Mar 7 21:04:17 CTU-UNRAID-2 kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Mar 7 21:04:17 CTU-UNRAID-2 kernel: ? handle_bug+0x41/0x6f Mar 7 21:04:17 CTU-UNRAID-2 kernel: ? exc_invalid_op+0x13/0x60 Mar 7 21:04:17 CTU-UNRAID-2 kernel: ? asm_exc_invalid_op+0x16/0x20 Mar 7 21:04:17 CTU-UNRAID-2 kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Mar 7 21:04:17 CTU-UNRAID-2 kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack] Mar 7 21:04:17 CTU-UNRAID-2 kernel: ? nf_nat_inet_fn+0x126/0x1a8 [nf_nat] Mar 7 21:04:17 CTU-UNRAID-2 kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] Mar 7 21:04:17 CTU-UNRAID-2 kernel: nf_hook_slow+0x3d/0x96 Mar 7 21:04:17 CTU-UNRAID-2 kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Mar 7 21:04:17 CTU-UNRAID-2 kernel: NF_HOOK.constprop.0+0x79/0xd9 Mar 7 21:04:17 CTU-UNRAID-2 kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Mar 7 21:04:17 CTU-UNRAID-2 kernel: __netif_receive_skb_one_core+0x77/0x9c Mar 7 21:04:17 CTU-UNRAID-2 kernel: process_backlog+0x8c/0x116 Mar 7 21:04:17 CTU-UNRAID-2 kernel: __napi_poll.constprop.0+0x2b/0x124 Mar 7 21:04:17 CTU-UNRAID-2 kernel: net_rx_action+0x159/0x24f Mar 7 21:04:17 CTU-UNRAID-2 kernel: __do_softirq+0x129/0x288 Mar 7 21:04:17 CTU-UNRAID-2 kernel: do_softirq+0x7f/0xab Mar 7 21:04:17 CTU-UNRAID-2 kernel: </IRQ> Mar 7 21:04:17 CTU-UNRAID-2 kernel: <TASK> Mar 7 21:04:17 CTU-UNRAID-2 kernel: __local_bh_enable_ip+0x4c/0x6b Mar 7 21:04:17 CTU-UNRAID-2 kernel: netif_rx+0x52/0x5a Mar 7 21:04:17 CTU-UNRAID-2 kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Mar 7 21:04:17 CTU-UNRAID-2 kernel: ? _raw_spin_unlock+0x14/0x29 Mar 7 21:04:17 CTU-UNRAID-2 kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Mar 7 21:04:17 CTU-UNRAID-2 kernel: process_one_work+0x1ab/0x295 Mar 7 21:04:17 CTU-UNRAID-2 kernel: worker_thread+0x18b/0x244 Mar 7 21:04:17 CTU-UNRAID-2 kernel: ? rescuer_thread+0x281/0x281 Mar 7 21:04:17 CTU-UNRAID-2 kernel: kthread+0xe7/0xef Mar 7 21:04:17 CTU-UNRAID-2 kernel: ? kthread_complete_and_exit+0x1b/0x1b Mar 7 21:04:17 CTU-UNRAID-2 kernel: ret_from_fork+0x22/0x30 Mar 7 21:04:17 CTU-UNRAID-2 kernel: </TASK> Mar 7 21:04:17 CTU-UNRAID-2 kernel: ---[ end trace 0000000000000000 ]--- Mar 7 21:04:31 CTU-UNRAID-2 kernel: br0: port 2(vnet0) entered blocking state Mar 7 21:04:31 CTU-UNRAID-2 kernel: br0: port 2(vnet0) entered disabled state Mar 7 21:04:31 CTU-UNRAID-2 kernel: device vnet0 entered promiscuous mode Mar 7 21:04:31 CTU-UNRAID-2 kernel: br0: port 2(vnet0) entered blocking state Mar 7 21:04:31 CTU-UNRAID-2 kernel: br0: port 2(vnet0) entered forwarding state Mar 7 21:04:31 CTU-UNRAID-2 kernel: br0: port 3(vnet1) entered blocking state Mar 7 21:04:31 CTU-UNRAID-2 kernel: br0: port 3(vnet1) entered disabled state Mar 7 21:04:31 CTU-UNRAID-2 kernel: device vnet1 entered promiscuous mode Mar 7 21:04:31 CTU-UNRAID-2 kernel: br0: port 3(vnet1) entered blocking state Mar 7 21:04:31 CTU-UNRAID-2 kernel: br0: port 3(vnet1) entered forwarding state Mar 7 21:04:32 CTU-UNRAID-2 kernel: br0: port 4(vnet2) entered blocking state Mar 7 21:04:32 CTU-UNRAID-2 kernel: br0: port 4(vnet2) entered disabled state Mar 7 21:04:32 CTU-UNRAID-2 kernel: device vnet2 entered promiscuous mode Mar 7 21:04:32 CTU-UNRAID-2 kernel: br0: port 4(vnet2) entered blocking state Mar 7 21:04:32 CTU-UNRAID-2 kernel: br0: port 4(vnet2) entered forwarding state Quote Link to comment
itimpi Posted March 7 Share Posted March 7 If you want to continue using macvlan then you need to make sure bridging is disabled on eth0. Quote Link to comment
Stan464 Posted March 8 Author Share Posted March 8 8 hours ago, itimpi said: If you want to continue using macvlan then you need to make sure bridging is disabled on eth0. Would that my Dockers useless as they wouldn't be able to communicate correctly/at all. Bridging is what allows the dockers to use the Host (the Server) to obtain an IP Address, it also allows flow of traffic🤣. Quote Link to comment
itimpi Posted March 8 Share Posted March 8 1 hour ago, Stan464 said: Would that my Dockers useless as they wouldn't be able to communicate correctly/at all. Bridging is what allows the dockers to use the Host (the Server) to obtain an IP Address, it also allows flow of traffic🤣. The combination of macvlan and bridging on eth0 is known to be highly likely to cause the system to crash. If you need to use bridging then you should set the docker networking to use ipvlan instead. 1 Quote Link to comment
Solution ich777 Posted March 8 Solution Share Posted March 8 2 hours ago, Stan464 said: Bridging is what allows the dockers to use the Host (the Server) to obtain an IP Address, it also allows flow of traffic🤣. That's not entirely true, please also see the documentation: https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces As @itimpi pointed out either use bridging with ipvlan (if you network gear supports it) or disable bridging and use macvlan. 1 Quote Link to comment
Stan464 Posted March 8 Author Share Posted March 8 Appreciate the response guys, will re-look at the config. Thanks All! ❤️ 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.