The latest round of updates from CrashPlan (4.3.0) has broken the CrashPlan package on Synology again. Please see http://chrisnelson.ca/2015/07/02/fixing-crashplan-4-3-0-on-synology/ for the newest instructions.
Archived information for 4.2:
After installing Synology DSM 5.2, CrashPlan recently pushed an update (4.2.0) which broke the CrashPlan package Patters had created for Synology. The log for the failing CrashPlan package would look something like this:
CrashPlan started, version 3.7.0, GUID 559750658046558476
Upgrades available at central.crashplan.com:443
Downloading a new version of CrashPlan.
Download of upgrade complete – version 1425276000420.
Installing upgrade – version 1425276000420
Upgrade installed – version 1425276000420
CrashPlan stopped, version 3.7.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/1425276000420.
This seemed to be similar to the previous issue seen in 3.7.0, so I used the following steps to fix crashplan on my synology box: Note that this will likely be fixed by Patters soon, this is just a workaround if your CrashPlan install has stopped as a result of the 4.2.0 update.
Connect as root to SSH
First, connect to Synology using SSH and the root account (uses admin password). Connecting as the admin account will not give you enough permissions.
In SSH, run commands to extract the update
unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar *.jar -d /var/packages/CrashPlan/target/lib/
unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.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/1425276000420.*
mv /var/packages/CrashPlan/target/upgrade/1425276000420.whatevervalue/upgrade.sh /var/packages/CrashPlan/target/upgrade/1425276000420.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.2.0 GUID 559750658046558476