Fixing CrashPlan 4.2.0 on Synology after DSM 5.2 update – chris nelson dot ca

Fixing CrashPlan 4.2.0 on Synology after DSM 5.2 update

 How To  Add comments
May 122015
 

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

  158 Responses to “Fixing CrashPlan 4.2.0 on Synology after DSM 5.2 update”

  1. Brynjar says:
    May 16, 2015 at 11:34 am

    THANKS! Works well. What should I do when Patters updates the package? Should I uninstall and install?

  2. george says:
    May 16, 2015 at 12:59 pm

    Total beginner here, I am attempting the instructions and keep getting “cannot find or open /var/packages/….” I am logged in as root with my password. The numbers match up, and I am editing the lines as CrashPlanPro, because I am using the pro version obviously. Any help would be appreciated

  3. george says:
    May 16, 2015 at 1:45 pm

    Total beginner here. I am trying this fix. I am logged in as root. When I copy and paste the commands i get a message “cannot find or open /var/packages…” All of the numbers match up, and I edited the line to read CrahPlanPro to reflect the product that I am using. Any help would be appreciated

  4. tnaseem says:
    May 16, 2015 at 4:37 pm

    Nice work and any thanks! Worked like a charm. :)

  5. Chris Olson says:
    May 16, 2015 at 7:15 pm

    Nice work! You saved me some time.

  6. Paul says:
    May 17, 2015 at 1:47 am

    Great!!! Thanks a lot

  7. Oscar says:
    May 17, 2015 at 1:58 am

    Hi,

    I have simular problem as george.When I run the command I get: caution: filename not matched: 1425276000420.jar. Any ideas?

  8. Jens says:
    May 17, 2015 at 3:06 am

    @george: really standing as root on the root of the filesystem?

  9. Raoul says:
    May 17, 2015 at 5:02 am

    Thanks a lot, worked perfectly for me!

  10. Torvi says:
    May 17, 2015 at 6:12 am

    Thank you very much, once again it works :)

  11. cereyanli says:
    May 17, 2015 at 6:45 am

    You are a saver. Your fix worked on my 215j now CrashPlan package works again:

    Thanks

  12. Matthew says:
    May 17, 2015 at 7:15 am

    Worked perfectly, thanks!

  13. Koesie says:
    May 17, 2015 at 8:08 am

    Thank you my backup is running again

  14. MFBrin says:
    May 17, 2015 at 9:52 am

    Terrific!! Readers should note that “whatevervalue” is in 2 places in the string.

  15. Rich says:
    May 17, 2015 at 10:10 am

    I see that people were having some trouble because of the global matching, the easy thing to do is to put quotes around the wildcards, so the one liners are:

    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/

  16. Mark says:
    May 17, 2015 at 12:40 pm

    Worked for me… thanks!

  17. g8r87trp92 says:
    May 17, 2015 at 4:35 pm

    You ‘da man!! Thanks a ton for posting this!

  18. zimbaa says:
    May 17, 2015 at 8:47 pm

    Worked for me using version 3.7.0

    Thanks

  19. Robbert Marrink says:
    May 17, 2015 at 9:11 pm

    Thank you very very much!

  20. Rick K. says:
    May 17, 2015 at 9:54 pm

    You’re the best!

  21. D says:
    May 17, 2015 at 10:16 pm

    perfect thank you!

  22. OMEGA says:
    May 17, 2015 at 11:27 pm

    Thanks for posting this and thank you even more for assembling this guide. Worked like a charm and was so easy to follow your instructions. Your help is highly appreciated.

  23. Tadeusz says:
    May 18, 2015 at 2:16 am

    Thank you so much!

  24. MattR says:
    May 18, 2015 at 2:53 am

    Working. Awesome. Thanks!

  25. Audran Stéphane says:
    May 18, 2015 at 4:49 am

    Hi, I have an issue, after entering the lines:
    mv /var/packages/CrashPlan/target/upgrade/1425276000420.1431945211031/upgrade.sh /var/packages/CrashPlan/target/upgrade/1425276000420.1431945211031/upgrade.sh.old

    It says ” mv: can’t rename ‘/var/packages/CrashPlan/target/upgrade/1425276000420.1431945211031/upgrade.sh’: No such file or directory”

    What’s wrong ?

    Thanks !

  26. Mooo says:
    May 18, 2015 at 5:19 am

    Oscar: Just perform the steps and disregard the error “filename not matched” (continue with the other steps). It should work. Did so for me.

  27. Audran Stéphane says:
    May 18, 2015 at 5:27 am

    Yes you’re all right, I could run Crashplan anyway. I just wonder now how I could speed it up because now I just can upload to 100kbps instead of 1-2 Mbps before !

  28. acgarland says:
    May 18, 2015 at 7:34 am

    Like many others, I’ve benefited from your help on this same problem on several updates now. You have saved me a lot of time for which I’ve very appreciative!

  29. AJ Willmer says:
    May 18, 2015 at 8:33 am

    Thank you Chris, worked for me

  30. Mike Nielsen says:
    May 18, 2015 at 8:36 am

    Excellent information!

  31. Kris says:
    May 18, 2015 at 10:43 am

    Thanks a mill. from Denmark

  32. theman says:
    May 18, 2015 at 10:50 am

    many thx

  33. Joe Wirtley says:
    May 18, 2015 at 10:59 am

    Thank you so much for the instructions. It worked great! And it’s the second time I’ve come to your site to fix something like this.

  34. stujordan says:
    May 18, 2015 at 11:01 am

    Thanks.

  35. David G says:
    May 18, 2015 at 11:02 am

    CrashPlanPRO is case sensitive. Replace CrashPlan with CrashPlanPRO and it works! Thanks, Chris

  36. David says:
    May 18, 2015 at 11:32 am

    This guide worked perfectly, I appreciate the help!

  37. Dale says:
    May 18, 2015 at 11:43 am

    Thanks this did the trick once I substituted “CrashPlanPRO” for each “CrashPlan” in each command.

  38. Dale says:
    May 18, 2015 at 12:09 pm

    Does anyone else notice that the time within the Crashplan logs has set itself to GMT after the latest update?

  39. george says:
    May 18, 2015 at 1:00 pm

    OK, cd/’ed into the directory, and everything is working now. Thanks to all for your help!!

  40. matshofstra says:
    May 18, 2015 at 1:27 pm

    Chris, you rock! Thanks again!! Crashplan running smooth as silk again.

  41. Brian says:
    May 18, 2015 at 3:48 pm

    You are a gentleman and a scholar. The instructions worked great, thanks!!

  42. Pete Ten says:
    May 18, 2015 at 6:01 pm

    First thanks for all work on setting up the crashplan backup service and sharing this with everyone. I new to this and don’t understand it all but with your help had my synology backing up to crashplan for a couple years. I had the backup service working with your commands after the 3.7 update…until now

    when I run the first unzip command I get the following:

    DiskStation> unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar
    *.jar -d /var/packages/CrashPlan/target/lib/
    Archive: /var/packages/CrashPlan/target/upgrade/1425276000420.jar
    error: cannot delete old /var/packages/CrashPlan/target/lib/bcprov-jdk15on.jar
    Permission denied
    error: cannot delete old /var/packages/CrashPlan/target/lib/c42_protolib.jar
    Permission denied
    error: cannot delete old /var/packages/CrashPlan/target/lib/com.backup42.desktop.jar
    Permission denied

    when I run the first unzip command with quotes I get the following:

    DiskStation> unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar ?
    ??*.jar” -d /var/packages/CrashPlan/target/lib/
    Archive: /var/packages/CrashPlan/target/upgrade/1425276000420.jar
    caution: filename not matched: “*.jar”

    Am I not running the commands from the right place or should I have done something prior to running the commands. When I use the package center to install the crashplan package it installs and starts running. Then stops. If I try to restart it will ‘think’ for several minutes before defaulting back to stopped.

    I have a DS1512+ running DSM 5.2-5565 with INTEL Atom D2700 processors.

  43. Cian Whalley says:
    May 18, 2015 at 6:15 pm

    Brilliant!

  44. TD says:
    May 18, 2015 at 6:34 pm

    Thank you, worked perfectly for me!

« Older Comments
Newer Comments »

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">

(required)

(required)