Leifgg

I am having some issues when powering down one of my servers, it simply hangs (see the pic). I had just updated the BMC firmware so I thought that could be the problem. I downgraded the firmware but no luck, still same problem. I decided to power down my two other servers and got into same problem. Decided to uninstall the IPMI plugin on all three servers and they all power down as they should. Reinstalling the plugin will bring back the problems again. Can I get some guidance for troubleshooting this pls…. (my signature is updated with current config)

I set 3 GByte as max memory for my 15 TByte and 800.000 files and that works for me. The recommendations looks like a bit "to be on the safe side".

My settings are: <dataDeDupAutoMaxFileSize>1</dataDeDupAutoMaxFileSize> <dataDeDupAutoMaxFileSizeForWan>1073741824</dataDeDupAutoMaxFileSizeForWan> I have disable DataDeDuplication for files above 1073741824 Bytes (1 GByte) since these are often media files that has (more or less) unique content, smaller files gets DeDuplicated. DataDeDuplication use a lot more CPU power so its easy to see what file actually is DeDuplicated. I uploaded 15 TByte in 4 weeks with a 100 Mbit line.

Yes, you can edit the xml file in CrashPlan Pro in the same way.

Thanks @Djoss for the quick fix!

Same problems as @Lebowski Log file attached. CP Container log.txt

My guess is that you have forced an update of the container and that version 4.8.0 is the one embedded in the container (one more guess…). In my case the CrashPlan app notice the old version and updates automatically however have no idea why yours doesn’t behave the same. Sorry...

This container will auto update (or actually the app will). Mine was in June. Check history.log in the log folder. I 06/15/17 12:32PM Downloading a new version of CrashPlan. I 06/15/17 12:32PM Download of upgrade complete - version 1436674800483. I 06/15/17 12:32PM CrashPlan has downloaded an update and will restart momentarily to apply the update. I 06/15/17 12:33PM Installing upgrade - version 1436674800483 I 06/15/17 12:33PM Upgrade installed - version 1436674800483 I 06/15/17 12:33PM CrashPlan started, version 4.8.3

CrashPlan can be used for backups to their cloud or locally to another server. You can probably use the plugin Unassigned Devices to mount a share on the remote server (NAS box). Note(!) that CrashPlan does a backup to a compressed backup archive (not a file backup) so you would need CrashPlan to restore the backup as well, not just a simple file copy.

Release notes for PMS can be found at the Plex forum: https://forums.plex.tv/discussion/62832/plex-media-server#latest The LimeTech Plex Docker container is on Github: https://github.com/limetech/dockerapp-plex

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

No, this worked for me but don't forget to check the settings in the Plex app as well so it finds your files.

Yes, /data refers to the location where you have your media files...

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 don’t believe that this Limetech container supports auto-updating so you might need to wait awhile.