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

Edited August 3, 20196 yr by Patb
additional information

Are you using Plex? Because the ipv6 setting they mention is in Plex not unRAID.

I had the same error yesterday, disabled ipv6 in Plex and the error was gone.

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

Edited August 4, 20196 yr by Patb
new information

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.

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