Patb

yes, that is correct. I can't connect to http://192.168.2.242:8080/vnc.html?autoconnect=true here is the advanced configuration

I'm still trying to make this work without any success. I decided to try to make it work with Chromium just to try to get it working and then I would go from there. Here is my configuration for Chromium I've been trying for days to get this resolved and I can't understand what I'm doing wrong.

I am trying to get OpenVPN-Client working and I can't seem to get the port passthrough to work. As can be seen, I am not using the default port for SABnzbd (8081 vs 8080). When I make the changes to pass it through it seems to no longer take my port mapping into account and seems to use the defaults (notice 8080 instead of 8081 below) even though I didn't change the port when I changed the network type. Any advice or assistance would be appreciated. Thanks

I love how expandable the platform is and the ability to deploy so much functionality. I would like to see the ability to support more than 30 hard drives in multiple arrays in 2020.

Updated Plex docker last night to Version 1.16.4.1469 and the problem seems to have gone away.

My docker file got corrupted and I had to rebuild it. I am still receiving the series of "error: /gcsp/2.0: missing csrf_token" errors when my dockers restart following my nightly backups but after 2 days I seem to not be receiving the BTRFS warnings anymore ("WARNING: CPU: 3 PID: 16918 at fs/btrfs/root-tree.c:377 btrfs_del_root_ref+0x10f/0x1b1"). Anybody have any ideas what could still be causing the missing csrf_token errors? As stated above, Enable server support for IPv6 in Plex is not checked.

Sorry, I missed that question. It wasn't full but I nevertheless increased the size to 30G. I will monitor it more closely. I am presently at 30% usage.

Yes I did. I read about it when I searched how to recreate the docker image. Thanks

ok, I'm trying that. I've deleted it and recreated it. I am now adding the apps back. My docker is back up. Thanks

