weirdcrap

You were right, I did leave one browser window open I totally forgot about. That's what I get for checking on the server from so many other servers on the network. Now that I fixed that CSRF error my ghost device is gone as well. I guess it had something to do with the browser session I had left open on the other machine.

@trurlThat disk has been unplugged for hours and is sitting on my desk at home so it should not still be showing in UD, that's why I was concerned about it. Thanks for the info about it being a part of UnRAID, I was not aware it was so heavily integrated. I did see some bits about having the controlr app installed with the associated plugin which I did have but have already uninstalled and it did not fix the issue. @SquidCome to think of it I may have a browser open on a machine in the server room I was using on Friday, that is probably the cause of the wrong csrf_token error.

I am still having this issue, though mine all show wrong csrf_token instead of missing. Hopefully someone can help me out. Running UnRAID 6.3.2 and as far as I know I was running the latest UD and preclear, I had CA AutoUpdate setup for the plugins to run weekly. I came in to the office last night to hook up a drive and setup a file copy to run over night. I hooked up a usb 3.0 external wd passport drive to the front port of the server and noticed a kernel panic flash across the screen and then the power light went out and the server rebooted. On booting and loading the UnRAID OS with the drive still plugged in UnRAID crashed again. I shut the server off, unplugged it, let it sit for five minutes, plugged it back in and it booted fine. When I looked at the log it was getting hit every five seconds with wrong csrf_token errors from both the preclear plugin and UD. I found some other threads were people saw clearing their browsers and uninstalling re-installing fixed it so I tried that, but the issue persisted. I use Chrome mainly if that makes a difference. I decided to uninstall it for the time being so the logs wouldn't fill up because I didn't want to work on it in the middle of the night. I unplugged the drive, cleared the /boot/ directory of any files folders I found relating to the plugins and rebooted the server. Even with the plugins uninstalled I am still seeing the UD section on my Main tab with a phantom disk for the USB hard drive listed as /dev/sda (see attached snippet). I checked and fdisk -l does not show a /dev/sda at all so the underlying Linux kernel does not see the drive still. Diagnostics are attached, you can see in the log that as soon as I attempt to re-install UD my log immediately starts getting wrong csrf_token errors again. I would prefer to be able to keep UD and preclear so I would appreciate some help in fixing whatever happened. node-diagnostics-20170305-1011.zip

https://github.com/linuxserver/docker-plex#setting-up-the-application The "fun" part is finding an exact version number that doesn't end up a 404 in the Git pull. I have one saved I used to fall back due to Roku issues. x.x.x.xxxx-xxxxxxx Its about 3 or 4 weeks back as of today? Hope that helps. ps. no this is NOT a dvr version number. *mod - don't post plexpass version numbers I am also having Roku issues, Plex has become unwatchable for me. Does anyone have a solution? Is it just to roll back to this magical x.x.x.xxxx-xxxxxxx version number where Roku playback wasn't completely f*cked?

What's the Public version? A fork of Jackett that includes support for public trackers not just private ones.

Ok, so that will print that line to the logger daemon so we can see it in the syslog? I have added the line to the beginning of the unmount script. I will move those system log errors to a separate support thread and see if anyone can shed some light on them. If it is indeed a heat issue I will have to talk to my boss and see if he will let me turn down the A/C in the server room or I will have to order an after market CPU cooler.

