Yet another update from CrashPlan that might crash your CrashPlan package.
Today I received an email from CrashPlan saying that my server has been unable to reach any backup destinations for 3 days. After some investigation I noticed that my desktop client had been updated to 4.5.0 while the CrashPlan package in DSM had trouble updating and thus stopped.
Even though I’m quite happy with CrashPlan and patters is doing an amazing job on this package, I would love to see a official supported version from CrashPlan that doesn’t crash now and then (no pun intended). Luckily it’s rather easy to fix, so if you have this issue you may follow these steps.
A new version of the CrashPlan package has been released which should fix this issue automatically.
Manually upgrading to CrashPlan 4.5.0
Make sure that the CrashPlan package has been stopped in Package Center. If you click on “View log” you should see something similar to the log below. Make a note of the version number it failed to upgrade to. In this case 1435726800450.
I 12/10/15 08:05PM Installing upgrade - version 1435726800450 I 12/10/15 08:05PM Upgrade failed - version 1435726800450 I 12/10/15 08:15PM [server Backup] Starting backup to CrashPlan Central: 2 files (173.80MB) to back up I 12/10/15 08:16PM [server Backup] Completed backup to CrashPlan Central in < 1 minute: 2 files (173.80MB) backed up, 1.20MB encrypted and sent @ 173.5Kbps (Effective rate: 158Mbps) I 12/10/15 08:21PM Stopping CrashPlan I 12/10/15 08:22PM Synology repairing upgrade in I 12/13/15 09:57PM Synology repairing upgrade in
Use Putty or similar to SSH into your server and navigate to the CrashPlan upgrade directory:
List all files and folders in that directory by using ls -la.
CrashPlan creates a new directory for every time it tries (and fails) to upgrade. Delete all directories that match your upgrade id which in my case is 1435726800450. Simply delete all these folders by running the following command. Just be careful not to delete the .jar file.
rm -r ./1435726800450*/
Now it’s time for the actual upgrade. Run these two command that will extract the updated files from the .jar file to the appropriate locations. Remember to change the file name if needed:
unzip -o 1435726800450_270.jar "*.jar" -d /var/packages/CrashPlan/target/lib/
unzip -o 1435726800450_270.jar "lang/*" -d /var/packages/CrashPlan/target/
Now go back to “Package Center” in DSM and try to restart your CrashPlan package. If you have followed all steps the package should start again and sync your backup… until the next upgrade. 🙂