Fixing CrashPlan 4.2.0 on Synology after DSM 5.2 update

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

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:

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

Join the Conversation

158 Comments

  1. @Darrell: Although your thought delivers an easy way to backup stuff sitting on the Synology to the Crashplan cloud, this is by far the prefered way; it would mean your PC or laptop should be on all the time while making backups. The coolness of this solution is that Synology itself runs the client and all is automated from there…

  2. Your right Erik, but in my case I will let my PC stay on for the initial sync, then go from there. I tried to get it working, read everything I could, tried all different ports, settings, etc, but I could not get them to talk…

  3. How do you update the .ui_info on the DS412+ through putty? I have updated the server’s ip on all files but it does not change that I cannot update it on the server. It does not connect.
    Thanks in advance!

  4. I am sure this is a little over simplifying and may get someone in trouble eventually. use at your own risk. but

    as long as
    ls -l /var/packages/CrashPlanPRO/target/upgrade/*.jar
    only returns the current file, the next section should just work… at least it did for me

    export CPVersion=ls -g /var/packages/CrashPlanPRO/target/upgrade/*.jar | xargs -0 -n 1 basename | sed -e 's/\..*$//'
    unzip -o /var/packages/CrashPlanPRO/target/upgrade/$CPVersion.jar *.jar -d /var/packages/CrashPlanPRO/target/lib/
    unzip -o /var/packages/CrashPlanPRO/target/upgrade/$CPVersion.jar lang/* -d /var/packages/CrashPlanPRO/target/
    rm /var/packages/CrashPlanPRO/target/upgrade/$CPVersion.jar
    ls -d /var/packages/CrashPlanPRO/target/upgrade/$CPVersion.*/ | while read -r line; do mv ${line}upgrade.sh ${line}upgrade.sh.old ; done

Leave a comment

Your email address will not be published. Required fields are marked *