My server froze last night and l had to do a reboot. The docker service fails to start after reboot and I have what appear to be BTRFS errors. My cache used to be set to BTRFS but I changes it to XFS not too long ago after I had a crash that I couldn't recover from. I don't understand the BTRFS errors when I don't have a BTRFS formatted drive. I am attaching the log since the previous restart and my diagnostics. Help The first error appears to be: Aug 5 02:41:41 Tower kernel: WARNING: CPU: 12 PID: 8042 at fs/btrfs/ctree.c:3611 leaf_space_used+0xc6/0xef Aug 5 02:41:41 Tower kernel: Modules linked in: iptable_mangle tun macvlan xt_nat veth ipt_MASQUERADE iptable_nat nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs nfsd lockd grace sunrpc md_mod bonding bnx2x mdio igb i2c_algo_bit sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 ipmi_ssif crypto_simd cryptd glue_helper intel_cstate mpt3sas intel_uncore intel_rapl_perf i2c_i801 i2c_core raid_class wmi ipmi_si scsi_transport_sas button pcc_cpufreq [last unloaded: mdio] Aug 5 02:41:41 Tower kernel: CPU: 12 PID: 8042 Comm: btrfs-transacti Tainted: G W 4.19.56-Unraid #1 Aug 5 02:41:41 Tower kernel: Hardware name: IBM System x3630 M4 -[7158AC1]-/00KF924, BIOS -[BEE166CUS-3.10]- 08/29/2018 Aug 5 02:41:41 Tower kernel: RIP: 0010:leaf_space_used+0xc6/0xef Aug 5 02:41:41 Tower kernel: Code: 41 01 c4 44 39 fb 48 89 e1 0f 4e f3 45 6b ed 19 ff ce 48 63 f6 45 01 e5 48 6b f6 19 48 83 c6 65 e8 6b b8 03 00 41 29 c5 79 02 <0f> 0b 48 8b 4c 24 18 65 48 33 0c 25 28 00 00 00 44 89 e8 74 05 e8 Aug 5 02:41:41 Tower kernel: RSP: 0018:ffffc900074ffc00 EFLAGS: 00010283 Aug 5 02:41:41 Tower kernel: RAX: 0000000000778d42 RBX: 00000000000000c7 RCX: ffff888ae609a000 Aug 5 02:41:41 Tower kernel: RDX: 0000000000001000 RSI: 000000016b204000 RDI: 0000000000000000 Aug 5 02:41:41 Tower kernel: RBP: ffff88814ba33a40 R08: ffffc900074ffbb8 R09: ffffc900074ffbc0 Aug 5 02:41:41 Tower kernel: R10: 0000000000000000 R11: 0000000000001000 R12: 0000000000003f9b Aug 5 02:41:41 Tower kernel: R13: 00000000ff88c5c8 R14: 0000000000000065 R15: 00000000000000c7 Aug 5 02:41:41 Tower kernel: FS: 0000000000000000(0000) GS:ffff888667980000(0000) knlGS:0000000000000000 Aug 5 02:41:41 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Aug 5 02:41:41 Tower kernel: CR2: 00001463c3c808e8 CR3: 0000000001e0a006 CR4: 00000000000606e0 Aug 5 02:41:41 Tower kernel: Call Trace: Aug 5 02:41:41 Tower kernel: btrfs_leaf_free_space+0x48/0x82 Aug 5 02:41:41 Tower kernel: btrfs_search_slot+0x64d/0x832 Aug 5 02:41:41 Tower kernel: btrfs_insert_empty_items+0x4e/0x91 Aug 5 02:41:41 Tower kernel: __btrfs_run_delayed_refs+0x7c3/0xb96 Aug 5 02:41:41 Tower kernel: ? __switch_to_asm+0x35/0x70 Aug 5 02:41:41 Tower kernel: btrfs_run_delayed_refs+0x5a/0x15c Aug 5 02:41:41 Tower kernel: ? try_to_del_timer_sync+0x4f/0x6e Aug 5 02:41:41 Tower kernel: btrfs_commit_transaction+0x50/0x76b Aug 5 02:41:41 Tower kernel: ? start_transaction+0x29e/0x30e Aug 5 02:41:41 Tower kernel: transaction_kthread+0xca/0x136 Aug 5 02:41:41 Tower kernel: ? btrfs_cleanup_transaction+0x4a1/0x4a1 Aug 5 02:41:41 Tower kernel: kthread+0x10b/0x113 Aug 5 02:41:41 Tower kernel: ? kthread_park+0x71/0x71 Aug 5 02:41:41 Tower kernel: ret_from_fork+0x35/0x40 Aug 5 02:41:41 Tower kernel: ---[ end trace 1e3060d86793bb3c ]--- Aug 5 02:41:41 Tower kernel: WARNING: CPU: 12 PID: 8042 at fs/btrfs/ctree.c:3611 leaf_space_used+0xc6/0xef Aug 5 02:41:41 Tower kernel: Modules linked in: iptable_mangle tun macvlan xt_nat veth ipt_MASQUERADE iptable_nat nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs nfsd lockd grace sunrpc md_mod bonding bnx2x mdio igb i2c_algo_bit sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 ipmi_ssif crypto_simd cryptd glue_helper intel_cstate mpt3sas intel_uncore intel_rapl_perf i2c_i801 i2c_core raid_class wmi ipmi_si scsi_transport_sas button pcc_cpufreq [last unloaded: mdio] Aug 5 02:41:41 Tower kernel: CPU: 12 PID: 8042 Comm: btrfs-transacti Tainted: G W 4.19.56-Unraid #1 Aug 5 02:41:41 Tower kernel: Hardware name: IBM System x3630 M4 -[7158AC1]-/00KF924, BIOS -[BEE166CUS-3.10]- 08/29/2018 Aug 5 02:41:41 Tower kernel: RIP: 0010:leaf_space_used+0xc6/0xef Aug 5 02:41:41 Tower kernel: Code: 41 01 c4 44 39 fb 48 89 e1 0f 4e f3 45 6b ed 19 ff ce 48 63 f6 45 01 e5 48 6b f6 19 48 83 c6 65 e8 6b b8 03 00 41 29 c5 79 02 <0f> 0b 48 8b 4c 24 18 65 48 33 0c 25 28 00 00 00 44 89 e8 74 05 e8 Aug 5 02:41:41 Tower kernel: RSP: 0018:ffffc900074ffbf8 EFLAGS: 00010283 Aug 5 02:41:41 Tower kernel: RAX: 0000000000778d42 RBX: 00000000000000c7 RCX: ffff888ae609a000 Aug 5 02:41:41 Tower kernel: RDX: 0000000000001000 RSI: 000000016b204000 RDI: 0000000000000000 Aug 5 02:41:41 Tower kernel: RBP: ffff88814ba33a40 R08: ffffc900074ffbb0 R09: ffffc900074ffbb8 Aug 5 02:41:41 Tower kernel: R10: 0000000000000000 R11: 0000000000001000 R12: 0000000000003f9b Aug 5 02:41:41 Tower kernel: R13: 00000000ff88c5c8 R14: 0000000000000065 R15: 00000000000000c7 Aug 5 02:41:41 Tower kernel: FS: 0000000000000000(0000) GS:ffff888667980000(0000) knlGS:0000000000000000 Aug 5 02:41:41 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Aug 5 02:41:41 Tower kernel: CR2: 00001463c3c808e8 CR3: 0000000001e0a006 CR4: 00000000000606e0 Aug 5 02:41:41 Tower kernel: Call Trace: Aug 5 02:41:41 Tower kernel: btrfs_leaf_free_space+0x48/0x82 Aug 5 02:41:41 Tower kernel: setup_items_for_insert+0xf4/0x352 Aug 5 02:41:41 Tower kernel: btrfs_insert_empty_items+0x7b/0x91 Aug 5 02:41:41 Tower kernel: __btrfs_run_delayed_refs+0x7c3/0xb96 Aug 5 02:41:41 Tower kernel: ? __switch_to_asm+0x35/0x70 Aug 5 02:41:41 Tower kernel: btrfs_run_delayed_refs+0x5a/0x15c Aug 5 02:41:41 Tower kernel: ? try_to_del_timer_sync+0x4f/0x6e Aug 5 02:41:41 Tower kernel: btrfs_commit_transaction+0x50/0x76b Aug 5 02:41:41 Tower kernel: ? start_transaction+0x29e/0x30e Aug 5 02:41:41 Tower kernel: transaction_kthread+0xca/0x136 Aug 5 02:41:41 Tower kernel: ? btrfs_cleanup_transaction+0x4a1/0x4a1 Aug 5 02:41:41 Tower kernel: kthread+0x10b/0x113 Aug 5 02:41:41 Tower kernel: ? kthread_park+0x71/0x71 Aug 5 02:41:41 Tower kernel: ret_from_fork+0x35/0x40 Aug 5 02:41:41 Tower kernel: ---[ end trace 1e3060d86793bb3d ]--- and then I get a series of these: Aug 5 02:41:41 Tower kernel: BTRFS info (device loop2): leaf 6092242944 gen 60401 total ptrs 199 free space 7829971 owner 2 Aug 5 02:41:41 Tower kernel: item 0 key (6089441280 169 0) itemoff 16223 itemsize 60 Aug 5 02:41:41 Tower kernel: extent refs 4 gen 10446 flags 2 Aug 5 02:41:41 Tower kernel: ref#0: tree block backref root 462 Aug 5 02:41:41 Tower kernel: ref#1: tree block backref root 461 Aug 5 02:41:41 Tower kernel: ref#2: tree block backref root 460 Aug 5 02:41:41 Tower kernel: ref#3: tree block backref root 458 Aug 5 02:41:41 Tower kernel: item 1 key (6089457664 169 0) itemoff 16100 itemsize 123 Aug 5 02:41:41 Tower kernel: extent refs 11 gen 10446 flags 2 Aug 5 02:41:41 Tower kernel: ref#0: tree block backref root 469 Aug 5 02:41:41 Tower kernel: ref#1: tree block backref root 468 Aug 5 02:41:41 Tower kernel: ref#2: tree block backref root 467 Aug 5 02:41:41 Tower kernel: ref#3: tree block backref root 466 Aug 5 02:41:41 Tower kernel: ref#4: tree block backref root 465 Aug 5 02:41:41 Tower kernel: ref#5: tree block backref root 464 Aug 5 02:41:41 Tower kernel: ref#6: tree block backref root 463 Aug 5 02:41:41 Tower kernel: ref#7: tree block backref root 462 Aug 5 02:41:41 Tower kernel: ref#8: tree block backref root 461 Aug 5 02:41:41 Tower kernel: ref#9: tree block backref root 460 Aug 5 02:41:41 Tower kernel: ref#10: tree block backref root 458 And then when I reboot I can't start docker and I get the following in the log: Aug 5 07:40:04 Tower kernel: BTRFS: device fsid ba577f11-99fc-487e-a96e-aed9e181a702 devid 1 transid 60400 /dev/loop2 Aug 5 07:40:04 Tower kernel: BTRFS info (device loop2): disk space caching is enabled Aug 5 07:40:04 Tower kernel: BTRFS info (device loop2): has skinny extents Aug 5 07:40:05 Tower kernel: BTRFS critical (device loop2): corrupt leaf: root=2 block=6073548800 slot=131, unexpected item end, have 1810063561 expect 10088 Aug 5 07:40:05 Tower kernel: BTRFS critical (device loop2): corrupt leaf: root=2 block=6073548800 slot=131, unexpected item end, have 1810063561 expect 10088 Aug 5 07:40:05 Tower kernel: BTRFS critical (device loop2): corrupt leaf: root=2 block=6073548800 slot=131, unexpected item end, have 1810063561 expect 10088 Aug 5 07:40:05 Tower kernel: BTRFS: error (device loop2) in __btrfs_free_extent:6803: errno=-5 IO failure Aug 5 07:40:05 Tower kernel: BTRFS: error (device loop2) in btrfs_run_delayed_refs:2935: errno=-5 IO failure Aug 5 07:40:05 Tower kernel: BTRFS: error (device loop2) in btrfs_replay_log:2282: errno=-5 IO failure (Failed to recover log tree) Aug 5 07:40:05 Tower kernel: BTRFS error (device loop2): pending csums is 69632 Aug 5 07:40:05 Tower root: mount: /var/lib/docker: can't read superblock on /dev/loop2. Aug 5 07:40:05 Tower kernel: BTRFS error (device loop2): open_ctree failed Aug 5 07:40:05 Tower root: mount error Aug 5 07:40:05 Tower emhttpd: shcmd (85): exit status: 1 Aug 5 07:40:05 Tower kernel: mdcmd (41): check nocorrect Aug 5 07:40:05 Tower kernel: md: recovery thread: check Q ... Aug 5 07:40:05 Tower kernel: md: using 8192k window, over a total of 9766436812 blocks. Aug 5 07:40:07 Tower unassigned.devices: Mounting 'Auto Mount' Remote Shares... Aug 5 07:40:11 Tower unassigned.devices: Remote SMB mount '192.168.2.207://volume1/Various' is not set to auto mount and will not be mounted... Aug 5 07:40:11 Tower unassigned.devices: Remote SMB mount '192.168.2.206://volume1/photo' is not set to auto mount and will not be mounted... Aug 5 07:40:11 Tower unassigned.devices: Remote SMB mount '192.168.2.206://volume1/video' is not set to auto mount and will not be mounted... Aug 5 07:40:11 Tower unassigned.devices: Remote SMB mount '192.168.2.206://volume1/music' is not set to auto mount and will not be mounted... Aug 5 07:40:11 Tower unassigned.devices: Remote SMB mount '192.168.2.207://volume1/Backup' is not set to auto mount and will not be mounted... Aug 5 07:40:11 Tower unassigned.devices: Remote SMB mount '192.168.2.206://volume1/homes' is not set to auto mount and will not be mounted... Aug 5 07:40:18 Tower nginx: 2019/08/05 07:40:18 [error] 5948#5948: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen. Aug 5 07:40:18 Tower nginx: 2019/08/05 07:40:18 [error] 5948#5948: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen. Aug 5 07:40:18 Tower nginx: 2019/08/05 07:40:18 [error] 5948#5948: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen. syslog paired down.txt tower-diagnostics-20190805-1215.zip

