guest_user Posted September 17, 2021 Share Posted September 17, 2021 I don't want to but i am getting very tired on Unraid.. I had a rock solid system, dog slow but solid. Not long ago i fed Unraid some new hardware (cpu, mobo, ram bigger cache..) thinking that that would make it happy... But no. There is the normal array of dockers and only 1 half baked win10 vm. with all Dockers turned off it will run stable, running any more than just pihole I get massive instability (Unraid will hang and need a hard reboot at least once a day. The error is always the same, starts with 'BTRFS critical (Device nvme1n1p1): corrupt leaf.... *see the attached image I have tried different nvme drives for my cache, I have tried different nic's (onboard / pcie .. 1g/10g) i have swapped ram, (32gb of older DDR4 has given better stability than the brand new 64gb but still no more than 7 days without crashing) and now its crashed 3 time in 2 days. even on a reboot I get this after boot: Sep 17 21:13:40 NAS01 kernel: ------------[ cut here ]------------ Sep 17 21:13:40 NAS01 kernel: WARNING: CPU: 2 PID: 21650 at net/netfilter/nf_conntrack_core.c:1120 __nf_conntrack_confirm+0x9b/0x1e6 [nf_conntrack] Sep 17 21:13:40 NAS01 kernel: Modules linked in: nvidia_uvm(PO) xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle nf_tables vhost_net tun vhost vhost_iotlb tap macvlan veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi i915 iosf_mbi drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nct6775 hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding igb i2c_algo_bit wmi_bmof intel_wmi_thunderbolt x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd nvme nvme_core ahci i2c_i801 glue_helper input_leds i2c_smbus i2c_core libahci led_class aacraid video wmi thermal backlight fan acpi_pad button Sep 17 21:13:40 NAS01 kernel: [last unloaded: i2c_algo_bit] Sep 17 21:13:40 NAS01 kernel: CPU: 2 PID: 21650 Comm: kworker/2:2 Tainted: P O 5.10.28-Unraid #1 Sep 17 21:13:40 NAS01 kernel: Hardware name: ASUS System Product Name/Pro WS W480-ACE, BIOS 2301 07/08/2021 Sep 17 21:13:40 NAS01 kernel: Workqueue: events macvlan_process_broadcast [macvlan] Sep 17 21:13:40 NAS01 kernel: RIP: 0010:__nf_conntrack_confirm+0x9b/0x1e6 [nf_conntrack] Sep 17 21:13:40 NAS01 kernel: Code: e8 dc f8 ff ff 44 89 fa 89 c6 41 89 c4 48 c1 eb 20 89 df 41 89 de e8 36 f6 ff ff 84 c0 75 bb 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 89 df 44 89 e6 31 db e8 6d f3 ff ff e8 35 f5 ff ff e9 22 01 Sep 17 21:13:40 NAS01 kernel: RSP: 0018:ffffc900001ccdd8 EFLAGS: 00010202 Sep 17 21:13:40 NAS01 kernel: RAX: 0000000000000188 RBX: 000000000000a957 RCX: 000000004e4652a6 Sep 17 21:13:40 NAS01 kernel: RDX: 0000000000000000 RSI: 00000000000002cd RDI: ffffffffa0315d34 Sep 17 21:13:40 NAS01 kernel: RBP: ffff8881a989ba40 R08: 000000008b40c334 R09: ffff888208c727c0 Sep 17 21:13:40 NAS01 kernel: R10: 0000000000000000 R11: ffff8882e0e2f200 R12: 000000000000e6cd Sep 17 21:13:40 NAS01 kernel: R13: ffffffff8210b440 R14: 000000000000a957 R15: 0000000000000000 Sep 17 21:13:40 NAS01 kernel: FS: 0000000000000000(0000) GS:ffff88884fc80000(0000) knlGS:0000000000000000 Sep 17 21:13:40 NAS01 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 17 21:13:40 NAS01 kernel: CR2: 0000151652d27718 CR3: 000000000200a004 CR4: 0000000000770ee0 Sep 17 21:13:40 NAS01 kernel: PKRU: 55555554 Sep 17 21:13:40 NAS01 kernel: Call Trace: Sep 17 21:13:40 NAS01 kernel: <IRQ> Sep 17 21:13:40 NAS01 kernel: nf_conntrack_confirm+0x2f/0x36 [nf_conntrack] Sep 17 21:13:40 NAS01 kernel: nf_hook_slow+0x39/0x8e Sep 17 21:13:40 NAS01 kernel: nf_hook.constprop.0+0xb1/0xd8 Sep 17 21:13:40 NAS01 kernel: ? ip_protocol_deliver_rcu+0xfe/0xfe Sep 17 21:13:40 NAS01 kernel: ip_local_deliver+0x49/0x75 Sep 17 21:13:40 NAS01 kernel: __netif_receive_skb_one_core+0x74/0x95 Sep 17 21:13:40 NAS01 kernel: process_backlog+0xa3/0x13b Sep 17 21:13:40 NAS01 kernel: net_rx_action+0xf4/0x29d Sep 17 21:13:40 NAS01 kernel: __do_softirq+0xc4/0x1c2 Sep 17 21:13:40 NAS01 kernel: asm_call_irq_on_stack+0xf/0x20 Sep 17 21:13:40 NAS01 kernel: </IRQ> Sep 17 21:13:40 NAS01 kernel: do_softirq_own_stack+0x2c/0x39 Sep 17 21:13:40 NAS01 kernel: do_softirq+0x3a/0x44 Sep 17 21:13:40 NAS01 kernel: netif_rx_ni+0x1c/0x22 Sep 17 21:13:40 NAS01 kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Sep 17 21:13:40 NAS01 kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] Sep 17 21:13:40 NAS01 kernel: process_one_work+0x13c/0x1d5 Sep 17 21:13:40 NAS01 kernel: worker_thread+0x18b/0x22f Sep 17 21:13:40 NAS01 kernel: ? process_scheduled_works+0x27/0x27 Sep 17 21:13:40 NAS01 kernel: kthread+0xe5/0xea Sep 17 21:13:40 NAS01 kernel: ? __kthread_bind_mask+0x57/0x57 Sep 17 21:13:40 NAS01 kernel: ret_from_fork+0x1f/0x30 Sep 17 21:13:40 NAS01 kernel: ---[ end trace 9f8fe0c8367f8603 ]--- I'm about ready to put it on the road for a truck to run over if it was nit so heavy.. sigh please help nas01-diagnostics-20210917-2113.zip Quote Link to comment
JorgeB Posted September 17, 2021 Share Posted September 17, 2021 1 hour ago, guest_user said: Sep 17 21:13:40 NAS01 kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Sep 17 21:13:40 NAS01 kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] Macvlan 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, or more info below. 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
guest_user Posted September 17, 2021 Author Share Posted September 17, 2021 Thanks @JorgeB i have updated to 6.10 and the has cleared the macvlan error in the system log! could that also have been what was causing the cache drive issues and killing the server? Quote Link to comment
JorgeB Posted September 18, 2021 Share Posted September 18, 2021 9 hours ago, guest_user said: killing the server? This yes, and server crashing can cause issues with the cache filesystem, see how it goes for now, if cache keeps getting corrupt there could be other issues, like bad RAM. Quote Link to comment
guest_user Posted September 18, 2021 Author Share Posted September 18, 2021 Yes, my first thought way back when was it must be bad RAM but after swapping for known good RAM and it still happening i was getting very frustrated.. hahaha We are over 8 and a half hours in and so far it's running like a dream. lets wait and see 2 Quote Link to comment
guest_user Posted September 18, 2021 Author Share Posted September 18, 2021 ok I take that back, after starting up a bunch of dockers and trying to push it, it fell over: from the system log: Sep 18 18:10:33 NAS01 kernel: general protection fault, probably for non-canonical address 0x614320646c6f42cb: 0000 [#1] SMP NOPTI Sep 18 18:10:33 NAS01 kernel: CPU: 3 PID: 25217 Comm: nzbget Tainted: P W O 5.13.8-Unraid #1 Sep 18 18:10:33 NAS01 kernel: Hardware name: ASUS System Product Name/Pro WS W480-ACE, BIOS 2301 07/08/2021 Sep 18 18:10:33 NAS01 kernel: RIP: 0010:nf_nat_setup_info+0x12f/0x6d9 [nf_nat] Sep 18 18:10:33 NAS01 kernel: Code: 15 52 6a 00 00 89 c0 48 8d 04 c2 48 8b 10 48 85 d2 74 07 48 81 ea 98 00 00 00 45 31 c0 48 85 d2 0f 84 6d ff ff ff 8a 44 24 46 <38> 42 46 74 19 48 8b 92 98 00 00 00 48 85 d2 0f 84 54 ff ff ff 48 Sep 18 18:10:33 NAS01 kernel: RSP: 0018:ffffc900002007b8 EFLAGS: 00010202 Sep 18 18:10:33 NAS01 kernel: RAX: ffff888196e1a911 RBX: ffff88819196d180 RCX: 0000000000000000 Sep 18 18:10:33 NAS01 kernel: RDX: 614320646c6f4285 RSI: 00000000473b52ac RDI: ffffc900002007d8 Sep 18 18:10:33 NAS01 kernel: RBP: ffffc90000200880 R08: 0000000000000000 R09: ffff888191154260 Sep 18 18:10:33 NAS01 kernel: R10: ffff888758eec388 R11: ffffffff816ae1c2 R12: 0000000000000000 Sep 18 18:10:33 NAS01 kernel: R13: ffffc900002007d8 R14: ffffc90000200894 R15: ffffffff82168b00 Sep 18 18:10:33 NAS01 kernel: FS: 000014ad7b5fa700(0000) GS:ffff88884fcc0000(0000) knlGS:0000000000000000 Sep 18 18:10:33 NAS01 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 18 18:10:33 NAS01 kernel: CR2: 000014ae88093000 CR3: 0000000246eca004 CR4: 0000000000770ee0 Sep 18 18:10:33 NAS01 kernel: PKRU: 55555554 Sep 18 18:10:33 NAS01 kernel: Call Trace: Sep 18 18:10:33 NAS01 kernel: <IRQ> Sep 18 18:10:33 NAS01 kernel: ? __ksize+0x1e/0x76 Sep 18 18:10:33 NAS01 kernel: ? krealloc+0x31/0x89 Sep 18 18:10:33 NAS01 kernel: nf_nat_masquerade_ipv4+0x110/0x136 [nf_nat] Sep 18 18:10:33 NAS01 kernel: masquerade_tg+0x47/0x61 [xt_MASQUERADE] Sep 18 18:10:33 NAS01 kernel: ? __dev_queue_xmit+0x507/0x52f Sep 18 18:10:33 NAS01 kernel: ipt_do_table+0x4f1/0x597 [ip_tables] Sep 18 18:10:33 NAS01 kernel: ? fib_validate_source+0xb5/0xe1 Sep 18 18:10:33 NAS01 kernel: ? ipt_do_table+0x547/0x597 [ip_tables] Sep 18 18:10:33 NAS01 kernel: nf_nat_inet_fn+0xfc/0x19c [nf_nat] Sep 18 18:10:33 NAS01 kernel: nf_nat_ipv4_out+0x15/0x8b [nf_nat] Sep 18 18:10:33 NAS01 kernel: nf_hook_slow+0x3b/0x93 Sep 18 18:10:33 NAS01 kernel: nf_hook+0xab/0xd3 Sep 18 18:10:33 NAS01 kernel: ? __ip_finish_output+0x14b/0x14b Sep 18 18:10:33 NAS01 kernel: ip_output+0x82/0x8f Sep 18 18:10:33 NAS01 kernel: ? __ip_finish_output+0x14b/0x14b Sep 18 18:10:33 NAS01 kernel: ip_sabotage_in+0x49/0x59 [br_netfilter] Sep 18 18:10:33 NAS01 kernel: nf_hook_slow+0x3b/0x93 Sep 18 18:10:33 NAS01 kernel: ? ip_rcv_finish_core.constprop.0+0x351/0x351 Sep 18 18:10:33 NAS01 kernel: NF_HOOK.constprop.0+0x70/0xc8 Sep 18 18:10:33 NAS01 kernel: ? ip_rcv_finish_core.constprop.0+0x351/0x351 Sep 18 18:10:33 NAS01 kernel: __netif_receive_skb_one_core+0x77/0x98 Sep 18 18:10:33 NAS01 kernel: netif_receive_skb+0xac/0x103 Sep 18 18:10:33 NAS01 kernel: br_handle_frame_finish+0x325/0x369 Sep 18 18:10:33 NAS01 kernel: ? __br_multicast_querier_exists+0x42/0x42 Sep 18 18:10:33 NAS01 kernel: br_nf_hook_thresh+0xc3/0xf7 [br_netfilter] Sep 18 18:10:33 NAS01 kernel: ? __br_multicast_querier_exists+0x42/0x42 Sep 18 18:10:33 NAS01 kernel: br_nf_pre_routing_finish+0x23e/0x265 [br_netfilter] Sep 18 18:10:33 NAS01 kernel: ? __br_multicast_querier_exists+0x42/0x42 Sep 18 18:10:33 NAS01 kernel: ? NF_HOOK.isra.0+0xc5/0x119 [br_netfilter] Sep 18 18:10:33 NAS01 kernel: ? br_handle_frame_finish+0x369/0x369 Sep 18 18:10:33 NAS01 kernel: br_nf_pre_routing+0x226/0x236 [br_netfilter] Sep 18 18:10:33 NAS01 kernel: ? br_nf_forward_finish+0xd8/0xd8 [br_netfilter] Sep 18 18:10:33 NAS01 kernel: br_handle_frame+0x2a0/0x2eb Sep 18 18:10:33 NAS01 kernel: ? __br_multicast_querier_exists+0x42/0x42 Sep 18 18:10:33 NAS01 kernel: __netif_receive_skb_core+0x368/0x52e Sep 18 18:10:33 NAS01 kernel: __netif_receive_skb_one_core+0x40/0x98 Sep 18 18:10:33 NAS01 kernel: process_backlog+0xab/0x143 Sep 18 18:10:33 NAS01 kernel: __napi_poll+0x27/0x114 Sep 18 18:10:33 NAS01 kernel: net_rx_action+0xe8/0x1f2 Sep 18 18:10:33 NAS01 kernel: __do_softirq+0xec/0x21b Sep 18 18:10:33 NAS01 kernel: do_softirq+0x50/0x68 Sep 18 18:10:33 NAS01 kernel: </IRQ> Sep 18 18:10:33 NAS01 kernel: __local_bh_enable_ip+0x40/0x48 Sep 18 18:10:33 NAS01 kernel: ip_finish_output2+0x2f8/0x32b Sep 18 18:10:33 NAS01 kernel: ip_send_skb+0x15/0x37 Sep 18 18:10:33 NAS01 kernel: udp_send_skb+0x253/0x2b5 Sep 18 18:10:33 NAS01 kernel: udp_sendmsg+0x55a/0x733 Sep 18 18:10:33 NAS01 kernel: ? ip_mc_finish_output+0x69/0x69 Sep 18 18:10:33 NAS01 kernel: ? __fget_files+0x57/0x63 Sep 18 18:10:33 NAS01 kernel: sock_sendmsg_nosec+0x2b/0x3c Sep 18 18:10:33 NAS01 kernel: __sys_sendto+0xd3/0x10e Sep 18 18:10:33 NAS01 kernel: ? __sys_connect+0x78/0xa2 Sep 18 18:10:33 NAS01 kernel: __x64_sys_sendto+0x25/0x28 Sep 18 18:10:33 NAS01 kernel: do_syscall_64+0x60/0x76 Sep 18 18:10:33 NAS01 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Sep 18 18:10:33 NAS01 kernel: RIP: 0033:0x6f12cf Sep 18 18:10:33 NAS01 kernel: Code: 53 49 89 f4 89 fb 48 83 ec 10 e8 0c f8 ff ff 45 31 c9 89 c5 45 31 c0 4d 63 d5 4c 89 f2 4c 89 e6 48 63 fb b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 1e 89 ef 48 89 44 24 08 e8 3d f8 ff ff 48 8b Sep 18 18:10:33 NAS01 kernel: RSP: 002b:000014ad7b5f7de0 EFLAGS: 00000246 ORIG_RAX: 000000000000002c Sep 18 18:10:33 NAS01 kernel: RAX: ffffffffffffffda RBX: 000000000000005a RCX: 00000000006f12cf Sep 18 18:10:33 NAS01 kernel: RDX: 0000000000000024 RSI: 000014ad7b5f8030 RDI: 000000000000005a Sep 18 18:10:33 NAS01 kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 Sep 18 18:10:33 NAS01 kernel: R10: 0000000000004000 R11: 0000000000000246 R12: 000014ad7b5f8030 Sep 18 18:10:33 NAS01 kernel: R13: 0000000000004000 R14: 0000000000000024 R15: 000014ad7b5fadb8 Sep 18 18:10:33 NAS01 kernel: Modules linked in: nvidia_modeset(PO) nvidia_uvm(PO) veth xt_nat xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod nvidia(PO) iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi i915 iosf_mbi drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nct6775 hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding igb i2c_algo_bit wmi_bmof intel_wmi_thunderbolt x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_i801 intel_cstate intel_uncore i2c_smbus nvme ahci input_leds i2c_core video led_class aacraid nvme_core libahci backlight thermal fan wmi acpi_pad button Sep 18 18:10:33 NAS01 kernel: [last unloaded: i2c_algo_bit] Sep 18 18:10:33 NAS01 kernel: ---[ end trace 548612d6da2f5d1b ]--- attached is what was left on the screen any other tips? Quote Link to comment
guest_user Posted September 18, 2021 Author Share Posted September 18, 2021 Here is another snip from the system log, why is 9.10.0-rc1 still using macvlan?? Sep 18 18:33:36 NAS01 kernel: CPU: 5 PID: 115 Comm: kworker/5:1 Tainted: P O 5.13.8-Unraid #1 Sep 18 18:33:36 NAS01 kernel: Hardware name: ASUS System Product Name/Pro WS W480-ACE, BIOS 2301 07/08/2021 Sep 18 18:33:36 NAS01 kernel: Workqueue: events macvlan_process_broadcast [macvlan] Sep 18 18:33:36 NAS01 kernel: RIP: 0010:__nf_conntrack_confirm+0xa0/0x1eb [nf_conntrack] Sep 18 18:33:36 NAS01 kernel: Code: e8 7e f6 ff ff 44 89 fa 89 c6 41 89 c4 48 c1 eb 20 89 df 41 89 de e8 92 f4 ff ff 84 c0 75 bb 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 89 df 44 89 e6 31 db e8 c6 ed ff ff e8 09 f3 ff ff e9 22 01 Sep 18 18:33:36 NAS01 kernel: RSP: 0018:ffffc90000258dc8 EFLAGS: 00010202 Sep 18 18:33:36 NAS01 kernel: RAX: 0000000000000188 RBX: 0000000000007748 RCX: 0000000097a6698c Sep 18 18:33:36 NAS01 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffffa02d1ee0 Sep 18 18:33:36 NAS01 kernel: RBP: ffff888250935e00 R08: 00000000a4ed46f5 R09: ffff8881e76fa0a0 Sep 18 18:33:36 NAS01 kernel: R10: 0000000000000098 R11: 0000000000000000 R12: 000000000000587e Sep 18 18:33:36 NAS01 kernel: R13: ffffffff82168b00 R14: 0000000000007748 R15: 0000000000000000 Sep 18 18:33:36 NAS01 kernel: FS: 0000000000000000(0000) GS:ffff88884fd40000(0000) knlGS:0000000000000000 Sep 18 18:33:36 NAS01 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 18 18:33:36 NAS01 kernel: CR2: 000015112b8e8000 CR3: 0000000185772003 CR4: 0000000000770ee0 Sep 18 18:33:36 NAS01 kernel: PKRU: 55555554 Sep 18 18:33:36 NAS01 kernel: Call Trace: Sep 18 18:33:36 NAS01 kernel: <IRQ> Sep 18 18:33:36 NAS01 kernel: nf_conntrack_confirm+0x2f/0x36 [nf_conntrack] Sep 18 18:33:36 NAS01 kernel: nf_hook_slow+0x3b/0x93 Sep 18 18:33:36 NAS01 kernel: ? ip_protocol_deliver_rcu+0x115/0x115 Sep 18 18:33:36 NAS01 kernel: NF_HOOK.constprop.0+0x70/0xc8 Sep 18 18:33:36 NAS01 kernel: ? ip_protocol_deliver_rcu+0x115/0x115 Sep 18 18:33:36 NAS01 kernel: __netif_receive_skb_one_core+0x77/0x98 Sep 18 18:33:36 NAS01 kernel: process_backlog+0xab/0x143 Sep 18 18:33:36 NAS01 kernel: __napi_poll+0x27/0x114 Sep 18 18:33:36 NAS01 kernel: net_rx_action+0xe8/0x1f2 Sep 18 18:33:36 NAS01 kernel: __do_softirq+0xec/0x21b Sep 18 18:33:36 NAS01 kernel: do_softirq+0x50/0x68 Sep 18 18:33:36 NAS01 kernel: </IRQ> Sep 18 18:33:36 NAS01 kernel: netif_rx_ni+0x56/0x8b Sep 18 18:33:36 NAS01 kernel: macvlan_broadcast+0x116/0x144 [macvlan] Sep 18 18:33:36 NAS01 kernel: macvlan_process_broadcast+0xc7/0x10b [macvlan] Sep 18 18:33:36 NAS01 kernel: process_one_work+0x193/0x274 Sep 18 18:33:36 NAS01 kernel: worker_thread+0x19c/0x240 Sep 18 18:33:36 NAS01 kernel: ? rescuer_thread+0x2a2/0x2a2 Sep 18 18:33:36 NAS01 kernel: kthread+0xdd/0xe4 Sep 18 18:33:36 NAS01 kernel: ? set_kthread_struct+0x32/0x32 Sep 18 18:33:36 NAS01 kernel: ret_from_fork+0x1f/0x30 Sep 18 18:33:36 NAS01 kernel: ---[ end trace 2c720b2b7f9b3c26 ]--- Quote Link to comment
JorgeB Posted September 18, 2021 Share Posted September 18, 2021 Did you switch to ipvlan mode? Quote Link to comment
guest_user Posted September 18, 2021 Author Share Posted September 18, 2021 Ok, this is going to make look even dumber... how do i do that? i read this in the notes: Quote The new ipvlan mode is introduced to battle the crashes some people experience when using macvlan mode. If that is your case, change to ipvlan mode and test. Changing of mode does not require to reconfigure anything on Docker level, internally everything is being taken care off. and assumed that updating was all I needed to do 😞 looking, all i could find was: https://docs.docker.com/network/ipvlan/ that says add '-d ipvlan' is that what's needed? Quote Link to comment
JorgeB Posted September 18, 2021 Share Posted September 18, 2021 Settings -> Docker Settings -> Docker custom network type -> ipvlan Advanced view must be enable (top right) Quote Link to comment
guest_user Posted September 18, 2021 Author Share Posted September 18, 2021 Well.. Advanced view... Gets me every time hahaha Thank you once again Quote Link to comment
guest_user Posted September 20, 2021 Author Share Posted September 20, 2021 Thanks @JorgeB ipvlan has solved my stability issues 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.