syphant Posted March 24, 2023 Share Posted March 24, 2023 (edited) Lately I have been running into this weird issue every 15 to 20 days where my Unraid server becomes unreachable but the machine is still powered on, I cannot ping it and the Web GUI does not load, all of my docker containers are offline as well. A hard shutdown / power up resolves the issue and everything appears normal afterwards. I had previously set up a remote syslog server but it only shows the 50 most recent logged events, this is what I'm seeing logged: Kernel.Info Mar 24 01:37:25 acidbath kernel: br-7c65b67ee074: port 7(veth90a872f) entered blocking state Kernel.Info Mar 24 01:37:25 acidbath kernel: br-7c65b67ee074: port 7(veth90a872f) entered forwarding state Kernel.Info Mar 24 01:37:25 acidbath kernel: eth0: renamed from veth2c003da Kernel.Info Mar 24 01:37:25 acidbath kernel: br-7c65b67ee074: port 8(veth103010f) entered blocking state Kernel.Info Mar 24 01:37:25 acidbath kernel: br-7c65b67ee074: port 8(veth103010f) entered disabled state Kernel.Info Mar 24 01:37:25 acidbath kernel: device veth103010f entered promiscuous mode Kernel.Info Mar 24 01:37:25 acidbath kernel: br-7c65b67ee074: port 8(veth103010f) entered blocking state Kernel.Info Mar 24 01:37:25 acidbath kernel: br-7c65b67ee074: port 8(veth103010f) entered forwarding state Kernel.Info Mar 24 01:37:25 acidbath kernel: eth0: renamed from vethf9d8671 Kernel.Info Mar 24 01:44:39 acidbath kernel: TCP: request_sock_TCP: Possible SYN flooding on port 8080. Sending cookies. Check SNMP counters. Kernel.Info Mar 24 01:45:32 acidbath kernel: br-7c65b67ee074: port 9(vethf00e394) entered blocking state Kernel.Info Mar 24 01:45:32 acidbath kernel: br-7c65b67ee074: port 9(vethf00e394) entered disabled state Kernel.Info Mar 24 01:45:32 acidbath kernel: device vethf00e394 entered promiscuous mode Kernel.Info Mar 24 01:45:32 acidbath kernel: eth0: renamed from veth2b71823 Kernel.Info Mar 24 01:45:32 acidbath kernel: br-7c65b67ee074: port 9(vethf00e394) entered blocking state Kernel.Info Mar 24 01:45:32 acidbath kernel: br-7c65b67ee074: port 9(vethf00e394) entered forwarding state Kernel.Info Mar 24 01:45:53 acidbath kernel: veth2b71823: renamed from eth0 Kernel.Info Mar 24 01:45:53 acidbath kernel: br-7c65b67ee074: port 9(vethf00e394) entered disabled state Kernel.Info Mar 24 01:45:53 acidbath kernel: br-7c65b67ee074: port 9(vethf00e394) entered disabled state Kernel.Info Mar 24 01:45:53 acidbath kernel: device vethf00e394 left promiscuous mode Kernel.Info Mar 24 01:45:53 acidbath kernel: br-7c65b67ee074: port 9(vethf00e394) entered disabled state Kernel.Info Mar 24 01:45:58 acidbath kernel: br-7c65b67ee074: port 9(vethb689dab) entered blocking state Kernel.Info Mar 24 01:45:58 acidbath kernel: br-7c65b67ee074: port 9(vethb689dab) entered disabled state Kernel.Info Mar 24 01:45:58 acidbath kernel: device vethb689dab entered promiscuous mode Kernel.Info Mar 24 01:45:59 acidbath kernel: eth0: renamed from veth045adb6 Kernel.Info Mar 24 01:45:59 acidbath kernel: br-7c65b67ee074: port 9(vethb689dab) entered blocking state Kernel.Info Mar 24 01:45:59 acidbath kernel: br-7c65b67ee074: port 9(vethb689dab) entered forwarding state Kernel.Info Mar 24 01:48:36 acidbath kernel: br-7c65b67ee074: port 9(vethb689dab) entered disabled state Kernel.Info Mar 24 01:48:36 acidbath kernel: veth045adb6: renamed from eth0 Kernel.Info Mar 24 01:48:36 acidbath kernel: br-7c65b67ee074: port 9(vethb689dab) entered disabled state Kernel.Info Mar 24 01:48:36 acidbath kernel: device vethb689dab left promiscuous mode Kernel.Info Mar 24 01:48:36 acidbath kernel: br-7c65b67ee074: port 9(vethb689dab) entered disabled state Kernel.Info Mar 24 01:48:42 acidbath kernel: br-7c65b67ee074: port 9(vethc871276) entered blocking state Kernel.Info Mar 24 01:48:42 acidbath kernel: br-7c65b67ee074: port 9(vethc871276) entered disabled state Kernel.Info Mar 24 01:48:42 acidbath kernel: device vethc871276 entered promiscuous mode Kernel.Info Mar 24 01:48:42 acidbath kernel: eth0: renamed from veth6f72b3a Kernel.Info Mar 24 01:48:42 acidbath kernel: br-7c65b67ee074: port 9(vethc871276) entered blocking state Kernel.Info Mar 24 01:48:42 acidbath kernel: br-7c65b67ee074: port 9(vethc871276) entered forwarding state Kernel.Info Mar 24 01:48:55 acidbath kernel: br-7c65b67ee074: port 9(vethc871276) entered disabled state Kernel.Info Mar 24 01:48:55 acidbath kernel: veth6f72b3a: renamed from eth0 Kernel.Info Mar 24 01:48:55 acidbath kernel: br-7c65b67ee074: port 9(vethc871276) entered disabled state Kernel.Info Mar 24 01:48:55 acidbath kernel: device vethc871276 left promiscuous mode Kernel.Info Mar 24 01:48:55 acidbath kernel: br-7c65b67ee074: port 9(vethc871276) entered disabled state Kernel.Info Mar 24 01:49:16 acidbath kernel: br-7c65b67ee074: port 9(veth40507b2) entered blocking state Kernel.Info Mar 24 01:49:16 acidbath kernel: br-7c65b67ee074: port 9(veth40507b2) entered disabled state Kernel.Info Mar 24 01:49:16 acidbath kernel: device veth40507b2 entered promiscuous mode Kernel.Info Mar 24 01:49:16 acidbath kernel: eth0: renamed from veth2d9c034 Kernel.Info Mar 24 01:49:16 acidbath kernel: br-7c65b67ee074: port 9(veth40507b2) entered blocking state Kernel.Info Mar 24 01:49:16 acidbath kernel: br-7c65b67ee074: port 9(veth40507b2) entered forwarding state Cron.Notice Mar 24 02:00:16 acidbath crond[1190]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null I have also attached a diagnostic that was exported immediately after powercycling the server to bring it back online. To my untrained eye, I can't make heads or tails of it unfortunately, I'd appreciate any insight from more knowledgeable members of the community if anything seems obviously wrong. Thanks in advance! acidbath-diagnostics-20230324-1015.zip Edited March 24, 2023 by syphant Quote Link to comment
JorgeB Posted March 24, 2023 Share Posted March 24, 2023 Not having anything relevant logged points to a hardware problem, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one. Quote Link to comment
syphant Posted April 2, 2023 Author Share Posted April 2, 2023 (edited) On 3/24/2023 at 10:46 AM, JorgeB said: Not having anything relevant logged points to a hardware problem, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one. So I gave this a try as you advised, but it happened again last night at the same time, curiously though the last log message sent was the same: Cron.Notice Apr 2 02:00:16 acidbath crond[1171]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null As expected, mover is scheduled to run daily at 2:00am, so maybe mover is the culprit somehow? Not sure if it matters, but my setup is a bit unconventional. I really only use Unraid for ease of running docker containers/VMs and for mounting my Google Drive via Rclone, so I don't use the "array" feature at all (which solely consists of one 32GB USB stick because you're forced to have at least 1 device in the array). I don't have any shares using the array (all are set to cache only) and there is no data on the array so mover is not really needed at all in my use case. I found that some people "disable" mover by renaming the binary in /usr/local/sbin/ to something else ("mover.bak"), I will maybe give this a try unless someone else may have better advice or something else I could try. EDIT: Instead of renaming the mover binary, I found the "Mover Tuning" plugin by Squid and used it to disable the mover schedule, we'll see if this sorts me out going forward. Edited April 2, 2023 by syphant Quote Link to comment
JorgeB Posted April 3, 2023 Share Posted April 3, 2023 You can try that but unlikely that the mover, which if I understand correctly is not moving anything, would crash the server. Quote Link to comment
syphant Posted April 3, 2023 Author Share Posted April 3, 2023 12 hours ago, JorgeB said: You can try that but unlikely that the mover, which if I understand correctly is not moving anything, would crash the server. Unlikely yes, but it just seemed odd that the mover job running at 2:00am was the last log message in both cases of the server becoming unreachable, so I'm basically just documenting my troubleshooting process here. That being said, I am open to trying pretty much anything and everything to determine the cause of the issue! Quote Link to comment
syphant Posted April 8, 2023 Author Share Posted April 8, 2023 Server became unresponsive again, unfortunately I don't have a clue where to start with this. Could the below be indicative of a hardware issue, bad RAM maybe? Any pointers on where to start investigating/troubleshooting? 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: general protection fault, probably for non-canonical address 0x55a159d541a22a25: 0000 [#1] PREEMPT SMP PTI 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: CPU: 9 PID: 15390 Comm: python3 Tainted: G W 5.19.17-Unraid #2 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: Hardware name: Gigabyte Technology Co., Ltd. C246-WU4/C246-WU4-CF, BIOS F7 01/18/2022 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: RIP: 0010:nf_nat_setup_info+0x142/0x7b1 [nf_nat] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: Code: 4c 89 f7 e8 2f f8 ff ff 48 8b 15 66 6a 00 00 89 c0 48 8d 04 c2 4c 8b 28 4d 85 ed 74 2a 49 81 ed 90 00 00 00 eb 21 8a 44 24 46 <41> 38 45 46 74 21 49 8b 95 90 00 00 00 48 85 d2 0f 84 53 ff ff ff 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: RSP: 0018:ffffc900002e4730 EFLAGS: 00010202 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: RAX: ffff88818a1c6106 RBX: ffff88810b583e00 RCX: 4854bbdf6d781f1b 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: RDX: 55a159d541a22a6f RSI: 391cd2755cf159ca RDI: 7b8e242ab137fc55 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: RBP: ffffc900002e47f8 R08: ba2c54ffe5116370 R09: f7b326215877c7ec 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: R10: e3f67bd99310ac3b R11: 0e6f874a5de72109 R12: ffffc900002e480c 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: R13: 55a159d541a229df R14: ffffffff82909480 R15: 0000000000000000 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: FS: 000014b165e88b38(0000) GS:ffff88886d440000(0000) knlGS:0000000000000000 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: CR2: 000014b1688f2902 CR3: 0000000118ec2006 CR4: 00000000003706e0 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: Call Trace: 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: <IRQ> 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? krealloc+0x7f/0x90 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: nf_nat_masquerade_ipv4+0x114/0x13c [nf_nat] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: masquerade_tg+0x48/0x66 [xt_MASQUERADE] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ipt_do_table+0x51b/0x5bf [ip_tables] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: nf_nat_inet_fn+0x123/0x1a8 [nf_nat] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: nf_nat_ipv4_out+0x15/0x91 [nf_nat] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: nf_hook_slow+0x3a/0x96 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? __ip_finish_output+0x144/0x144 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: nf_hook+0xdf/0x110 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? ethnl_parse_bit+0xce/0x202 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? __ip_finish_output+0x144/0x144 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ip_output+0x78/0x88 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? __ip_finish_output+0x144/0x144 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ip_sabotage_in+0x47/0x58 [br_netfilter] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: nf_hook_slow+0x3a/0x96 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? ip_rcv_finish_core.constprop.0+0x3b7/0x3b7 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: NF_HOOK.constprop.0+0x79/0xd9 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? ip_rcv_finish_core.constprop.0+0x3b7/0x3b7 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: __netif_receive_skb_one_core+0x77/0x9c 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: netif_receive_skb+0xbf/0x127 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: br_handle_frame_finish+0x476/0x4b0 [bridge] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: br_nf_hook_thresh+0xe2/0x109 [br_netfilter] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: br_nf_pre_routing_finish+0x2c1/0x2ec [br_netfilter] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? NF_HOOK.isra.0+0xe4/0x140 [br_netfilter] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? br_nf_hook_thresh+0x109/0x109 [br_netfilter] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: br_nf_pre_routing+0x226/0x23a [br_netfilter] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? br_nf_hook_thresh+0x109/0x109 [br_netfilter] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: br_handle_frame+0x27c/0x2e7 [bridge] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: __netif_receive_skb_core.constprop.0+0x4f6/0x6e3 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? rcu_is_cpu_rrupt_from_idle+0x11/0x59 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? rcu_sched_clock_irq+0xa53/0xaf7 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: __netif_receive_skb_one_core+0x40/0x9c 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: process_backlog+0x8c/0x116 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: __napi_poll.constprop.0+0x28/0x124 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: net_rx_action+0x159/0x24f 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: __do_softirq+0x126/0x288 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: do_softirq+0x7f/0xab 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: </IRQ> 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: <TASK> 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: __local_bh_enable_ip+0x4c/0x6b 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ip_finish_output2+0x37d/0x3b0 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: __ip_queue_xmit+0x2fd/0x344 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: __tcp_transmit_skb+0x841/0x8b1 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: tcp_connect+0x7e4/0x86f 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: tcp_v4_connect+0x3e3/0x43e 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: __inet_stream_connect+0x110/0x311 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ? percpu_counter_add_batch+0x85/0xa2 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: inet_stream_connect+0x39/0x52 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: __sys_connect+0x68/0xa7 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: __x64_sys_connect+0x14/0x1b 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: do_syscall_64+0x68/0x81 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: RIP: 0033:0x14b16c1c63c1 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: Code: c3 8b 07 85 c0 75 24 49 89 fb 48 89 f0 48 89 d7 48 89 ce 4c 89 c2 4d 89 ca 4c 8b 44 24 08 4c 8b 4c 24 10 4c 89 5c 24 08 0f 05 <c3> e9 6a d1 ff ff 41 54 b8 02 00 00 00 49 89 f4 be 00 88 08 00 55 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: RSP: 002b:000014b165e84728 EFLAGS: 00000246 ORIG_RAX: 000000000000002a 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: RAX: ffffffffffffffda RBX: 000000000000002a RCX: 000014b16c1c63c1 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: RDX: 0000000000000010 RSI: 000014b165e847d0 RDI: 000000000000000a 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: RBP: 000014b165e88b38 R08: 0000000000000000 R09: 0000000000000000 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: R13: 000014b167e3e7f0 R14: 0000000000000010 R15: 000014b16b34f830 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: </TASK> 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: Modules linked in: tcp_diag udp_diag inet_diag tun af_packet tls xt_nat xt_tcpudp veth macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc e1000e igb i915 iosf_mbi drm_buddy ttm drm_display_helper drm_kms_helper drm x86_pkg_temp_thermal intel_powerclamp intel_gtt coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel gigabyte_wmi wmi_bmof intel_wmi_thunderbolt crypto_simd cryptd rapl intel_cstate intel_uncore i2c_i801 agpgart i2c_smbus nvme syscopyarea i2c_algo_bit sysfillrect ahci sysimgblt i2c_core nvme_core libahci intel_pch_thermal fb_sys_fops thermal wmi fan video backlight button acpi_pad unix [last unloaded: e1000e] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: ---[ end trace 0000000000000000 ]--- 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: RIP: 0010:nf_nat_setup_info+0x142/0x7b1 [nf_nat] 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: Code: 4c 89 f7 e8 2f f8 ff ff 48 8b 15 66 6a 00 00 89 c0 48 8d 04 c2 4c 8b 28 4d 85 ed 74 2a 49 81 ed 90 00 00 00 eb 21 8a 44 24 46 <41> 38 45 46 74 21 49 8b 95 90 00 00 00 48 85 d2 0f 84 53 ff ff ff 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: RSP: 0018:ffffc900002e4730 EFLAGS: 00010202 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: RAX: ffff88818a1c6106 RBX: ffff88810b583e00 RCX: 4854bbdf6d781f1b 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: RDX: 55a159d541a22a6f RSI: 391cd2755cf159ca RDI: 7b8e242ab137fc55 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: RBP: ffffc900002e47f8 R08: ba2c54ffe5116370 R09: f7b326215877c7ec 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: R10: e3f67bd99310ac3b R11: 0e6f874a5de72109 R12: ffffc900002e480c 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: R13: 55a159d541a229df R14: ffffffff82909480 R15: 0000000000000000 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: FS: 000014b165e88b38(0000) GS:ffff88886d440000(0000) knlGS:0000000000000000 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: CR2: 000014b1688f2902 CR3: 0000000118ec2006 CR4: 00000000003706e0 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 2023-04-07 23:01:04 Kernel.Warning 192.168.0.2 Apr 7 23:01:05 acidbath kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Quote Link to comment
JorgeB Posted April 8, 2023 Share Posted April 8, 2023 Try switching to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)) Quote Link to comment
syphant Posted April 8, 2023 Author Share Posted April 8, 2023 Hey Jorge, just now changed this as advised, will report back after some time, thanks! 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.