Leifgg

Tell us a bit more about the actual problem. Normally Plex plugins are in the Plug-ins folder that should be located outside the Docker container in the appdata share where configuration data for the containers are stored. On my system that is appdata/Plex/Library/Application Support/Plex Media Server/Plug-ins/Sub-Zero.bundle I am using Sub-Zero myself without problems and installed as described in the wiki: https://github.com/pannal/Sub-Zero.bundle/wiki

It should be possible to change the settings from the CrashPlan GUI as well (but that never worked for me): https://support.code42.com/CrashPlan/4/Troubleshooting/Adjust_CrashPlan_settings_for_memory_usage_with_large_backups Happy to hear that its working again...

What I do is to edit the file run.conf in bin folder (mine is located here: appdata/CrashPlan/bin) Stop CrashPlan and edit the first line with a Linux editor (Notepad++): SRV_JAVA_OPTS="-Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m -Xmx3072m I have set it to 3072 (3GB), think the default is 1024 (1 GB). This is not actually allocated, it’s the limit on how much CrashPlan can allocate if needed. This works for my 800.000 files, 14 TB.

Firstly, I have been running CrashPlan for a bit more than two years but I am unfortunately not able to give much help but here are my thoughts… The CrashPlan Java app is developed and maintained by CrashPlan and gfjardim (the maintainer of this Docker container) downloads the app and make the adaptations needed for this Docker container. I would assume that any adaptation for multicore processes I best done by CrashPlan. Regarding the inotify problems I can only say that I haven’t seen them myself and I have around 450.000 files (12 TBytes). From what I can see from your logs there are a lot related to Plex and I don’t have any of these errors in my logs (I use Plex as well). Here is a link that talks about inotify: https://support.code42.com/CrashPlan/4/Troubleshooting/Linux_Real-Time_File_Watching_Errors The only thoughts I have about this is if it could be related to permissions (access rights) to the files on the appdata share? And BTW, some of the log files you provided contains (sensitive) personal information so you might prefer to edit your post...

Yepp, it will survive a reboot. The change you made is stored in the file run.conf located here: appdata\Chrasplan\bin

This is for those that would like to install a previously installed Plex version by changing the Version variable.... Have a look in the appdata share and go to: Plex\Library\Application Support\Plex Media Server\Crash Reports You will find folders for previous installed versions (and current) and use these folder names for the Version variable.

Version 1.5.4 was released today.

There has been a lot of changes made to the Plex transcoder since this thread was started. I assume you a running Plex in a Docker container, then the easiest way to get it to work is to transcode to disk and then preferably an SSD. You need to setup the Plex container with a mapping to a folder and also specify the mount point to this folder in the Plex app. Plex does a lot of logging so it might be worth to check the Plex Media Server log for errors (not the container log). Suggest you also look at the Plex forum, there as a lot of questions about transcoding there.

You can make a test and monitor the folder where Plex stores the transcoded data, play a file and see what you get. Keep in mind that if there are several users there might be more data than only yours.

It’s hard to give good suggestions without more details. Do you use the CrashPlan Docker container? Has it been working in the past? When did this problem start to occur? Are you backing up to the CrashPlan cloud or to a local or remote folder? There are a lot of different log files related to backup, restore, backup service and history. They are located in the log folder. Open the most recent ones and search for Errors to see if you can get some useful information out of that. CrashPlan also have support pages that can be useful to search trough.

Don’t think you need to worry about the errors in the log, I see the same but CrashPlan works flawlessly regardless of them ….

I have allocated 3 GB memory (1 GB is default) and that works fine for me with 12 TB in one backup set. It doesn’t hurt to allocate more memory since CrashPlan only uses what’s needed.

I'm getting the same message in my logs. Is this Plex or container related? From my quick glance at the logs looks like the plex version number seems to be missing - instead it's been replaced with %20 in the file name. Strange, I don’t see this behavior in my logs. Atempting to upgrade to: 1.3.4.3285-b46e0ea 2017-02-02 16:21:43 URL:https://downloads.plex.tv/plex-media-server/1.3.4.3285-b46e0ea/plexmediaserver_1.3.4.3285-b46e0ea_amd64.deb [101364400/101364400] -> "/tmp/plexmediaserver_1.3.4.3285-b46e0ea_amd64.deb" [1] (Reading database ... 10918 files and directories currently installed.) Preparing to unpack .../plexmediaserver_1.3.4.3285-b46e0ea_amd64.deb ... /var/lib/dpkg/info/plexmediaserver.prerm: 13: /var/lib/dpkg/info/plexmediaserver.prerm: stop: not found Unpacking plexmediaserver (1.3.4.3285-b46e0ea) over (1.3.3.3148-b38628e) ... Setting up plexmediaserver (1.3.4.3285-b46e0ea) ... Processing triggers for systemd (229-4ubuntu13) ... [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server. What unRAID version are you running? I am on 6.3.0-rc9