Sep 19 22:30:42 Node kernel: ------------[ cut here ]------------ Sep 19 22:30:42 Node kernel: WARNING: CPU: 0 PID: 27309 at ./arch/x86/include/asm/thread_info.h:236 SyS_rt_sigsuspend+0x8f/0x9e() Sep 19 22:30:42 Node kernel: Modules linked in: xt_nat veth xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net tun vhost macvtap macvlan ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod x86_pkg_temp_thermal coretemp kvm_intel kvm r8169 i2c_i801 i2c_core ahci libahci mii Sep 19 22:30:42 Node kernel: CPU: 0 PID: 27309 Comm: Threadpool work Not tainted 4.4.19-unRAID #1 Sep 19 22:30:42 Node kernel: Hardware name: Gigabyte Technology Co., Ltd. B85M-DS3H-A/B85M-DS3H-A, BIOS F2 08/10/2015 Sep 19 22:30:42 Node kernel: 0000000000000000 ffff8803c77ebee0 ffffffff8136a68e 0000000000000000 Sep 19 22:30:42 Node kernel: 00000000000000ec ffff8803c77ebf18 ffffffff8104a39a ffffffff81055502 Sep 19 22:30:42 Node kernel: fffffffffffffdfe 0000000000014f98 000000000000000d 000000000000a0b7 Sep 19 22:30:42 Node kernel: Call Trace: Sep 19 22:30:42 Node kernel: [<ffffffff8136a68e>] dump_stack+0x61/0x7e Sep 19 22:30:42 Node kernel: [<ffffffff8104a39a>] warn_slowpath_common+0x8f/0xa8 Sep 19 22:30:42 Node kernel: [<ffffffff81055502>] ? SyS_rt_sigsuspend+0x8f/0x9e Sep 19 22:30:42 Node kernel: [<ffffffff8104a457>] warn_slowpath_null+0x15/0x17 Sep 19 22:30:42 Node kernel: [<ffffffff81055502>] SyS_rt_sigsuspend+0x8f/0x9e Sep 19 22:30:42 Node kernel: [<ffffffff81620a2e>] entry_SYSCALL_64_fastpath+0x12/0x6d Sep 19 22:30:42 Node kernel: ---[ end trace 753ae045f3fb133e ]--- This: x86_pkg_temp_thermal coretemp kvm_intel kvm r8169 i2c_i801 i2c_core ahci libahci mii But I don't know that much about these faults. Reardless, I don't think is is good. I agree I never like seeing those messages but so far I haven't been able to find any information on what exactly that kernel error means.

I noticed those in the system log this morning when I was trying to troubleshoot this. They python error took place right around the time I was upgrading from 6.19 to 6.2 and I haven't seen it pop up since (I upgraded 9/18 around 9-10AM) I have never seen the CPU temp spike over 45C and utilization is generally pretty low (less than 10%) unless plex is transcoding heavily. What part of those messages makes you think the CPU is over heating? EDIT: Well apparently when I setup the Dynamix CPU temp plugin I picked the wrong sensor, when plex is really hammering the CPU it gets up to around 58-60C but that is still well below the thermal throttling threshold for the processor. The UnRAID case sits in an air conditioned server room so besides cranking up the fans manually on the fan controller my only other options to address a CPU temp issue would be to buy an aftermarket CPU cooler.

The mounts became unavailable sometime in the last 24 hours, sorry I can't be more specific I haven't really checked on it much. The only reason I noticed is my couchpotato was pissed off because it couldn't find the remote share it uses. I have a diagnostic log attached to my OP in this thread.

Can't remember off the top of my head if I put the time of execution in the logging for the start / stop scripts (not at home at the moment). But if the scripts logs available through user.scripts shows only a single execution, then its not unRaid. I didn't think to check the script logs, where do I view them? I only see a log icon next to my mount script? Nevermind, found it. I don't even see a log having been generated for the unmount script so I guess the plugin hasn't run the script at all. Like I said before I am just going off what I have experienced previously with the PowerDown plugin and when I disabled the K00 script prior to the v2.23 release I no longer had an issue. I have disabled the schedule for the unmount script in user.scripts for now and I will see if they stay mounted...

Thanks, I would tend to agree with you if not for my previous experience with powerdown. Once I disabled the script that had the umount commands to remove the shares they would stay up and never drop until I manually removed them. The weird behavior makes me think there has to be some kind of signal unRAID is issuing that is tricking these plugins into thinking that the array is being stopped or something like that (of course I am just guessing).

