Leifgg

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

I use SyncBack to backup my desktop PC to an unRAID share on my Main system. I use rsync to backup my Main system to my Backup system. I backup user shares and have split levels setup on my backup system. I did a post long time ago in this thread about my rsync setup. I believe I have made some minor changes since then but you should at least get some hints on how to use rsync. http://lime-technology.com/forum/index.php?topic=38554.msg358683#msg358683 Pls remember that rsync is very powerful and not very forgiving so use the option “--dry-run” to test the script first. Search the web for some guides before you start using rsync.

There are a number of different things that influences the speed of the backup. The most obvious ones are our own bandwidth and the CPU allocated. CrashPlan uses compression and data deduplication to reduce the amount of data being sent (CrashPlan puts your files in a compressed backup archive). Compression doesn’t use that much resources but data deduplication will, especially if you have a lot of data already backed up. Another factor is the load on the server that you are backing up to (if there are many simultaneous users or not). If have 100 Mbit bandwidth and my backup speed can range from 5 Mbit up to almost 100 Mbit to the CrashPlan cloud (11 TByte of data stored). The speed you see does indicate that there is something fundamentally wrong. Even if CrashPlan doesn’t give support for specific questions related to Docker installation they will be able to provide general support so it might be good to contact them. They will respond within a few days normally for non-urgent matters. You are mentioning that that you backup from one device to another and then to the CrashPlan cloud. If you are doing that, this article might be useful. http://support.code42.com/CrashPlan/4/Backup/Can_I_Back_Up_A_Backup

If you are using Docker, Plex uses a folder structure located in the appdata share (locate on the cache drive or the array) to store metadata, database and other stuff. If folder mappings are correctly setup nothing should be stored within the container. Transcoding is negotiated between the server and the client and transcoding is used if needed to play the content. Haven’t seen any possibility to disable it on the server but some clients can be set to disable transcoding.

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

Also a CrashPlan (cloud) user for more than 2 years. It fulfils my requirements of having a backup at a remote location as well as having versions of my files. Personally I see this as a “disaster recovery” alternative since I have backups on my local backup server as well as on a dedicated set of disks on my main server (but none of these handle different file versions). You can use CrashPlan for local backups and it works well but the design of the app is for cloud backup and local backups is a “bonus feature”. CrashPlan stores your files in a compressed backup archive so you will need to have the app installed to restore a backup. This is one reason why I don’t use it for local backups. If you chose the “free” app (for local backups only) there is also a number of limitations that you should be aware of, one of them is having versions of files. CrashPlan provides a lot of information on their support pages so have a look there and you can also have a 30-day trial to play with it the get a feel on how it works.

I can’t see any obvious reason but it might be that you are running out of memory. Suggest having a look in the service.log (the latest one) and search for OutOfMemoryError. You can find the log files in the log folder for CrashPlan in your appdata share.

Older releases (than 1.0) is no longer supported and has been removed from the file archive. Read more at the Plex Forum: http://forums.plex.tv/discussion/62832/plex-media-server#latest

There are several reports about issues with watched status at the Plex forum. Some clients works fine but a few have this issue.

According to Plex Release Announcement: Plex Media Server 1.0.0 is now available for everyone

Guess that everybody more or less have unique needs? Personally I have a daily local backup of all my data on a separate disk set on my main server as well as a daily backup (using rsync) on my backup server. In addition, I use CrashPlan and have a full backup there as well but I prefer to see that as a disaster recovery option since it would take ages to restore a complete backup.

Thanks, I'll check it out tonight. However, it still doesn't let me know how much RAM is actually used by the docker. Nope, CrashPlan doesn’t let you know how much it uses. The sign when it’s running out of memory is that the backup never get ready and it’s starting all over again, and again... I think that there are other ways to get the resource usage, can check when I get back home… You can try the Netdata and cAdvisor Docker containers. These can be used to monitor CPU and RAM usage. I have them installed but haven’t had much time to play with them.

Thanks, I'll check it out tonight. However, it still doesn't let me know how much RAM is actually used by the docker. Nope, CrashPlan doesn’t let you know how much it uses. The sign when it’s running out of memory is that the backup never get ready and it’s starting all over again, and again... I think that there are other ways to get the resource usage, can check when I get back home…

How did you configure? And how did you know Crashplan only uses 3GB? Check this thread to set max memory usage. http://lime-technology.com/forum/index.php?topic=33864.msg454520#msg454520