Changes

From Amahi Wiki
Jump to: navigation, search
401 bytes added ,  00:15, 12 May 2017
You now should be able to administer CrashPlan using your HDA as the local storage location.
==CrashPlan Desktop Java RTE Errors==If you use the CrashPlan desktop on version 3.5.3 you may experience a Java error - when starting the Crashplan desktop the splash image shows for a few seconds, and then vanishes, but the application doesn't open. It appears that CrashPlan 3.5.3 bundles a buggy version of the "Eclipse Standard Widget Toolkit". To fix, you just need to replace that toolkit with the latest one from the developer. * Download swt-4.3-gtk-linux-x86.zip and swt-4.3-gtk-linux-x86_64.zip from [http://download.eclipse.org/eclipse/downloads/drops4/R-4.3-201306052000/#SWT Eclipse].  * Extract swt.jar from the x86_64 file and rename it as swt-64.jar, and extract swt.jar from the second file. I saved them both to the home directory. (You can do this from terminal from the directory in which you saved the .zip files): unzip -e swt-4.3-gtk-linux-x86_64.zip swt.jar -d ~ mv ~/swt.jar ~/swt-64.jar unzip -e swt-4.3-gtk-linux-x86.zip swt.jar -d ~ Then you need to copy these to the CrashPlan library. On my HDA CrashPlan was installed to /var/hda/web-apps/crashplan/html. If your installation is different you will need to replace the commands below this your directory. * Stop the crashplan server sudo systemctl stop crashplan.service * Back up the old files and copy in the new ones (change the directory path to your own if it is different and remember to put the /lib at the end): cd /var/hda/web-apps/crashplan/html/lib mv swt.jar swt.jar.old mv swt-64.jar swt-64.jar.old mv ~/swt.jar swt.jar mv ~/swt-64.jar swt-64.jar * Restart the crashplan systemctl start crashplan.service Should be working now. [Source: [https://forums.amahi.org/viewtopic.php?f=26&t=4951 this forum post]] ==Amahi 8/9 /10 (Fedora 21/23/25)==
See [https://support.code42.com/CrashPlan/4/Configuring/Using_CrashPlan_On_A_Headless_Computer Using CrashPlan On A Headless Computer] for guidance.
It requires you to install CrashPlan on your client computer, manually editing a config file, and using SSH port forwarding.
 
= Troubleshooting =
==CrashPlan Desktop Java RTE Errors==
If you use the CrashPlan desktop on version 3.5.3 you may experience a Java error - when starting the Crashplan desktop the splash image shows for a few seconds, and then vanishes, but the application doesn't open.
 
It appears that CrashPlan 3.5.3 bundles a buggy version of the "Eclipse Standard Widget Toolkit". To fix, you just need to replace that toolkit with the latest one from the developer.
 
* Download swt-4.3-gtk-linux-x86.zip and swt-4.3-gtk-linux-x86_64.zip from [http://download.eclipse.org/eclipse/downloads/drops4/R-4.3-201306052000/#SWT Eclipse].
 
* Extract swt.jar from the x86_64 file and rename it as swt-64.jar, and extract swt.jar from the second file. I saved them both to the home directory. (You can do this from terminal from the directory in which you saved the .zip files):
unzip -e swt-4.3-gtk-linux-x86_64.zip swt.jar -d ~
mv ~/swt.jar ~/swt-64.jar
unzip -e swt-4.3-gtk-linux-x86.zip swt.jar -d ~
 
Then you need to copy these to the CrashPlan library. On my HDA CrashPlan was installed to /var/hda/web-apps/crashplan/html. If your installation is different you will need to replace the commands below this your directory.
 
* Stop the crashplan server
sudo systemctl stop crashplan.service
 
* Back up the old files and copy in the new ones (change the directory path to your own if it is different and remember to put the /lib at the end):
cd /var/hda/web-apps/crashplan/html/lib
mv swt.jar swt.jar.old
mv swt-64.jar swt-64.jar.old
mv ~/swt.jar swt.jar
mv ~/swt-64.jar swt-64.jar
 
* Restart the crashplan
systemctl start crashplan.service
 
Should be working now.
 
[Source: [https://forums.amahi.org/viewtopic.php?f=26&t=4951 this forum post]]
 
== Too many inotify watches ==
You may see messages in other apps that there is "No space left on device" but you have enough disk space .. it may be that Crashplan is issuing too many inotify watches.
 
Some processes may report "No space left on device" when this happens. there is a possible work-around for this in Amahi [https://bugs.amahi.org/issues/2091 Bug # 2091].
12,424

edits