Enable server support for IPv6 is not checked and has been for weeks. I decided to remove some plugins and that seems to have calmed things down (at least so far). Spoke too soon.... it's back

I read and posted to topic: [SOLVED] root: error: /gcsp/2.0: missing csrf_token and my problem is still not resolved so I decided to start a new topic. My network settings are already set to "IPv4 only" and I get the following error approximately 1000 times in 2 to 3 seconds Tower root: error: /gcsp/2.0: missing csrf_token I am also getting these messages in my log that seem to make reference to IPv6 when restarting dockers. I wonder if this is related given the reference to IPv6 Aug 3 19:31:29 Tower kernel: eth0: renamed from veth0ebee7b Aug 3 19:31:29 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethdda6428: link becomes ready Aug 3 19:31:29 Tower kernel: docker0: port 2(vethdda6428) entered blocking state Aug 3 19:31:29 Tower kernel: docker0: port 2(vethdda6428) entered forwarding state Just to add to what's happening I also got the following warning and error Aug 3 19:37:41 Tower kernel: WARNING: CPU: 3 PID: 16918 at fs/btrfs/root-tree.c:377 btrfs_del_root_ref+0x10f/0x1b1 Aug 3 19:37:41 Tower kernel: Modules linked in: iptable_mangle tun macvlan xt_nat veth ipt_MASQUERADE iptable_nat nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs nfsd lockd grace sunrpc md_mod bonding bnx2x mdio igb i2c_algo_bit sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd ipmi_ssif glue_helper intel_cstate mpt3sas intel_uncore i2c_i801 i2c_core wmi intel_rapl_perf pcc_cpufreq raid_class scsi_transport_sas button ipmi_si [last unloaded: mdio] Aug 3 19:37:41 Tower kernel: CPU: 3 PID: 16918 Comm: dockerd Not tainted 4.19.56-Unraid #1 Aug 3 19:37:41 Tower kernel: Hardware name: IBM System x3630 M4 -[7158AC1]-/00KF924, BIOS -[BEE166CUS-3.10]- 08/29/2018 Aug 3 19:37:41 Tower kernel: RIP: 0010:btrfs_del_root_ref+0x10f/0x1b1 Aug 3 19:37:41 Tower kernel: Code: b7 c0 3b 84 24 80 00 00 00 74 02 0f 0b 48 63 8c 24 80 00 00 00 48 8d 55 12 4c 89 e7 48 8b 74 24 20 e8 9a be 02 00 85 c0 74 02 <0f> 0b 31 c9 ba 08 00 00 00 48 89 ee 4c 89 e7 e8 02 35 02 00 48 8b Aug 3 19:37:41 Tower kernel: RSP: 0018:ffffc900224d7b60 EFLAGS: 00010202 Aug 3 19:37:41 Tower kernel: RAX: 000000000000000b RBX: ffff88844a901e70 RCX: 000000000000000e Aug 3 19:37:41 Tower kernel: RDX: 0000000000000045 RSI: ffff88859b35ebae RDI: ffff88861af04a90 Aug 3 19:37:41 Tower kernel: RBP: 0000000000002b9c R08: 0000000000000058 R09: ffffc900224d7b20 Aug 3 19:37:41 Tower kernel: R10: 0000000000000000 R11: 0000000000002000 R12: ffff88863a637810 Aug 3 19:37:41 Tower kernel: R13: 0000000000000000 R14: ffff88864f07ba90 R15: 000000000000026d Aug 3 19:37:41 Tower kernel: FS: 0000153c821f0700(0000) GS:ffff8886678c0000(0000) knlGS:0000000000000000 Aug 3 19:37:41 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Aug 3 19:37:41 Tower kernel: CR2: 0000153c908abb08 CR3: 0000000631ef6004 CR4: 00000000000606e0 Aug 3 19:37:41 Tower kernel: Call Trace: Aug 3 19:37:41 Tower kernel: btrfs_unlink_subvol+0x14d/0x34c Aug 3 19:37:41 Tower kernel: btrfs_delete_subvolume+0x15e/0x538 Aug 3 19:37:41 Tower kernel: btrfs_ioctl_snap_destroy+0x24c/0x2a9 Aug 3 19:37:41 Tower kernel: btrfs_ioctl+0x54b/0x28ad Aug 3 19:37:41 Tower kernel: ? kmem_cache_alloc+0xe7/0xf3 Aug 3 19:37:41 Tower kernel: ? _copy_to_user+0x22/0x28 Aug 3 19:37:41 Tower kernel: ? cp_new_stat+0x14b/0x17a Aug 3 19:37:41 Tower kernel: ? vfs_ioctl+0x19/0x26 Aug 3 19:37:41 Tower kernel: vfs_ioctl+0x19/0x26 Aug 3 19:37:41 Tower kernel: do_vfs_ioctl+0x526/0x54e Aug 3 19:37:41 Tower kernel: ? __se_sys_newlstat+0x48/0x6b Aug 3 19:37:41 Tower kernel: ksys_ioctl+0x39/0x58 Aug 3 19:37:41 Tower kernel: __x64_sys_ioctl+0x11/0x14 Aug 3 19:37:41 Tower kernel: do_syscall_64+0x57/0xf2 Aug 3 19:37:41 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Aug 3 19:37:41 Tower kernel: RIP: 0033:0x4b6570 Aug 3 19:37:41 Tower kernel: Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 Aug 3 19:37:41 Tower kernel: RSP: 002b:000000c421f7c018 EFLAGS: 00000212 ORIG_RAX: 0000000000000010 Aug 3 19:37:41 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00000000004b6570 Aug 3 19:37:41 Tower kernel: RDX: 000000c421f7c088 RSI: 000000005000940f RDI: 000000000000005c Aug 3 19:37:41 Tower kernel: RBP: 000000c421f7d238 R08: 0000000000000000 R09: 0000000000000000 Aug 3 19:37:41 Tower kernel: R10: 0000000000000000 R11: 0000000000000212 R12: ffffffffffffffff Aug 3 19:37:41 Tower kernel: R13: 000000000000001e R14: 000000000000001d R15: 0000000000000040 Aug 3 19:37:41 Tower kernel: ---[ end trace f2cfdcac4249d4fb ]--- Aug 3 19:37:43 Tower kernel: br-0084f414a875: port 12(vethfef8dfa) entered blocking state Aug 3 19:37:43 Tower kernel: br-0084f414a875: port 12(vethfef8dfa) entered disabled state Aug 3 19:37:43 Tower kernel: device vethfef8dfa entered promiscuous mode Aug 3 19:37:43 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): vethfef8dfa: link is not ready Aug 3 19:37:45 Tower kernel: eth0: renamed from vethff483b1 Aug 3 19:37:45 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfef8dfa: link becomes ready Aug 3 19:37:45 Tower kernel: br-0084f414a875: port 12(vethfef8dfa) entered blocking state Aug 3 19:37:45 Tower kernel: br-0084f414a875: port 12(vethfef8dfa) entered forwarding state I figure it's wise to attach a diagnostic tower-diagnostics-20190803-2350.zip