I'm getting the same message in my logs. Is this Plex or container related? From my quick glance at the logs looks like the plex version number seems to be missing - instead it's been replaced with %20 in the file name. Strange, I don’t see this behavior in my logs. Atempting to upgrade to: 1.3.4.3285-b46e0ea 2017-02-02 16:21:43 URL:https://downloads.plex.tv/plex-media-server/1.3.4.3285-b46e0ea/plexmediaserver_1.3.4.3285-b46e0ea_amd64.deb [101364400/101364400] -> "/tmp/plexmediaserver_1.3.4.3285-b46e0ea_amd64.deb" [1] (Reading database ... 10918 files and directories currently installed.) Preparing to unpack .../plexmediaserver_1.3.4.3285-b46e0ea_amd64.deb ... /var/lib/dpkg/info/plexmediaserver.prerm: 13: /var/lib/dpkg/info/plexmediaserver.prerm: stop: not found Unpacking plexmediaserver (1.3.4.3285-b46e0ea) over (1.3.3.3148-b38628e) ... Setting up plexmediaserver (1.3.4.3285-b46e0ea) ... Processing triggers for systemd (229-4ubuntu13) ... [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server.

Updated to latest version (1.3.4.3285) by restarting the Container. This release is available for everyone. The Container Variable: VERSION set to latest.

One of the updates that Plex did related to Transcoding is that the app actually will check available space before starting the Transcoding. This post (post 18 from ChuckPa) is about converting files but Plex might do a similar check during normal playback as well. http://forums.plex.tv/discussion/244822/conversion-failed-a-required-codec-could-not-be-found-or-failed-to-install-a-bad-update#latest

Suggest start reading from here: http://lime-technology.com/forum/index.php?topic=42148.555

You can find release announcement for PMS at the Plex forum. Version 1.2.7 is currently the latest and is available to everyone. Plex DVR releases are not available as main release or Plex Pass release. The DVR releases needs to be installed manually and are available for Plex Pass users.

This Docker is for CrashPlan Home. If you have a subscription you can do backup to the CrashPlan cloud. Suggests checking directly with their support if this app is compatible with CrashPlan PRO.

You can restore to another share or folder. Go to Restore and select "a folder" then click "nobody" and browse for the location you prefer.

Save your key file in a txt file and import it from there. It need to be in a location that CrashPlan can see like /appdata/crashplan/...... Sent from my SGP771 using Tapatalk

Yup, Latest update fixed the issue for me also Does this mean that there haw been an additional CrashPlan update since and that the 2nd fix took care of whatever the issue was in the first fix, or does it mean that it took 2 installs of the first (and only recent) fix to make it work? Also, what's been fixed/updated? I'm only 48GB into a 1TB photo backup, and it took several days for CP to settle itself down and actually start making progress. I don't want to kill off the backup if it's for something minor that won't really impact me. Many, many thanks to gfjardim for getting this docker working in the first place! Probably the first build was broken and gfjardim did a new build to fix that. Don’t know if there are any specific changes other that the container now has the latest release (4.8.0) of the CrashPlan app. Suggest updating, regardless the CrashPlan app will auto-update itself to the latest version.

I just updated by Crashplan Docker and I'm having the same problem. I have the same problem. Just updated CP and VNC connection is not working and CP client also can't connect to server. Try to update again. That solved it for me. Sent from my SGP771 using Tapatalk

FYI, might be good for people to keep an eye on the CrashPlan Docker container if this update affects you as well. My CrashPlan Docker container did auto update itself today to version 4.8.0 My Custom key did not “survive” the update so I needed to re-enter it to get it running again.

Having a similar problem. Can’t find Dockers and VM on my Xperia Z4 tablet. However, it works on my Xperia Z1 tablet and on my OnePlus2 phone. Edit: clear cache and reinstall solved this