Hi Squid, not sure if you can help me with an issue I am having that has come back up now that powerdown is deprecated for v6.2. In powerdown I had K and S scripts that would mount and remove remote share mounts when the array was stopped and started. Prior to powerdown v2.23 I had issues where my mounts would mysteriously disappear that were solved by simply disabling the K script. The changes dlandon made in v2.23 of his excellent script fixed my issues and my shares stayed mounted without any problems. Now that I have moved to unRAID v6.2 and started using your user scripts plugin my issue has returned. I am randomly losing my remote share mounts after only a day or so of having them mounted. The scripts are set to run on array start and array stop so they shouldn't be executing for any other reason and I don't see any evidence of them running randomly in the system log. I have attached my diagnostics zip to this post. Here is a copy/paste of my post from the powerdown thread that shows what my scripts contain and some other details: node-diagnostics-20160920-0936.zip

to modify the startup settings for sonarr , exec into the container docker exec -it <container-name> bash and modify the file /etc/service/sonarr/run Ok, I am completely new to messing around with mono and editing stuff in Docker containers so bear with me. This is what is in the run file: XDG_CONFIG_HOME="/config/xdg" exec /sbin/setuser abc mono /opt/NzbDrone/NzbDrone.exe -nobrowser -data=/config so would I just append the debug switch here? XDG_CONFIG_HOME="/config/xdg" exec /sbin/setuser abc mono --debug /opt/NzbDrone/NzbDrone.exe -nobrowser -data=/config Or just put it at the end of the line? XDG_CONFIG_HOME="/config/xdg" exec /sbin/setuser abc mono /opt/NzbDrone/NzbDrone.exe -nobrowser -data=/config --debug

Is it possible to run mono with the debug switch in this container? I am having an issue with sonarr and the devs on their forum say the stack trace logs are pretty much useless without mono in debug mode. EDIT: In fact while I am here I may as well ask the community about my issue as well. I am having issues with certain shows/episodes/possibly NZBs being added to NZBGet from Sonarr while others work with no issue. I have made no changes to either my Sonarr or NZBGet setup in weeks and this issue just started happening yesterday afternoon.I have verified that Sonarr can connect to NZBGet by using the "test" button in the download client page of the Sonarr settings. I restarted UnRAID as well on the off chance that something was hung up in the system. Here is a pastebin of my sonarr log from yesterday: http://pastebin.com/xyJN8jnQ and here is a link to my thread over on the sonarr forums if it helps at all: https://forums.sonarr.tv/t/request-failed-failed-to-add-nzb/11596 The error message that stands out to me and would explain why the NZB fails to add is: [v2.0.0.4230] System.IO.IOException: "Error writing request ---> System.Net.Sockets.SocketException: The socket has been shut down" But if the connection between Sonarr and NZBGet was closed then why do other shows and even other episodes from the same show work fine?

Fixed for me as well, looks like the missing python package was added to resolve the issue.

