CrashPlan Issue For Synology – Fixing the 4.3.0 update
If your Synology NAS can run docker, you may want to consider an alternative to the CrashPlan package. See here: CrashPlan and CrashPlan Pro on Synology using Docker
Note, see bottom of page for information on DSM 6 and CrashPlan 4.6.0
Recently CrashPlan updated to version 1427864400430, which broke the CrashPlan package Patters had created for Synology installations again. They then (July 2nd?) released 1427864410430 as well, which means that if your CrashPlan installation on Synology broke with version 1427864400430, you will need to upgrade, wait for it to break again, and then fix with version 1427864410430. In general the fix process has been the same over the last few breaks, and I’ve outlined those steps below for the latest version.
There is one major change introduced from CrashPlan. Starting with the 1427864400430 update, a guid (think of it as a key) is needed to securely log into the headless client. Thanks to Mathew Stocks, I’ve made those instructions available as well.
The log for the failing CrashPlan package would look something like this for a failing 1427864400430 upgrade:
Upgrades available at central.crashplan.com:443
Downloading a new version of CrashPlan.
Download of upgrade complete – version 1427864400430.
Installing upgrade – version 1427864400430
Upgrade installed – version 1427864400430
CrashPlan stopped, version 4.2.0, GUID 559750658046558476
If the package was attempted to start again, it would write a line similar to the following, and then stop:
Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1427864400430.
Note that the following instructions are for the 1427864410430 upgrade, which is the latest (as of July 2nd, 2015) update. If your Synology didn’t make it to this version, run the following steps, but substitute “1427864400430” where there are any references to “1427864410430”.
Connect as root to SSH
First, connect to Synology using SSH and the root account (uses admin password). Connecting as the admin account will give you permission failures!
In SSH, run commands to extract the update
unzip -o /var/packages/CrashPlan/target/upgrade/1427864410430.jar "*.jar" -d /var/packages/CrashPlan/target/lib/
unzip -o /var/packages/CrashPlan/target/upgrade/1427864410430.jar "lang/*" -d /var/packages/CrashPlan/target/
In SSH, run unique command to cleanup the package
The next command will be different for everyone, as part of the file path is randomized. In this case, you will need to see what your path is first by running ls, and then editing the second statement below, replacing whatevervalue with the rest of your path:
ls -l /var/packages/CrashPlan/target/upgrade/1427864410430.*
mv /var/packages/CrashPlan/target/upgrade/1427864410430.whatevervalue/upgrade.sh /var/packages/CrashPlan/target/upgrade/1427864410430.whatevervalue/upgrade.sh.old
Start CrashPlan package, check log
After the above completes, you should be able to start the CrashPlan package again in Synology and get it running once more. The log should show:
CrashPlan started, version 4.3.0 GUID 559750658046558476
Get the headless key from the .ui_info file
While connected to SSH as root, run the following command to get the headless key file. The funky formatting of this command is because the file does not contain the special newline character:
cat /var/lib/crashplan/.ui_info ; echo
The command will output a line similar to the following (everyone’s will be different):
Update .ui_info on the computer connecting to Synology
On the computer where you are connecting to CrashPlan on Synology, go to the .ui_info file under the CrashPlan directory. NOTE: I had to manually upgrade my computer’s version of CrashPlan (via https://www.code42.com/crashplan/thankyou/) in order to see the .ui_info file.
Typically on Windows, this will be found under:
Or on a Mac in the following location (need to have finder set to show hidden files):
Enter in the new key in the file, replacing the current value, and save it. You should now able able to connect to the headless client. Note that you may need to also update the values in ui.properties again if you had to upgrade CrashPlan.
There are some tools referenced in the comments for this page which might make upgrades easier for some people. But I’ll also give the latest files & paths using the original instructions above – the following commands can be used for v4.6.0:
unzip -o /var/packages/CrashPlan/target/upgrade/1435813200460_382.jar "*.jar" -d /var/packages/CrashPlan/target/lib/
unzip -o /var/packages/CrashPlan/target/upgrade/1435813200460_382.jar "lang/*" -d /var/packages/CrashPlan/target/
Find latest package folder:
ls -l /var/packages/CrashPlan/target/upgrade/1435813200460_382.*
Replace the whatevervalue with the folder name:
mv /var/packages/CrashPlan/target/upgrade/1435813200460_382.whatevervalue/upgrade.sh /var/packages/CrashPlan/target/upgrade/1435813200460_382.whatevervalue/upgrade.sh.old
Synology DSM v6
I don’t recommend upgrading to v6 at this time (March 2016) if you do not have an Intel based CPU in your Synology NAS as there have been issues reported with the java packages in the comments here as well as on Patter’s page. If you do have an Intel based CPU you will need to use 7z commands on DSM6 instead of zip commands. Examples for CrashPlan 4.6.0:
sudo 7z e -y -o/var/packages/CrashPlan/target/lib /var/packages/CrashPlan/target/upgrade/1435813200460_382.jar "*.jar"
sudo 7z e -y -o/var/packages/CrashPlan/target/lang /var/packages/CrashPlan/target/upgrade/1435813200460_382.jar "lang/*"