Crashplan "Could not find JAR file" since 6.5 update

Hi,

Interestingly I had this issue, and thought it was because of the 6.5 update, but turn out to be a Crashplan update that came out at almost the same time, the Crashplan update borked itself.

Anyway here are the high level steps I took to recover.

Replace busybox-cpio with cpio (that is why the crashplan update failed)

# apt-get install cpio

Download the latest Crashplan into home

# cd
# wget https://download2.code42.com/installs/linux/install/CrashPlan/CrashPlan_4.7.0_Linux.tgz

Extract

# tar zxf CrashPlan_4.7.0_Linux.tgz

cd into the extracted dir

# cd crashplan-install/

Now you will need to run the uninstall script and then the install script.

Note - Make sure when you run the install script that you put Crashplan where ever you had it before, eg for me I just use the default installer locations but have a softlink from /usr/local/crashplan to /data/crashplan so it isn't taking space from the root volume. Also note that something (or someone) deleted my crashplan backups on this NAS from my other local machines, I don't have enough evidence to determine if the Crashplan upgrade script did something, I did something accidently or who knows. Anyway this time I created a backup share via the NAS interface disabling any sharing (since it is just for crashplan to store local backups from friends) and put a custom snapshot schedule on it for three months, then used this as my backup location when setting up crashplan again ie /data/backup. Of course if you only backup to the Crashplan cloud this doesn't really matter.

You will also note the install script downloads and sets up JAVA as required for you, reasonably slick.

Uninstalling (you need to know the base dir where crashplan is installed (the below is the default location)

# ./uninstall.sh -i /usr/local/crashplan

Reinstalling

# ./install.sh

This should cleanly install and start up Crashplan.

Of course the next bit of fun is connectioning to the headless Crashplan. Since you have reinstalled you will need to grab the new UUID from .ui_info

# cd /var/lib/crashplan
# cat .ui_info

You will see something like this
4243,185c81b6-4759-4c22-9487-be5e1dc4c051,127.0.0.1

If you are using an SSH tunnel to port forward you can just copy the second part eg 185c81b6-4759-4c22-9487-be5e1dc4c051 (yours will be unique). You need this identifier to connect remotely, since you are already using Crashplan I will assume you are across how to do this. I use UISwitcher 1.4 to flick between my Windows PC local Crashplan and Crashplan on my NAS.

Cheers

Steve