Is anyone else having issues with the container after the new sab update this morning? I had restarted UnRAID to put a new disk in for preclearing and it looks like sab downloaded an update and now I can't get it to come up in the web interface at all, I just get can't connect to server. If I view the docker log outside of the UnRAID logger directly using docker logs -f sabnzbd: EDIT: here is the full log after a restart, ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- *** Running /etc/my_init.d/20_apt_update.sh... finding fastest mirror Getting list of mirrors...done. Testing latency to mirror(s) [72/72] 100% Getting list of launchpad URLs...done. Looking up 3 status(es) [3/3] 100% 1. ubuntu.mirrors.tds.net (current) Latency: 10.00 ms Org: TDS Internet Services Status: Up to date Speed: 1 Gbps 2. mirrors.gigenet.com Latency: 11.00 ms Org: GigeNet Status: Up to date Speed: 1 Gbps 3. cosmos.cites.illinois.edu Latency: 12.99 ms Org: University of Illinois Status: Up to date Speed: 100 Mbps ubuntu.mirrors.tds.net (current) is the currently used mirror. Skipping file generation We are now refreshing packages from apt repositories, this *may* take a while Ign http://ubuntu.mirrors.tds.net trusty InRelease Hit http://ubuntu.mirrors.tds.net trusty-updates InRelease Hit http://ubuntu.mirrors.tds.net trusty-security InRelease Hit http://ubuntu.mirrors.tds.net trusty Release.gpg Hit http://ubuntu.mirrors.tds.net trusty-updates/main Sources Hit http://ubuntu.mirrors.tds.net trusty-updates/restricted Sources Hit http://ubuntu.mirrors.tds.net trusty-updates/universe Sources Hit http://ubuntu.mirrors.tds.net trusty-updates/multiverse Sources Hit http://ppa.launchpad.net trusty InRelease Hit http://ubuntu.mirrors.tds.net trusty-updates/main amd64 Packages Hit http://ubuntu.mirrors.tds.net trusty-updates/restricted amd64 Packages Hit http://ubuntu.mirrors.tds.net trusty-updates/universe amd64 Packages Hit http://ubuntu.mirrors.tds.net trusty-updates/multiverse amd64 Packages Hit http://ppa.launchpad.net trusty/main amd64 Packages Hit http://ubuntu.mirrors.tds.net trusty-security/main Sources Hit http://ubuntu.mirrors.tds.net trusty-security/restricted Sources Hit http://ubuntu.mirrors.tds.net trusty-security/universe Sources Hit http://ubuntu.mirrors.tds.net trusty-security/multiverse Sources Hit http://ubuntu.mirrors.tds.net trusty-security/main amd64 Packages Hit http://ubuntu.mirrors.tds.net trusty-security/restricted amd64 Packages Hit http://ubuntu.mirrors.tds.net trusty-security/universe amd64 Packages Hit http://ubuntu.mirrors.tds.net trusty-security/multiverse amd64 Packages Hit http://ubuntu.mirrors.tds.net trusty Release Hit http://ubuntu.mirrors.tds.net trusty/main Sources Hit http://ubuntu.mirrors.tds.net trusty/restricted Sources Hit http://ubuntu.mirrors.tds.net trusty/universe Sources Hit http://ubuntu.mirrors.tds.net trusty/multiverse Sources Hit http://ubuntu.mirrors.tds.net trusty/main amd64 Packages Hit http://ubuntu.mirrors.tds.net trusty/restricted amd64 Packages Hit http://ubuntu.mirrors.tds.net trusty/universe amd64 Packages Hit http://ubuntu.mirrors.tds.net trusty/multiverse amd64 Packages Reading package lists... *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/10_add_user_abc.sh... *** Running /etc/my_init.d/20_apt_update.sh... Getting list of mirrors...done. Testing latency to mirror(s) [72/72] 100% Getting list of launchpad URLs...done. Looking up 3 status(es) [3/3] 100% ubuntu.mirrors.tds.net (current) is the currently used mirror. Skipping file generation *** Running /etc/my_init.d/30_set_config.sh... *** Running /etc/my_init.d/999_advanced_script.sh... *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 123 Jul 6 14:04:49 3bf6a4df3199 syslog-ng[132]: syslog-ng starting up; version='3.5.3' Traceback (most recent call last): File "/usr/bin/sabnzbdplus", line 55, in <module> import cherrypy File "/usr/share/sabnzbdplus/cherrypy/__init__.py", line 64, in <module> from cherrypy._cperror import HTTPError, HTTPRedirect, InternalRedirect File "/usr/share/sabnzbdplus/cherrypy/_cperror.py", line 122, in <module> import six ImportError: No module named six Traceback (most recent call last): File "/usr/bin/sabnzbdplus", line 55, in <module> import cherrypy File "/usr/share/sabnzbdplus/cherrypy/__init__.py", line 64, in <module> from cherrypy._cperror import HTTPError, HTTPRedirect, InternalRedirect File "/usr/share/sabnzbdplus/cherrypy/_cperror.py", line 122, in <module> import six ImportError: No module named six Traceback (most recent call last): File "/usr/bin/sabnzbdplus", line 55, in <module> import cherrypy File "/usr/share/sabnzbdplus/cherrypy/__init__.py", line 64, in <module> from cherrypy._cperror import HTTPError, HTTPRedirect, InternalRedirect File "/usr/share/sabnzbdplus/cherrypy/_cperror.py", line 122, in <module> import six ImportError: No module named six Traceback (most recent call last): File "/usr/bin/sabnzbdplus", line 55, in <module> import cherrypy File "/usr/share/sabnzbdplus/cherrypy/__init__.py", line 64, in <module> from cherrypy._cperror import HTTPError, HTTPRedirect, InternalRedirect File "/usr/share/sabnzbdplus/cherrypy/_cperror.py", line 122, in <module> import six ImportError: No module named six Traceback (most recent call last): File "/usr/bin/sabnzbdplus", line 55, in <module> import cherrypy File "/usr/share/sabnzbdplus/cherrypy/__init__.py", line 64, in <module> from cherrypy._cperror import HTTPError, HTTPRedirect, InternalRedirect File "/usr/share/sabnzbdplus/cherrypy/_cperror.py", line 122, in <module> import six ImportError: No module named six Traceback (most recent call last): File "/usr/bin/sabnzbdplus", line 55, in <module> import cherrypy File "/usr/share/sabnzbdplus/cherrypy/__init__.py", line 64, in <module> from cherrypy._cperror import HTTPError, HTTPRedirect, InternalRedirect File "/usr/share/sabnzbdplus/cherrypy/_cperror.py", line 122, in <module> import six ImportError: No module named six Traceback (most recent call last): File "/usr/bin/sabnzbdplus", line 55, in <module> import cherrypy File "/usr/share/sabnzbdplus/cherrypy/__init__.py", line 64, in <module> from cherrypy._cperror import HTTPError, HTTPRedirect, InternalRedirect File "/usr/share/sabnzbdplus/cherrypy/_cperror.py", line 122, in <module> import six ImportError: No module named six Traceback (most recent call last): File "/usr/bin/sabnzbdplus", line 55, in <module> import cherrypy File "/usr/share/sabnzbdplus/cherrypy/__init__.py", line 64, in <module> from cherrypy._cperror import HTTPError, HTTPRedirect, InternalRedirect File "/usr/share/sabnzbdplus/cherrypy/_cperror.py", line 122, in <module> import six ImportError: No module named six I tried deleting and re-creating the container and there is no change, I can see the two ports setup and listening using netstat so it seems like the web server side of it is up? Could there be something wrong with my configuration? In the meantime I have switched to NZBGet, so far I like what I see.

