A headless installation of CrashPlan will fail when it tries to update itself.
This short post assumes that you already have it setup and successfully running before, and is targeted only to help you save some time by identifying important files to copy.
Running the installer again will also work, but we actually spend more time to fix the scripts and the identity file might get overwritten causing more time to figure out what happened.
So here goes. This is how we extract the tar archive and the cpio archive within it.
# CrashPlan_3.5.3_Linux.tgz # cd CrashPlan-install # cat CrashPlan_3.5.3.cpi | gzip -dc - | cpio -i --no-preserve-owner
Changed files for 3.4.1 to 3.5.3 (thanks to rsync) are:
lang/txt.properties lang/txt_sv.properties lang/txt_th.properties lang/txt_tr.properties lang/txt_zh.properties lib/com.backup42.desktop.jar lib/com.jniwrapper.jniwrap.jar lib/com.jniwrapper.winpack.jar
All I did was replace those files, and my CrashPlan installation is working fine.
If you actually arrive here to find information on installing for the first time, this post can help you if you’re using a Dlink DNS-32X series. Follow it from start to end (with some adaptation to the paths) and you’ll be fine.
However, you might have to change paths and also do extra steps to get it working. At one point, CrashPlan will run fine but you’ll see that it’s not uploading files.
This post can help you troubleshoot the Java issues by replacing libraries.
From the top of my head I remember having to insert a new library with the correct architecture inside jna-3.2.5.jar, replace libmd5.so, and replace libjtux.so. I also had to link /ffp/usr/local/crashplan/libffi.so.5 to a location accessible by the system loader.