So I can now confirm that eth0 is "IPv4 Only" and that the other interfaces are set to the same because of the bond (40:F2:E9:6C:65:50 - Interface is member of bond0 (see interface eth0)). The following is also logged immediately following the errors which I don't understand, especially the references to IPv6 Jul 24 08:13:51 Tower kernel: br-0084f414a875: port 11(vethfadb862) entered blocking state Jul 24 08:13:51 Tower kernel: br-0084f414a875: port 11(vethfadb862) entered disabled state Jul 24 08:13:51 Tower kernel: device vethfadb862 entered promiscuous mode Jul 24 08:13:51 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): vethfadb862: link is not ready Jul 24 08:13:51 Tower kernel: br-0084f414a875: port 11(vethfadb862) entered blocking state Jul 24 08:13:51 Tower kernel: br-0084f414a875: port 11(vethfadb862) entered forwarding state Jul 24 08:13:51 Tower kernel: br-0084f414a875: port 11(vethfadb862) entered disabled state Jul 24 08:13:55 Tower kernel: eth0: renamed from vethdee8524 Jul 24 08:13:55 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfadb862: link becomes ready Jul 24 08:13:55 Tower kernel: br-0084f414a875: port 11(vethfadb862) entered blocking state Jul 24 08:13:55 Tower kernel: br-0084f414a875: port 11(vethfadb862) entered forwarding state Jul 24 08:13:56 Tower rc.docker: nextcloud: started succesfully! Jul 24 08:13:56 Tower kernel: docker0: port 5(veth66af27c) entered blocking state Jul 24 08:13:56 Tower kernel: docker0: port 5(veth66af27c) entered disabled state Jul 24 08:13:56 Tower kernel: device veth66af27c entered promiscuous mode Jul 24 08:13:56 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): veth66af27c: link is not ready Jul 24 08:13:56 Tower kernel: docker0: port 5(veth66af27c) entered blocking state Jul 24 08:13:56 Tower kernel: docker0: port 5(veth66af27c) entered forwarding state Jul 24 08:13:56 Tower kernel: docker0: port 5(veth66af27c) entered disabled state Jul 24 08:14:00 Tower kernel: eth0: renamed from veth10ad285 Jul 24 08:14:00 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth66af27c: link becomes ready Jul 24 08:14:00 Tower kernel: docker0: port 5(veth66af27c) entered blocking state Jul 24 08:14:00 Tower kernel: docker0: port 5(veth66af27c) entered forwarding state Jul 24 08:14:01 Tower rc.docker: kodi-headless: started succesfully!

I'll check again when I get home but when I looked at it last (this morning) it was set to "IPv4 Only" but I did not check the individual interfaces (I have one ethernet and two fiber ports).

rereading my post I see that I may have had a confusing use of the terms checked and unchecked. When I said I checked the setting I meant that I looked to see its status. It was already unchecked and I left it that way. So yes, the "Enable server support for IPv6" in NOT checked in Plex. My ISP doesn't support IPv6 so I don't use it. Thanks

I'm getting the same error but I checked my Plex settings and I already have "Enable server support for IPv6" unchecked in Plex. Also the error repeats approximately 1000 times in the span of 2 seconds when it occurs. Jul 24 08:13:51 Tower root: error: /gcsp/2.0: missing csrf_token Any help would be greatly appreciated.

ok, this is strange, I renamed the container to bitwarden (lower case b) and it now works... Thanks

They are both in a network called "proxynet" and I verified that the names match. Still no success.