You and me both... Do you have NZBToMedia.py setup and working and could give me some instructions for the TorrentToMedia.py script? CP seems to do alright the majority of the time with getting stuff moved from SAB properly but it's torrent client support is horrendous. I had posted a thread on the CP forums about issues with the CP renamer causing all kinds of annoyances with still seeding torrents and the renamer partially moving files (causing both my plex copy and the original copy to be unplayable/unseedable) and constantly re-processing movies that are still seeding because it thinks they are repacks of a release (even though they are exactly the same). The moderators suggestion was to use his TorrentToMedia.py script. Should I put the script inside the docker container or will it get wiped out anytime the docker updates? How do I tell CP to use a post-processing script for just torrent downloads? Some basic steps to get it setup would be super helpful. Mr crap... I don't use NZBmedia.py at all and was just trying to help slimer, who left before we ever got to the root of his problem, which I'm sure was to do with his config somewhere. He hasn't been online since April so you may not get much feedback on your request. Good Luck nonetheless. Love the username Yeah it is a unique name that I picked back when I was a teenager haha. I am fairly certain my CP and Deluge configurations are correct as the majority of the time I do not have issues, the renamer grabs the media and copies things correctly. However occasionally (ie this morning) it just randomly starts to repeatedly re-process the same movies over and over and over again. But anyways , could you tell me if it is safe to put the script in the docker container itself? I am assuming it will survive any updates as long as I don't actually delete and re-create the container?

You and me both... Do you have NZBToMedia.py setup and working and could give me some instructions for the TorrentToMedia.py script? CP seems to do alright the majority of the time with getting stuff moved from SAB properly but it's torrent client support is horrendous. I had posted a thread on the CP forums about issues with the CP renamer causing all kinds of annoyances with still seeding torrents and the renamer partially moving files (causing both my plex copy and the original copy to be unplayable/unseedable) and constantly re-processing movies that are still seeding because it thinks they are repacks of a release (even though they are exactly the same). The moderators suggestion was to use his TorrentToMedia.py script. Should I put the script inside the docker container or will it get wiped out anytime the docker updates? How do I tell CP to use a post-processing script for just torrent downloads? Some basic steps to get it setup would be super helpful.

