Patb

Members
  • Posts

    35
  • Joined

  • Last visited

Patb's Achievements

Newbie

Newbie (1/14)

3

Reputation

  1. 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.
  2. Updated Plex docker last night to Version 1.16.4.1469 and the problem seems to have gone away.
  3. 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.
  4. 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.
  5. Yes I did. I read about it when I searched how to recreate the docker image. Thanks
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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!
  11. 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).
  12. 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
  13. 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.
  14. ok, this is strange, I renamed the container to bitwarden (lower case b) and it now works... Thanks
  15. They are both in a network called "proxynet" and I verified that the names match. Still no success.