Follow up to my post from yesterday. Still getting a 502 Bad Gateway for Bitwarden. I forced update on both Letsencrypt and Bitwarden and still nothing. I am able to connect by using the IP address (in my case: http://192.168.2.242:8343/#/) but this is of limited value as I need to be able to connect to bitwarden remotely. I tried to change the bitwarden in the configuration file to upper case B with no change. Below is the conf I'm using for Bitwarden, I have no problems with any other servers at this time. # make sure that your dns has a cname set for bitwarden and that your bitwarden container is not using a base url server { listen 443 ssl; listen [::]:443 ssl; server_name bitwarden.*; include /config/nginx/ssl.conf; client_max_body_size 128M; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_bitwarden bitwarden; proxy_pass http://$upstream_bitwarden:80; } location /notifications/hub { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_bitwarden bitwarden; proxy_pass http://$upstream_bitwarden:80; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; } location /notifications/hub/negotiate { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_bitwarden bitwarden; proxy_pass http://$upstream_bitwarden:80; } } As stated above, I continue to get the following errors when I try to connect 2019/07/18 22:25:47 [error] 380#380: *1 bitwarden could not be resolved (3: Host not found), client: 192.168.2.1, server: bitwarden.*, request: "GET /favicon.ico HTTP/2.0", host: "bitwarden.XXX.com", referrer: "https://bitwarden.XXX.com/"

I'm starting to loose my mind. I had this working before but my unraid BTRFS cache drive was corrupted and I'm not able to get my bitwarden working with letsencrypt anymore. I'm using the default configuration in letsencrypt and I didn't do anything special with Bitwarden but I keep getting 502 Bad Gateway. I get the following error in the nginx error.log 2019/07/17 22:00:59 [error] 371#371: *2 bitwarden could not be resolved (3: Host not found), client: 192.168.2.1, server: bitwarden.*, request: "GET /favicon.ico HTTP/2.0", host: "bitwarden.xxx.com", referrer: "https://bitwarden.xxx.com/" I have both letsencrypt and bitwarden on the same network "proxynet". I have other services like NextCloud and phpmyadmin set up and working correctly but I can't seem to get bitwarden to work anymore. Thanks.

I've tested the memory a couple of times and it always passes but will try again... not sure what's happening. Woke up this morning and server crashed again and cache drive (BTRFS) is corrupt. I swapped all the memory in that server and have reformatted my cache to XFS and am now in the process of restoring my appdata from backup. This is not a good day This is the last log entry before I noticed the crash in the morning (full log attached) Jul 6 21:15:30 Tower kernel: WARNING: CPU: 4 PID: 0 at net/netfilter/nf_nat_core.c:420 nf_nat_setup_info+0x6b/0x5fb [nf_nat] Jul 6 21:15:30 Tower kernel: Modules linked in: macvlan xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle xt_nat ip6table_filter ip6_tables vhost_net tun vhost tap veth ipt_MASQUERADE iptable_nat nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs nfsd lockd grace sunrpc md_mod bonding bnx2x mdio igb i2c_algo_bit sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd ipmi_ssif glue_helper mpt3sas intel_cstate wmi i2c_i801 intel_uncore i2c_core intel_rapl_perf raid_class pcc_cpufreq ipmi_si scsi_transport_sas button [last unloaded: mdio] Jul 6 21:15:30 Tower kernel: CPU: 4 PID: 0 Comm: swapper/4 Tainted: G W 4.19.56-Unraid #1 Jul 6 21:15:30 Tower kernel: Hardware name: IBM System x3630 M4 -[7158AC1]-/00KF924, BIOS -[BEE166CUS-3.10]- 08/29/2018 Jul 6 21:15:30 Tower kernel: RIP: 0010:nf_nat_setup_info+0x6b/0x5fb [nf_nat] Jul 6 21:15:30 Tower kernel: Code: 48 89 fb 48 8b 87 80 00 00 00 49 89 f7 41 89 d6 76 04 0f 0b eb 0b 85 d2 75 07 25 80 00 00 00 eb 05 25 00 01 00 00 85 c0 74 07 <0f> 0b e9 ac 04 00 00 48 8b 83 90 00 00 00 4c 8d 64 24 30 48 8d 73 Jul 6 21:15:30 Tower kernel: RSP: 0018:ffff8886679037b0 EFLAGS: 00010202 Jul 6 21:15:30 Tower kernel: RAX: 0000000000000080 RBX: ffff88810e868dc0 RCX: 0000000000000000 Jul 6 21:15:30 Tower kernel: RDX: 0000000000000000 RSI: ffff88866790389c RDI: ffff88810e868dc0 Jul 6 21:15:30 Tower kernel: RBP: ffff888667903888 R08: ffff88810e868dc0 R09: 0000000000000000 Jul 6 21:15:30 Tower kernel: R10: 0000000000000158 R11: ffffffff81e8e001 R12: ffff8883f98ec800 Jul 6 21:15:30 Tower kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffff88866790389c Jul 6 21:15:30 Tower kernel: FS: 0000000000000000(0000) GS:ffff888667900000(0000) knlGS:0000000000000000 Jul 6 21:15:30 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 6 21:15:30 Tower kernel: CR2: 00001506159a4480 CR3: 0000000001e0a003 CR4: 00000000000606e0 Jul 6 21:15:30 Tower kernel: Call Trace: Jul 6 21:15:30 Tower kernel: <IRQ> Jul 6 21:15:30 Tower kernel: ? ipt_do_table+0x58e/0x5db [ip_tables] Jul 6 21:15:30 Tower kernel: nf_nat_alloc_null_binding+0x6f/0x86 [nf_nat] Jul 6 21:15:30 Tower kernel: nf_nat_inet_fn+0xa0/0x192 [nf_nat] Jul 6 21:15:30 Tower kernel: nf_hook_slow+0x37/0x96 Jul 6 21:15:30 Tower kernel: ip_local_deliver+0xa9/0xd7 Jul 6 21:15:30 Tower kernel: ? ip_sublist_rcv_finish+0x53/0x53 Jul 6 21:15:30 Tower kernel: ip_sabotage_in+0x38/0x3e Jul 6 21:15:30 Tower kernel: nf_hook_slow+0x37/0x96 Jul 6 21:15:30 Tower kernel: ip_rcv+0x8e/0xbe Jul 6 21:15:30 Tower kernel: ? ip_rcv_finish_core.isra.0+0x2e2/0x2e2 Jul 6 21:15:30 Tower kernel: __netif_receive_skb_one_core+0x4d/0x69 Jul 6 21:15:30 Tower kernel: netif_receive_skb_internal+0x9f/0xba Jul 6 21:15:30 Tower kernel: br_pass_frame_up+0x123/0x145 Jul 6 21:15:30 Tower kernel: ? br_port_flags_change+0x29/0x29 Jul 6 21:15:30 Tower kernel: br_handle_frame_finish+0x330/0x375 Jul 6 21:15:30 Tower kernel: ? ipt_do_table+0x58e/0x5db [ip_tables] Jul 6 21:15:30 Tower kernel: ? br_pass_frame_up+0x145/0x145 Jul 6 21:15:30 Tower kernel: br_nf_hook_thresh+0xa3/0xc3 Jul 6 21:15:30 Tower kernel: ? br_pass_frame_up+0x145/0x145 Jul 6 21:15:30 Tower kernel: br_nf_pre_routing_finish+0x239/0x260 Jul 6 21:15:30 Tower kernel: ? br_pass_frame_up+0x145/0x145 Jul 6 21:15:30 Tower kernel: ? nf_nat_ipv4_in+0x1d/0x64 [nf_nat_ipv4] Jul 6 21:15:30 Tower kernel: br_nf_pre_routing+0x2fc/0x321 Jul 6 21:15:30 Tower kernel: ? br_nf_forward_ip+0x352/0x352 Jul 6 21:15:30 Tower kernel: nf_hook_slow+0x37/0x96 Jul 6 21:15:30 Tower kernel: br_handle_frame+0x290/0x2d3 Jul 6 21:15:30 Tower kernel: ? br_pass_frame_up+0x145/0x145 Jul 6 21:15:30 Tower kernel: ? br_handle_local_finish+0xe/0xe Jul 6 21:15:30 Tower kernel: __netif_receive_skb_core+0x466/0x798 Jul 6 21:15:30 Tower kernel: ? udp_gro_receive+0x4c/0x134 Jul 6 21:15:30 Tower kernel: __netif_receive_skb_one_core+0x31/0x69 Jul 6 21:15:30 Tower kernel: netif_receive_skb_internal+0x9f/0xba Jul 6 21:15:30 Tower kernel: napi_gro_receive+0x42/0x76 Jul 6 21:15:30 Tower kernel: bnx2x_poll+0x101f/0x1527 [bnx2x] Jul 6 21:15:30 Tower kernel: ? recalibrate_cpu_khz+0x1/0x1 Jul 6 21:15:30 Tower kernel: ? ktime_get+0x3a/0x8d Jul 6 21:15:30 Tower kernel: ? tsc_refine_calibration_work+0x2d/0x225 Jul 6 21:15:30 Tower kernel: ? irq_entries_start+0x29a/0x660 Jul 6 21:15:30 Tower kernel: net_rx_action+0x10b/0x274 Jul 6 21:15:30 Tower kernel: __do_softirq+0xce/0x1e2 Jul 6 21:15:30 Tower kernel: irq_exit+0x5e/0x9d Jul 6 21:15:30 Tower kernel: do_IRQ+0xa9/0xc7 Jul 6 21:15:30 Tower kernel: common_interrupt+0xf/0xf Jul 6 21:15:30 Tower kernel: </IRQ> Jul 6 21:15:30 Tower kernel: RIP: 0010:cpuidle_enter_state+0xe5/0x141 Jul 6 21:15:30 Tower kernel: Code: 97 7e ba ff 45 84 ff 74 1d 9c 58 66 66 90 66 90 0f ba e0 09 73 09 0f 0b fa 66 66 90 66 66 90 31 ff e8 ae 0c be ff fb 66 66 90 <66> 66 90 48 2b 1c 24 b8 ff ff ff 7f 48 b9 ff ff ff ff f3 01 00 00 Jul 6 21:15:30 Tower kernel: RSP: 0018:ffffc900062f7ea0 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffdc Jul 6 21:15:30 Tower kernel: RAX: ffff888667920b00 RBX: 00017ffcf6cd2949 RCX: 000000000000001f Jul 6 21:15:30 Tower kernel: RDX: 00017ffcf6cd2949 RSI: 00000000435e532a RDI: 0000000000000000 Jul 6 21:15:30 Tower kernel: RBP: ffff88866792b600 R08: 0000000000000002 R09: 00000000000203c0 Jul 6 21:15:30 Tower kernel: R10: 0000000185276e44 R11: 00048c26e6f75a54 R12: 0000000000000005 Jul 6 21:15:30 Tower kernel: R13: 0000000000000005 R14: ffffffff81e5a078 R15: 0000000000000000 Jul 6 21:15:30 Tower kernel: do_idle+0x192/0x20e Jul 6 21:15:30 Tower kernel: cpu_startup_entry+0x6a/0x6c Jul 6 21:15:30 Tower kernel: start_secondary+0x197/0x1b2 Jul 6 21:15:30 Tower kernel: secondary_startup_64+0xa4/0xb0 Jul 6 21:15:30 Tower kernel: ---[ end trace c82e319e0a257db0 ]--- syslog

i did, that's what one of the attached files.

The only docker I have with a fixed IP is pi-hole. The log recorded the following this morning: Jul 1 08:21:06 Tower kernel: mdcmd (102): set md_write_method 0 Jul 1 08:21:06 Tower kernel: Jul 1 08:28:05 Tower kernel: BUG: Bad page map in process C1 CompilerThre pte:ffff888c446f7d08 pmd:5ab41b067 Jul 1 08:28:05 Tower kernel: addr:000000004c68d19d vm_flags:00100073 anon_vma:000000000e448825 mapping: (null) index:1546759d4 Jul 1 08:28:05 Tower kernel: file: (null) fault: (null) mmap: (null) readpage: (null) Jul 1 08:28:05 Tower kernel: CPU: 15 PID: 29094 Comm: C1 CompilerThre Tainted: G B W 4.19.55-Unraid #1 Jul 1 08:28:05 Tower kernel: Hardware name: IBM System x3630 M4 -[7158AC1]-/00KF924, BIOS -[BEE166CUS-3.10]- 08/29/2018 Jul 1 08:28:05 Tower kernel: Call Trace: Jul 1 08:28:05 Tower kernel: dump_stack+0x5d/0x79 Jul 1 08:28:05 Tower kernel: print_bad_pte+0x216/0x233 Jul 1 08:28:05 Tower kernel: _vm_normal_page+0x50/0xb7 Jul 1 08:28:05 Tower kernel: change_protection+0x54f/0x85c Jul 1 08:28:05 Tower kernel: change_prot_numa+0x13/0x22 Jul 1 08:28:05 Tower kernel: task_numa_work+0x208/0x2ac Jul 1 08:28:05 Tower kernel: task_work_run+0x77/0x8b Jul 1 08:28:05 Tower kernel: exit_to_usermode_loop+0x46/0x9b Jul 1 08:28:05 Tower kernel: prepare_exit_to_usermode+0x66/0x79 Jul 1 08:28:05 Tower kernel: retint_user+0x8/0x8 Jul 1 08:28:05 Tower kernel: RIP: 0033:0x154727f7a99d Jul 1 08:28:05 Tower kernel: Code: 4c 8b 21 48 89 55 90 48 89 bd 60 ff ff ff 0f 83 e0 00 00 00 66 0f 1f 84 00 00 00 00 00 0f b6 02 48 8d 0d 66 e6 e6 00 89 45 c4 <8b> 04 81 3d ee 00 00 00 89 45 c0 0f 86 12 03 00 00 48 83 ea 01 48 Jul 1 08:28:05 Tower kernel: RSP: 002b:00001546f84cd980 EFLAGS: 00000293 ORIG_RAX: ffffffffffffff13 Jul 1 08:28:05 Tower kernel: RAX: 00000000000000c6 RBX: 00001546e04acfc0 RCX: 0000154728de9000 Jul 1 08:28:05 Tower kernel: RDX: 00001546e04acf24 RSI: 0000000000000003 RDI: 00001546f84cd9a0 Jul 1 08:28:05 Tower kernel: RBP: 00001546f84cda30 R08: 0000000000000000 R09: 00000000ffffffff Jul 1 08:28:05 Tower kernel: R10: 00001546e04acf60 R11: 0000000000000007 R12: 00001546e04ad090 Jul 1 08:28:05 Tower kernel: R13: 00001546e04ac780 R14: 000015472889dba8 R15: 0000000000000070 Jul 1 08:52:29 Tower rpcbind[25832]: connect from 192.168.1.233 to null() Jul 1 08:52:29 Tower rpcbind[25833]: connect from 192.168.1.233 to getport/addr(mountd) Jul 1 08:52:30 Tower rpcbind[25834]: connect from 192.168.1.233 to null() Jul 1 08:52:30 Tower rpcbind[25835]: connect from 192.168.1.233 to getport/addr(mountd) Jul 1 08:52:30 Tower rpc.mountd[8977]: authenticated mount request from 192.168.1.233:60026 for /mnt/user/video (/mnt/user/video) Jul 1 08:52:30 Tower rpcbind[25836]: connect from 192.168.1.233 to null() Jul 1 08:52:30 Tower rpcbind[25837]: connect from 192.168.1.233 to getport/addr(nfs) Jul 1 09:04:24 Tower kernel: BUG: Bad page map in process VM Periodic Tas pte:ffff888c446f7d08 pmd:5ab41b067 Jul 1 09:04:24 Tower kernel: addr:000000004c68d19d vm_flags:00100073 anon_vma:000000000e448825 mapping: (null) index:1546759d4 Jul 1 09:04:24 Tower kernel: file: (null) fault: (null) mmap: (null) readpage: (null) Jul 1 09:04:24 Tower kernel: CPU: 2 PID: 29097 Comm: VM Periodic Tas Tainted: G B W 4.19.55-Unraid #1 Jul 1 09:04:24 Tower kernel: Hardware name: IBM System x3630 M4 -[7158AC1]-/00KF924, BIOS -[BEE166CUS-3.10]- 08/29/2018 Jul 1 09:04:24 Tower kernel: Call Trace: Jul 1 09:04:24 Tower kernel: dump_stack+0x5d/0x79 Jul 1 09:04:24 Tower kernel: print_bad_pte+0x216/0x233 Jul 1 09:04:24 Tower kernel: _vm_normal_page+0x50/0xb7 Jul 1 09:04:24 Tower kernel: change_protection+0x54f/0x85c Jul 1 09:04:24 Tower kernel: change_prot_numa+0x13/0x22 Jul 1 09:04:24 Tower kernel: task_numa_work+0x208/0x2ac Jul 1 09:04:24 Tower kernel: task_work_run+0x77/0x8b Jul 1 09:04:24 Tower kernel: exit_to_usermode_loop+0x46/0x9b Jul 1 09:04:24 Tower kernel: do_syscall_64+0xdf/0xf2 Jul 1 09:04:24 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jul 1 09:04:24 Tower kernel: RIP: 0033:0x154728e481aa Jul 1 09:04:24 Tower kernel: Code: 00 00 b8 ca 00 00 00 0f 05 5a 5e c3 0f 1f 40 00 56 52 c7 07 00 00 00 00 81 f6 81 00 00 00 ba 01 00 00 00 b8 ca 00 00 00 0f 05 <5a> 5e c3 0f 1f 00 41 54 41 55 49 89 fc 49 89 f5 48 83 ec 18 48 89 Jul 1 09:04:24 Tower kernel: RSP: 002b:00001546f81cbc00 EFLAGS: 00000206 ORIG_RAX: 00000000000000ca Jul 1 09:04:24 Tower kernel: RAX: 0000000000000000 RBX: 00000000fffffffd RCX: 0000154728e481aa Jul 1 09:04:24 Tower kernel: RDX: 0000000000000001 RSI: 0000000000000081 RDI: 000015472022c728 Jul 1 09:04:24 Tower kernel: RBP: 00001546f81cbce0 R08: 0000000000000000 R09: 000015472022c750 Jul 1 09:04:24 Tower kernel: R10: 00001546f81cbc00 R11: 0000000000000206 R12: 000015472022c700 Jul 1 09:04:24 Tower kernel: R13: 000015472022c728 R14: 00001546f81cbca0 R15: 000015472022c750 Jul 1 09:38:35 Tower kernel: BUG: Bad page map in process G1 Young RemSet pte:ffff888c446f7d08 pmd:5ab41b067 Jul 1 09:38:35 Tower kernel: addr:000000004c68d19d vm_flags:00100073 anon_vma:000000000e448825 mapping: (null) index:1546759d4 Jul 1 09:38:35 Tower kernel: file: (null) fault: (null) mmap: (null) readpage: (null) Jul 1 09:38:35 Tower kernel: CPU: 23 PID: 29089 Comm: G1 Young RemSet Tainted: G B W 4.19.55-Unraid #1 Jul 1 09:38:35 Tower kernel: Hardware name: IBM System x3630 M4 -[7158AC1]-/00KF924, BIOS -[BEE166CUS-3.10]- 08/29/2018 Jul 1 09:38:35 Tower kernel: Call Trace: Jul 1 09:38:35 Tower kernel: dump_stack+0x5d/0x79 Jul 1 09:38:35 Tower kernel: print_bad_pte+0x216/0x233 Jul 1 09:38:35 Tower kernel: _vm_normal_page+0x50/0xb7 Jul 1 09:38:35 Tower kernel: change_protection+0x54f/0x85c Jul 1 09:38:35 Tower kernel: ? _copy_to_user+0x22/0x28 Jul 1 09:38:35 Tower kernel: change_prot_numa+0x13/0x22 Jul 1 09:38:35 Tower kernel: task_numa_work+0x208/0x2ac Jul 1 09:38:35 Tower kernel: task_work_run+0x77/0x8b Jul 1 09:38:35 Tower kernel: exit_to_usermode_loop+0x46/0x9b Jul 1 09:38:35 Tower kernel: prepare_exit_to_usermode+0x66/0x79 Jul 1 09:38:35 Tower kernel: retint_user+0x8/0x8 Jul 1 09:38:35 Tower kernel: RIP: 0033:0x15472859565d Jul 1 09:38:35 Tower kernel: Code: e5 41 56 41 55 41 54 53 48 89 fb 66 48 8d 3d 7a 29 81 00 66 66 48 e8 62 b5 6f ff ba 01 00 00 00 4c 8b 28 31 c0 f0 48 0f b1 13 <48> 85 c0 75 23 e9 e9 00 00 00 66 0f 1f 84 00 00 00 00 00 48 89 c1 Jul 1 09:38:35 Tower kernel: RSP: 002b:00001546f93f1ce0 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13 Jul 1 09:38:35 Tower kernel: RAX: 0000000000000000 RBX: 00001547201146a8 RCX: 0000000000000000 Jul 1 09:38:35 Tower kernel: RDX: 0000000000000001 RSI: 0000154720114510 RDI: 0000154728da7fc0 Jul 1 09:38:35 Tower kernel: RBP: 00001546f93f1d00 R08: 0000000000000000 R09: 000015472014cb50 Jul 1 09:38:35 Tower kernel: R10: 00001546f93f1c00 R11: 0000000000000206 R12: 00001546f93f1db0 Jul 1 09:38:35 Tower kernel: R13: 000015472014b800 R14: 0000154720114720 R15: 0000154728cf7328

I'm not exactly sure what's happening but my server is locking after a couple of days (this has happened a couple of times so far). The only thing I can do is a reboot. Attached is a copy of my syslog from last night after I got it back up and running as well as the diagnostics. I also have the following error in my log this morning. Jun 29 09:17:30 Tower kernel: WARNING: CPU: 3 PID: 5988 at net/netfilter/nf_conntrack_core.c:945 __nf_conntrack_confirm+0x97/0x686 Jun 29 09:17:30 Tower kernel: Modules linked in: xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle ip6table_filter ip6_tables vhost_net vhost tap veth macvlan xt_nat iptable_filter iptable_nat ipt_MASQUERADE nf_nat_ipv4 nf_nat ip_tables xfs nfsd lockd grace sunrpc md_mod tun bonding bnx2x mdio igb i2c_algo_bit sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate ipmi_ssif intel_uncore mpt3sas intel_rapl_perf wmi i2c_i801 ipmi_si i2c_core pcc_cpufreq raid_class button scsi_transport_sas [last unloaded: mdio] Jun 29 09:17:30 Tower kernel: CPU: 3 PID: 5988 Comm: kworker/3:2 Not tainted 4.19.55-Unraid #1 Jun 29 09:17:30 Tower kernel: Hardware name: IBM System x3630 M4 -[7158AC1]-/00KF924, BIOS -[BEE166CUS-3.10]- 08/29/2018 Jun 29 09:17:30 Tower kernel: Workqueue: events macvlan_process_broadcast [macvlan] Jun 29 09:17:30 Tower kernel: RIP: 0010:__nf_conntrack_confirm+0x97/0x686 Jun 29 09:17:30 Tower kernel: Code: c1 ed 20 89 2c 24 e8 67 fb ff ff 8b 54 24 04 89 ef 89 c6 41 89 c4 e8 29 f9 ff ff 84 c0 75 b9 49 8b 86 80 00 00 00 a8 08 74 25 <0f> 0b 44 89 e6 89 ef 45 31 ff e8 b2 f1 ff ff be 00 02 00 00 48 c7 Jun 29 09:17:30 Tower kernel: RSP: 0018:ffff8886678c3d98 EFLAGS: 00010202 Jun 29 09:17:30 Tower kernel: RAX: 0000000000000188 RBX: ffff8886422ece00 RCX: 000000008e171493 Jun 29 09:17:30 Tower kernel: RDX: 0000000000000001 RSI: 000000000000021c RDI: ffffffff81e090e8 Jun 29 09:17:30 Tower kernel: RBP: 00000000000062ba R08: ffff88843db45d30 R09: 00000000817a4f1c Jun 29 09:17:30 Tower kernel: R10: 0000000000000000 R11: ffff88863e371401 R12: 0000000000005e1c Jun 29 09:17:30 Tower kernel: R13: ffffffff81e8e080 R14: ffff88843db45cc0 R15: ffff88843db45d18 Jun 29 09:17:30 Tower kernel: FS: 0000000000000000(0000) GS:ffff8886678c0000(0000) knlGS:0000000000000000 Jun 29 09:17:30 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 29 09:17:30 Tower kernel: CR2: 00001498c65fd320 CR3: 0000000001e0a002 CR4: 00000000000606e0 Jun 29 09:17:30 Tower kernel: Call Trace: Jun 29 09:17:30 Tower kernel: <IRQ> Jun 29 09:17:30 Tower kernel: ipv4_confirm+0xaf/0xb7 Jun 29 09:17:30 Tower kernel: nf_hook_slow+0x37/0x96 Jun 29 09:17:30 Tower kernel: ip_local_deliver+0xa9/0xd7 Jun 29 09:17:30 Tower kernel: ? ip_sublist_rcv_finish+0x53/0x53 Jun 29 09:17:30 Tower kernel: ip_rcv+0xa0/0xbe Jun 29 09:17:30 Tower kernel: ? ip_rcv_finish_core.isra.0+0x2e2/0x2e2 Jun 29 09:17:30 Tower kernel: __netif_receive_skb_one_core+0x4d/0x69 Jun 29 09:17:30 Tower kernel: process_backlog+0x7c/0x116 Jun 29 09:17:30 Tower kernel: net_rx_action+0x10b/0x274 Jun 29 09:17:30 Tower kernel: __do_softirq+0xce/0x1e2 Jun 29 09:17:30 Tower kernel: do_softirq_own_stack+0x2a/0x40 Jun 29 09:17:30 Tower kernel: </IRQ> Jun 29 09:17:30 Tower kernel: do_softirq+0x4d/0x59 Jun 29 09:17:30 Tower kernel: netif_rx_ni+0x1c/0x22 Jun 29 09:17:30 Tower kernel: macvlan_broadcast+0x10f/0x153 [macvlan] Jun 29 09:17:30 Tower kernel: ? __switch_to_asm+0x41/0x70 Jun 29 09:17:30 Tower kernel: macvlan_process_broadcast+0xeb/0x128 [macvlan] Jun 29 09:17:30 Tower kernel: process_one_work+0x16e/0x24f Jun 29 09:17:30 Tower kernel: ? pwq_unbound_release_workfn+0xb7/0xb7 Jun 29 09:17:30 Tower kernel: worker_thread+0x1dc/0x2ac Jun 29 09:17:30 Tower kernel: kthread+0x10b/0x113 Jun 29 09:17:30 Tower kernel: ? kthread_park+0x71/0x71 Jun 29 09:17:30 Tower kernel: ret_from_fork+0x35/0x40 Jun 29 09:17:30 Tower kernel: ---[ end trace 4f9949cbfd7b7ba0 ]--- syslog tower-diagnostics-20190629-1421.zip

bump! anybody have any idea?