I am pretty sure I installed mine through CA and didn't have any issues. I believe CA just pulls the templates from the developers repo when you request them through CA. It could have just been a bad download of the XML template?

My log 100% contains my VPN username and password right near the top and yours doesn't even seem to make a mention of VPN anywhere in the log you posted. Here is what my log looks like: http://pastebin.com/B8cLidFk Having to enter the environmental variables manually is not the expected behavior, they should all be there and just need the values filled in. Are those the only environmental variables you have? If so you are missing some important ones. Based on what your log has in it I would say that these missing environmental variables are causing the VPN component of this docker to never be started in the first place which is why you are seeing your public ip address using the ip checking torrent file. The environmental variables you should have are: VPN_ENABLED yes VPN_USER UsernameHere VPN_PASS PasswordHere VPN_REMOTE nl.privateinternetaccess.com (this is the default one but can be changed to any PIA endpoint that supports port forwarding) VPN_PROTOCOL udp VPN_PROV pia ENABLE_PRIVOXY no (if you want to use privoxy you can, I choose not to) LAN_NETWORK 192.168.10.0/24 (this should be what you have based on what your IP scheme is) DEBUG false PUID 99 PGID 100 Out of curiosity did you get this docker template directly through binhex's repository or did you get it through the CommunityApplications plugin?

Can you post your container log file and your environmental variable settings so I can make sure everything is set correctly? Also post your servers local IP and subnet so I can make sure the LAN_NETWORK variable is set correctly. Be sure to remove the VPN credentials from the container log and environment variables before posting. Where do I grab the container log? I am familiar with getting into the Docker containers I just want to make sure I grab the correct file. There are probably easier ways than this but this is the only way I have ever done it. On the docker container page turn on advanced view and find the delugevpn container id (mine is 6a153b1d55b1). In the terminal navigate to /var/lib/docker/containers and find the directory that matches the container id you found (the folder names will be longer than the container name but they should still be unique, in my case mine was: 6a153b1d55b172fd951a6c5c0c524c9737a67609bfd72e44e44a4d561e531521). In that folder there should be a LongContainerIDString-json.log file. Copy that over to somewhere that you can access from the machine you are posting from and attach it or if it won't fit pastebin it. Remember that the docker does print your VPN credentials in plain text so be sure to remove those first (they should be somewhere near the top). EDIT: Alternatively if you just started the container you should be able to get the full log from the web GUI by clicking the log icon all the way to the right of the container entry on the docker tab and copy pasting the contents of it. The web GUI only shows the last 350 lines of the log file and my container has been running for a while so my startup log info is long gone.

Can you post your container log file and your environmental variable settings so I can make sure everything is set correctly? Also post your servers local IP and subnet so I can make sure the LAN_NETWORK variable is set correctly. Be sure to remove the VPN credentials from the container log and environment variables before posting.

It should already be started, you simply need to check allow remote connections under preferences in the webui (see attachment). Then in CouchPotato this is what I have setup for deluge (see attachment). I use the IP address of UnRAID plus the port of the daemon and the user I defined in the auth file according to Q6 in the OP. I've checked all this many times. The daemon is not running. I get connection failed, which is 100% not to do with my ip or port. The auth file and details in CP are correct. Using a different version of CP gives the same issue. I am positive it is the Daemon. Can you post a copy of the container log? I believe it leaves your VPN credentials in plain text in the log so be sure to remove them.

It is possible the script wasn't properly detecting the new port assigned to you (might be related to the issues I am having with the Windows client). The link I posted a few posts back made it sound like you are dynamically given a port from the endpoint and it can change at any time.

That is using the site itself. When I view the peer list on a file I am seeding it shows my username, that I am seeding, and that I am connectable. In Deluge on Windows there is a way to test if you are connectable I believe but it is not present in this version.