Leifgg
-
Posts
408 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Leifgg
-
-
14 hours ago, cmer said:
So far so good with 3GB! Thanks again.
It should be possible to change the settings from the CrashPlan GUI as well (but that never worked for me):
Happy to hear that its working again...
-
18 hours ago, cmer said:
What's the easy way to allocate more ram to Java? (if there is)
This constantly crashes my machine unfortunately. Well know problem for Java apps...
http://www.geert.io/java-freezing-due-to-garbage-collector.html
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.
-
1 hour ago, MrChunky said:
I am having several "issues" with the docker.
Firstly, I would like to clarify whether crashplan is supposed to run only on a single core? I see it pinning a single core to whatever I will allow it and moving on to another etc. Is there anyway to allow for multicore process.
Secondly, once in a while I get an issue with UnRaid becoming unresponsive due to large iowait values. I have narrowed the issue down to crashplan docker, however I have no idea where the crazy io requests are coming from. THe problem is usually solved by restarting the docker. I attach the docker logs.
Would be great if someone could chime in on those issues...
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...
-
18 hours ago, DoeBoye said:
I'm assuming it saves it to the config and doesn't need to be re-done on reboot, right?
Yepp, it will survive a reboot. The change you made is stored in the file run.conf located here: appdata\Chrasplan\bin
-
1
-
-
5 minutes ago, Carmico said:
ok, so there's no need to create a new path /Media
thanks
No, this worked for me but don't forget to check the settings in the Plex app as well so it finds your files.
-
14 hours ago, Carmico said:
what's the container /data stand for on Plex Docker (official repository) ?
i'm using UnassignedDevice (ssd nvme) for dockers & vms , so i move everything to that device , but don't know on Plex docker what's /data mean
for /transcode i put /tmp tu use Ram
for /config i put my appdata folder on the UnassignedDevice
for Media, i add a new map so /Media point to share /Media on my array
but for /data ?... or data refers to Media ?
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.-
1
-
-
6 hours ago, aptalca said:
This thread links to stable builds for arm but you can at least see the full version numbers in the links (I'm assuming the version numbers are the same for arm and x86-64):
Version 1.5.4 was released today.
-
11 hours ago, BillyPrefect said:
I just created an account to say thanks for the /tmp to /transcode translation. I was banging my head against the monitor trying to figure out why Plex wasn't working anymore. I tried making a separate directory, making a specific sized dataset, making it part of a config file, all sorts of things. Found this blog entry and thought, why not, I've tried everything else... now running like it was when it was it's own machine again. Thanks much.
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.
-
10 hours ago, wgstarks said:
How much ram is really needed for this? I saw a previous post that it would need more ram than the largest video file because plex stores the entire file in the transcode. I don't know if that's true or not. For me that would mean something like 40GB+. Seems excessive and my motherboard maxs out at 32GB.
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.
-
5 hours ago, andr3ws said:
hi, I've tried to use the search function and it won't pull up any new results for what I'm looking for (older releases). the problem is everytime i need to reboot the unraid server the crashplan engine comes back with an error unable to connect to back up engine, retry and i could click retry for days. finally i have to delete the app and reinstall in order to get it to work, then have to re-adopt my backup and wait for it to sync.
any help would be appreciated.
thanks
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.
-
On 2017-03-07 at 8:53 PM, bobekdj said:
UPDATE: May actually be a RAM issue causing it to crash since my backup was large... Increased to 5GB of ram, and we will see if it works.
Need some help, my crashplan keeps crashing while trying to backup. I lost my cache drive and subsequently was not backing up my appdata folder (shame on me)
since then i made a new docker, used community app to redownload CP, and then set it up from scratch again, choosing to restore from a previous PC option to sync the data.
not sure what any of this means, but have been getting this similar error over and over
any help is appreciated.
Think the key is "ERROR: openbox-xdg-autostart requires PyXDG to be installed"
Xvnc TigerVNC 1.7.0 - built Sep 8 2016 10:39:22 Copyright (C) 1999-2016 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC. Underlying X server release 11400000, The X.Org Foundation Initializing built-in extension VNC-EXTENSION Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension GLX Tue Mar 7 15:48:58 2017 vncext: VNC extension running! vncext: Listening for VNC connections on all interface(s), port 4239 vncext: created VNC server for screen 0 Warning: could not find self.pem Using local websockify at /opt/novnc/utils/websockify/run Starting webserver and WebSockets proxy on port 4280 ERROR: openbox-xdg-autostart requires PyXDG to be installed WebSocket server settings: - Listen on :4280 - Flash security policy server - Web server. Web root: /opt/novnc - No SSL/TLS support (no cert file) - proxying from :4280 to localhost:4239 Mar 7 15:48:58 unRAID syslog-ng[31]: syslog-ng starting up; version='3.5.6' Navigate to this URL: http://unRAID:4280/vnc.html?host=unRAID&port=4280 Press Ctrl-C to exitDon’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.
-
Just noticed this too. Didn't have as solution on how to update to the latest public version...
Just tried deleting the "PUBLIC" variable from the docker settings, resorted the docker, and the Plex Server settings are still telling me to install manually...
Looks like the server file isn't posted as per my server logs..
Atempting to upgrade to: https://downloads.plex.tv/plex-media-server/%20/plexmediaserver_%20_amd64.deb: 2017-02-02 08:41:07 ERROR 404: Not Found.
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
-
Just noticed this too. Didn't have as solution on how to update to the latest public version...
Just tried deleting the "PUBLIC" variable from the docker settings, resorted the docker, and the Plex Server settings are still telling me to install manually...
Looks like the server file isn't posted as per my server logs..
Atempting to upgrade to: https://downloads.plex.tv/plex-media-server/%20/plexmediaserver_%20_amd64.deb: 2017-02-02 08:41:07 ERROR 404: Not Found.
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.
-
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.
-
Hey, does anyone know how to use the clipboard copy/paste function? I need to paste in my very looooong encryption key and when I type it it says invalid so I must be messing it up. I can paste the text into the clipboard text box, but when I right-click within the crashplan app I cannot select paste.
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
-
Try to update again. That solved it for me.
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
Just updated the crashplan docker and it is not starting. This is what the logs show over and over
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.
-
Just updated the crashplan docker and it is not starting. This is what the logs show over and over
Sat Oct 1 14:16:32 2016 vncext: VNC extension running! vncext: Listening for VNC connections on all interface(s), port 4239 vncext: created VNC server for screen 0 XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. Fatal server error: Failed to activate core devices. Openbox-Message: Failed to open the display from the DISPLAY environment variable. Must have netstat installed _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/Tower:1 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root Xvnc TigerVNC 1.7.0 - built Sep 8 2016 10:39:22 Copyright (C) 1999-2016 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC. Underlying X server release 11400000, The X.Org Foundation Initializing built-in extension VNC-EXTENSION Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension GLX Sat Oct 1 14:16:34 2016 vncext: VNC extension running! vncext: Listening for VNC connections on all interface(s), port 4239 vncext: created VNC server for screen 0 XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. Fatal server error: Failed to activate core devices. Openbox-Message: Failed to open the display from the DISPLAY environment variable. Must have netstat installed _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/Tower:1 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root Xvnc TigerVNC 1.7.0 - built Sep 8 2016 10:39:22 Copyright (C) 1999-2016 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC. Underlying X server release 11400000, The X.Org Foundation Initializing built-in extension VNC-EXTENSION Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension GLX
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
[Support] Linuxserver.io - Plex Media Server
in Docker Containers
Posted
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