October 12, 201312 yr Based on WalterB's experience as posted in this and another Crashplan related thread, I decided to play with the run.conf file -Xmx values to see if it would make any difference. Crashplan started with a value of 1024m. It also started with a value of 1536m. It did not start with a value of 2048m (this value was fine in RC16c and RC16a). I lowered it to 1900m as WalterB had done; still no joy. I then lowered it to 1800m and Crashplan once again started. In my 4GB system, 1800m seems to be the highest value that will let Crashplan start while running V5.0. I am not sure this will be enough as I am backing up 2.3 TB and it keeps growing. V 5.0 has negatively impacted memory allowed for plugins it appears. It might not be until 64-bit unRaid that we get some relief with a 64-bit Java virtual machine.
October 12, 201312 yr I arrived at the same conclusion. Now I manually backup the media stuff which does not change as much and only use crashplan for documents etc. Hopefully there will be a fix for this in the future.
October 12, 201312 yr Based on WalterB's experience as posted in this and another Crashplan related thread, I decided to play with the run.conf file -Xmx values to see if it would make any difference. Crashplan started with a value of 1024m. It also started with a value of 1536m. It did not start with a value of 2048m (this value was fine in RC16c and RC16a). I lowered it to 1900m as WalterB had done; still no joy. I then lowered it to 1800m and Crashplan once again started. In my 4GB system, 1800m seems to be the highest value that will let Crashplan start while running V5.0. I am not sure this will be enough as I am backing up 2.3 TB and it keeps growing. V 5.0 has negatively impacted memory allowed for plugins it appears. It might not be until 64-bit unRaid that we get some relief with a 64-bit Java virtual machine. How many files? I have a suspicion it's the file count crashplan is sensitive to more than capacity. I'm backing up 2.8TB to one location (75k files) with no problems. 4G memory (virtualised unraid) and -Xmx 512 set.
October 12, 201312 yr How many files? I have a suspicion it's the file count crashplan is sensitive to more than capacity. I'm backing up 2.8TB to one location (75k files) with no problems. 4G memory (virtualised unraid) and -Xmx 512 set. The backup ran and completed the addition of about 750 photos and videos. The total file count is ~77.5k in my 2.2 TB backup set. I got the "Crashplan has been disconnected from the backup engine" error with -Xmx512m shortly after I passed 1.5 TB on the backup set. I increased it to -Xmx2048m at that time and it had been running fine until V5.0 upgrade. Now, -Xmx1800m is the max and it may be sufficient for a while. I am not sure the 1024 per TB suggestion is accurate in all cases.
October 12, 201312 yr What jvm are you using? The one packaged with crashplan or one from an unraid package tool (unmenu etc) ?
October 12, 201312 yr What jvm are you using? The one packaged with crashplan or one from an unraid package tool (unmenu etc) ? I assume it is the JVM packaged with Crashplan as the Crashplan install dowlnoaded java and unMenu shows I have not downloaded and installed the JRE available through unMenu.
October 25, 201312 yr I've made some modifications on the plugin file, basically implemented a kind of backup and some information on the plugin configuration page. https://dl.dropboxusercontent.com/u/18726846/Crashplan.plg
October 26, 201312 yr I've made some modifications on the plugin file, basically implemented a kind of backup and some information on the plugin configuration page. https://dl.dropboxusercontent.com/u/18726846/Crashplan.plg any chance you can add the logs links to the updated plugin? then we won't need the crashplan gui plugin any more...
October 26, 201312 yr I've made some modifications on the plugin file, basically implemented a kind of backup and some information on the plugin configuration page. https://dl.dropboxusercontent.com/u/18726846/Crashplan.plg any chance you can add the logs links to the updated plugin? then we won't need the crashplan gui plugin any more... Yes, of course! Will update when done.
October 29, 201312 yr Hi, Having issues with this plugin, I've been trying to use is within control panel but no sucess and so I'm now running manually and find that the latest version, from a few posts previous (the version doesn't seem to have been updated within it) tries to uninstall later versions of sshd and ssl as it runs. Upgrading openssl-0.9.8r-i486-3 package using /boot/packages/openssl-0.9.8n-i486-1.txz and Upgrading openssh-5.9p1-i486-2_slack13.37 package using /boot/packages/openssh-5.5p1-i486-1.txz I have ssh and ssl installed care of control (v3) All detail from first run below: root@server:/boot/plugins# installplg Crashplan.plg installing plugin: Crashplan file /boot/packages/CrashPlan_3.5.3_Linux.tgz: downloading from http://download.crashplan.com/installs/linux/install/CrashPlan/CrashPlan_3.5.3_Linux.tgz ... 2013-10-29 16:04:00 URL:http://download1.us.code42.com/installs/linux/install/CrashPlan/CrashPlan_3.5.3_Linux.tgz [21404033/21404033] -> "/boot/packages/CrashPlan_3.5.3_Linux.tgz" [1] success file /boot/packages/openssh-5.5p1-i486-1.txz: downloading from http://linorg.usp.br/slackware/slackware-13.1/slackware/n/openssh-5.5p1-i486-1.txz ... 2013-10-29 16:04:04 URL:http://linorg.usp.br/slackware/slackware-13.1/slackware/n/openssh-5.5p1-i486-1.txz [488276/488276] -> "/boot/packages/openssh-5.5p1-i486-1.txz" [1] success upgradepkg --install-new /boot/packages/openssh-5.5p1-i486-1.txz ... +============================================================================== | Upgrading openssh-5.9p1-i486-2_slack13.37 package using /boot/packages/openssh-5.5p1-i486-1.txz +============================================================================== Pre-installing package openssh-5.5p1-i486-1... Removing package /var/log/packages/openssh-5.9p1-i486-2_slack13.37-upgraded-2013-10-29,16:04:04... <snip> --> Deleting empty directory /usr/doc/openssh-5.9p1/ Verifying package openssh-5.5p1-i486-1.txz. Installing package openssh-5.5p1-i486-1.txz: PACKAGE DESCRIPTION: # openssh (Secure Shell daemon and clients) # # ssh (Secure Shell) is a program for logging into a remote machine and # for executing commands on a remote machine. It is intended to replace # rlogin and rsh, and provide secure encrypted communications between # two untrusted hosts over an insecure network. sshd (SSH Daemon) is # the daemon program for ssh. OpenSSH is based on the last free version # of Tatu Ylonen's SSH, further enhanced and cleaned up by Aaron # Campbell, Bob Beck, Markus Friedl, Niels Provos, Theo de Raadt, and # Dug Song. It has a homepage at http://www.openssh.com/ # Executing install script for openssh-5.5p1-i486-1.txz. Package openssh-5.5p1-i486-1.txz installed. Package openssh-5.9p1-i486-2_slack13.37 upgraded with new package /boot/packages/openssh-5.5p1-i486-1.txz. success file /boot/packages/openssl-0.9.8n-i486-1.txz: downloading from http://linorg.usp.br/slackware/slackware-13.1/slackware/n/openssl-0.9.8n-i486-1.txz ... 2013-10-29 16:04:19 URL:http://linorg.usp.br/slackware/slackware-13.1/slackware/n/openssl-0.9.8n-i486-1.txz [2353628/2353628] -> "/boot/packages/openssl-0.9.8n-i486-1.txz" [1] success upgradepkg --install-new /boot/packages/openssl-0.9.8n-i486-1.txz ... +============================================================================== | Upgrading openssl-0.9.8r-i486-3 package using /boot/packages/openssl-0.9.8n-i486-1.txz +============================================================================== Pre-installing package openssl-0.9.8n-i486-1... Removing package /var/log/packages/openssl-0.9.8r-i486-3-upgraded-2013-10-29,16:04:19... --> Deleting /usr/doc/openssl-0.9.8r/CHANGES <snip> --> Deleting empty directory /usr/doc/openssl-0.9.8r/ Verifying package openssl-0.9.8n-i486-1.txz. Installing package openssl-0.9.8n-i486-1.txz: PACKAGE DESCRIPTION: # openssl (Secure Sockets Layer toolkit) # # The OpenSSL certificate management tool and the shared libraries that # provide various encryption and decryption algorithms and protocols. # # This product includes software developed by the OpenSSL Project for # use in the OpenSSL Toolkit (http://www.openssl.org). This product # includes cryptographic software written by Eric Young # ([email protected]). This product includes software written by Tim # Hudson ([email protected]). # Executing install script for openssl-0.9.8n-i486-1.txz. Package openssl-0.9.8n-i486-1.txz installed. Package openssl-0.9.8r-i486-3 upgraded with new package /boot/packages/openssl-0.9.8n-i486-1.txz. success file /boot/packages/cpio-2.9-i486-2.txz: downloading from http://linorg.usp.br/slackware/slackware-13.1/slackware/a/cpio-2.9-i486-2.txz ... 2013-10-29 16:04:25 URL:http://linorg.usp.br/slackware/slackware-13.1/slackware/a/cpio-2.9-i486-2.txz [132368/132368] -> "/boot/packages/cpio-2.9-i486-2.txz" [1] success upgradepkg --install-new /boot/packages/cpio-2.9-i486-2.txz ... +============================================================================== | Installing new package /boot/packages/cpio-2.9-i486-2.txz +============================================================================== Verifying package cpio-2.9-i486-2.txz. Installing package cpio-2.9-i486-2.txz: PACKAGE DESCRIPTION: # cpio (backup and archiving utility) # # This is GNU cpio, a program to manage archives of files. This package # also includes mt, a tape drive control program. cpio copies files into # or out of a cpio or tar archive, which is a file that contains other # files plus information about them, such as their pathname, owner, # timestamps, and access permissions. The archive can be another file on # the disk, a magnetic tape, or a pipe. # Package cpio-2.9-i486-2.txz installed. success file /boot/config/plugins/CrashPlan/CrashPlan.png: downloading from http://lime-technology.com/wiki/images/5/59/Crashplan.png ... 2013-10-29 16:04:26 URL:http://lime-technology.com/wiki/images/5/59/Crashplan.png [2628/2628] -> "/boot/config/plugins/CrashPlan/CrashPlan.png" [1] success file /boot/config/plugins/CrashPlan/CrashPlan.cfg: successfully wrote INLINE file contents file /tmp/CrashPlan-upgrade: successfully wrote INLINE file contents /bin/bash /tmp/CrashPlan-upgrade ... success file /usr/local/emhttp/plugins/CrashPlan/CrashPlan.png: successfully copied LOCAL file file /usr/local/emhttp/plugins/CrashPlan/CrashPlan.page: successfully wrote INLINE file contents file /usr/local/emhttp/plugins/CrashPlan/CrashPlan.php: successfully wrote INLINE file contents file /usr/local/emhttp/plugins/CrashPlan/CrashPlanctl.php: successfully wrote INLINE file contents file /usr/local/emhttp/plugins/CrashPlan/event/disks_mounted: successfully wrote INLINE file contents successfully changed file mode file /usr/local/emhttp/plugins/CrashPlan/event/stopping_svcs: successfully wrote INLINE file contents successfully changed file mode file /var/log/plugins/CrashPlan: successfully wrote INLINE file contents plugin successfully installed
November 12, 201312 yr Crashplan will install manually and run but any reboot will cause emhttp to not respond.
Archived
This topic is now archived and is closed to further replies.