Adam64

That was my only good idea Unless it is running a task my Sonarr docker uses hardly any resources Thanks. I just got an update to the docker that seemed to update everything, so I'm crossing my fingers that it solves it. And it apparently did solve it. Thanks for the help all.

That was my only good idea Unless it is running a task my Sonarr docker uses hardly any resources Thanks. I just got an update to the docker that seemed to update everything, so I'm crossing my fingers that it solves it.

I'm on the stable version.

No one else is seeing this? I've tried reinstalling the docker, both importing the backup and creating it all new from scratch. Attached is a screenshot from CA showing it at 37% CPU utilization and using 19GB RAM. Not seeing this behaviour at all on my setup. Log into the webgui for sonarr and check System>Tasks, see if there is anything running? Never really had the time to fully investigate, but I don't actually believe that sonarr is truly using that amount of memory. Rather its all the cache, etc that the linux base is using (http://www.linuxatemyram.com/) and it will get released once something else requires the memory. But if you truly are worried about it then limit the amount of RAM that sonarr is capable of using (http://lime-technology.com/forum/index.php?topic=40937.msg492112#msg492112) As far as the CPU usage, I've never really seen sonarr be a pig like that unless its actually scanning or actively searching or what not. You can also limit its CPU resources (http://lime-technology.com/forum/index.php?topic=40937.msg492111#msg492111) for when something else requires the cpu time. The key question is sonarr actually working for you? Yeah, it does seem to be working. That said it's worked fine for months with zero issues, but now in the past few weeks this CPU and RAM thing has started. I could limit the Docker's access to CPU and RAM per your suggestion, but would prefer to find the underlying cause.

No one else is seeing this? I've tried reinstalling the docker, both importing the backup and creating it all new from scratch. Attached is a screenshot from CA showing it at 37% CPU utilization and using 19GB RAM. The RAM usage makes it seem like it has a severe memory leak.

I've been using this Sonarr docker for months and it's worked well. I've noticed in the past few days that my unRAID box CPU utilization is stuck at around 33% and if I stop the Sonarr docker it goes to zero, then restarting the docker it behaves as normal. Looking at the log doesn't seem to show anything happening at the time. Any ideas how I can troubleshoot? Edit: this happens daily now. Edit: I just restarted the docker a few minutes ago and CA confirms that it's using 30% of the CPU

I made the change to strong certs and got these warnings in the log: 2016-07-15 13:52:15,998 DEBG 'start-script' stdout output: Fri Jul 15 13:52:15 2016 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1570', remote='link-mtu 1542' Fri Jul 15 13:52:15 2016 WARNING: 'cipher' is used inconsistently, local='cipher AES-256-CBC', remote='cipher BF-CBC' Fri Jul 15 13:52:15 2016 WARNING: 'auth' is used inconsistently, local='auth SHA256', remote='auth SHA1' Fri Jul 15 13:52:15 2016 WARNING: 'keysize' is used inconsistently, local='keysize 256', remote='keysize 128' It still seems to start. Any need for concern?

I'm getting a malformed expression error in the log: File "/usr/lib/python2.7/site-packages/deluge/ui/console/commands/config.py", line 77, in atom raise SyntaxError("malformed expression (%s)" % token[1]) SyntaxError: malformed expression (,) My settings are: VPN_PROV: pia VPN_PROTOCOL: udp VPN_PORT: 1198 (or 1197 with STRONG_CERTS: yes). Interestingly sabnzbdvpn works fine with the same exact settings.

ok so if you have STRONG_CERTS set to yes then use port 501, if the env var doesnt exist or isnt set to yes then set the port to 502, that should sort it. I'm confused about the right port. I thought it was supposed to be 1198 (or 1197)? Where did 501 and 502 come from? From memory it goes like this:- 1198 = standard udo 1197 = strong UDP 502 = standard TCP 501 = strong tcp Sent from my SM-G900F using Tapatalk Thanks!

ok so if you have STRONG_CERTS set to yes then use port 501, if the env var doesnt exist or isnt set to yes then set the port to 502, that should sort it. I'm confused about the right port. I thought it was supposed to be 1198 (or 1197)? Where did 501 and 502 come from?

PIA users please read Due to changes in certificates and the increasing of the encryption used you will need to do the following (affects PIA users only):- 1. Go to unraid docker ui, left click delugevpn icon, and select stop 2. Delete all files in /config/openvpn/ on the host 3. Go to unraid docker ui, left click delugevpn icon, and select edit 4. Change the port number, normally 1194 to port 1198 5. Ciick save The action of saving will not only change your config but will force the pulldown of the latest docker image (unraid docker updates bug causes updates not to show). If anybody is seeing issues please screenshot your edit screen with advanced view switched on, also post the supervisord.log file (located in /config). Thanks!

Hi thanks did that and i can pull the docker image down now. I installed it last night and works fine. However i am getting the update message again this morning. I update it then when i check for updates again it says it needs updating? @naturalcarr are you getting update messages since your reinstall? Yeah I still get it when I mount my array, but that's it, so as long as my server and docker are on and enabled, it's not an issue. Sent from my SM-N910T using Tapatalk I get the same thing. It is fine till I reboot the server or click the check for updates button. Same here. Every day it wants me to update it. I've tried deleting the docker and making a new one and it's the same.

32GB Sent from my SM-T810 using Tapatalk

Does anyone have this working on 6.2B21? I'm having issues -- not sure it's the Plex docker, or even if it's Plex itself. Still investigating at this point.

+1 for Teracopy. Also, I'm guessing you've already done this, but make sure that SMB2&3 are disabled on your Win10 machine. https://support.microsoft.com/en-us/kb/2696547

+1

I was doing a defrag on one of my disks which ended up locking up my unRAID box and I had to hard reset it. I'd like to use this plugin to confirm that all the data is good on the disk. Do I just do the "check" command on the disk? What if I've updated the build and exported in the meantime, would that have exported a new hash with bad data?

Well... had to cycle power. BRB after my 10 hour parity check.

In my experience, if you specify a drive it ignores any duration you pass it. And 12 hours isn't anything to worry about, based on what other people are seeing. But if the system has actually locked up, that is new. Usually the best way to troubleshoot that is to look on the console for any messages. If you started the defrag from the console you can try ctrl-c to cancel it. Depending on what you see on the console you can either continue waiting or go ahead and power cycle. I started it from Putty, which seems to have hung up, so then I hooked up a monitor and keyboard to the box, but no joy -- blank screen and no reaction to a keypress. The HD light is flashing occasionally, but I would expect it to be more solid if it were defragging. Is there any magic to hooking up a monitor and keyboard? HDMI monitor and USB keyboard.

I started on my second drive that was 75% fragmented and it apparently ignored my -t 21400 as it's been running for over 12 hours. I'm concerned that it may be locked up now as the GUI is unresponsive and I can't access SMB shares nor open another terminal to it. Has anyone else seen this? Any thoughts on how to recover?

Thanks! I'd be interested in hearing how much it improves (and how long it takes) I had it run for 6 hours and it went from 80%ish to 0.44%. Very cool.

Thanks for posting this ljm42 and thanks to all for the discussion. I tested my drives and one of them was >80%, so defragging now. Thanks!

Thanks for the reply. Since I posted this I decided to try putting the library on the Cache drive to see if that improves it. Also, I've deleted all of the old plex instances from the appdata from when I've experimented with it in the past -- so this will be a for sure clean install. I'll report back on how it works.

I recently changed from Limetech's Plex Docker to this one and have found it to be REALLY sluggish compared to the Limetech one. For instance, it takes 15-20 seconds to display the show after clicking on it. Any idea as to why that is or how I can troubleshoot it? My unRAID box has plenty of horsepower so it's not hardware. Thanks!

You can make it show up by typing \\YOURNASNAMEHERE\ in Windows Explorer, then add it to quick access.