I have been chasing this down for the past few days and I am still stumped. I have removed all apps and turned off docker and vm and still keep getting this. I have tried searching and I keep coming up empty handed. Seems to be going off every hour to 50 minutes and I am new to unraid  their is no file or folder gcsp and when i try to figure out what uses that I come up empty handed on google search.

 

Jul 11 20:29:26 SERVERHOSTNAME apcupsd[8972]: NIS server startup succeeded
Jul 11 20:32:15 SERVERHOSTNAME emhttpd: req (3): cmd=/plugins/user.scripts/backgroundScript.sh&arg1=/tmp/user.scripts/tmpScripts/UPS/script&csrf_token=****************
Jul 11 20:32:15 SERVERHOSTNAME emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/backgroundScript.sh /tmp/user.scripts/tmpScripts/UPS/script
Jul 11 20:32:33 SERVERHOSTNAME emhttpd: req (4): csrf_token=****************&title=Log+Information&cmd=%2Fplugins%2Fuser.scripts%2FshowLog.php&arg1=UPS
Jul 11 20:32:33 SERVERHOSTNAME emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/showLog.php UPS
Jul 11 20:34:19 SERVERHOSTNAME emhttpd: req (5): cmdStartMover=Move+now&csrf_token=****************
Jul 11 20:34:19 SERVERHOSTNAME emhttpd: shcmd (117): /usr/local/sbin/mover &> /dev/null &
Jul 11 20:49:47 SERVERHOSTNAME emhttpd: req (6): cmd=/plugins/community.applications/scripts/pluginInstall.sh&arg1=remove&arg2=disklocation-master.plg&csrf_token=****************
Jul 11 20:49:47 SERVERHOSTNAME emhttpd: cmd: /usr/local/emhttp/plugins/community.applications/scripts/pluginInstall.sh remove disklocation-master.plg
Jul 11 20:49:47 SERVERHOSTNAME root: plugin: running: anonymous
Jul 11 20:49:50 SERVERHOSTNAME emhttpd: req (7): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog
Jul 11 20:49:50 SERVERHOSTNAME emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog
Jul 11 21:12:28 SERVERHOSTNAME root: error: /gcsp/2.0: missing csrf_token
Jul 11 21:12:28 SERVERHOSTNAME root: error: /gcsp/2.0: missing csrf_token
Jul 11 21:12:28 SERVERHOSTNAME root: error: /gcsp/2.0: missing csrf_token
Jul 11 21:12:28 SERVERHOSTNAME root: error: /gcsp/2.0: missing csrf_token
Jul 11 21:12:29 SERVERHOSTNAME root: error: /gcsp/2.0: missing csrf_token
Jul 11 21:12:29 SERVERHOSTNAME root: error: /gcsp/2.0: missing csrf_token
Jul 11 21:12:29 SERVERHOSTNAME root: error: /gcsp/2.0: missing csrf_token

Edited July 21, 20196 yr by Titus
[SOLVED]

Seems to be related to Plex if the other thread is accurate.

Start here:

       https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-545988

 

And then there is this current working thread: 

     https://forums.unraid.net/topic/81612-missing-csrf_token/

 

I would recommend that you simply follow the above thread and see if someone comes up with a solution to your problem.  If they don't find a solution, you want to post back here with more details like your Diagnostic file and a list of plugins and Dockers that you are using.  (By hanging onto this thread, the follow-on posts will be related to only your problem (hopefully) rather than being mixed in with two or three other people's issues.) 

 

Seems to be plex. once i checked disable ipv6 it stopped but I will wait a few days and see what it does once I have to restart the server again. 

Under Network Settings > Advanced View >  Enable server support for IPv6

 

uncheck it. I haven't had a single issues since its been unchecked I will repoort back in a few days/week to report if it is still not throwing the error

IF this fixes it, please come back and edit the  title to show that it is [SOLVED]. 

So after a week I haven't had the issue again. I have updated the Forum Header to reflect.

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.

9 minutes ago, Patb said:

I'm getting the same error but I checked my Plex settings and I already have "Enable server support for IPv6" unchecked in Plex.

Did you do it in this place?

On 7/14/2019 at 10:24 PM, Titus said:

Under Network Settings > Advanced View >  Enable server support for IPv6

 

uncheck it. I haven't had a single issues since its been unchecked I will repoort back in a few days/week to report if it is still not throwing the error

Many folks (depending on where you are in the world) don't need to use IPv6 protocol on the LAN side of their router and many ISP's shield the end user from having to use it to access the WWW world. 

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

1 hour ago, Patb said:

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.   

We are at cross purposes here.  I do not run Plex but Unraid itself has provision for  using IPv6.  You can find it by going to:

 

Settings   >>>    Network Settings   Now look at your "Interface ethX"  and find the dropdown box for 'Network protocol:' and make sure it is set to 'IPv4 only'.    

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).

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!