Fixing CrashPlan 4.2.0 on Synology after DSM 5.2 update – chris nelson dot ca
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. A godsend. I remembered this site from the last time this happened, looked up the older post, found that you had posted an update with today’s date and was like “Yes…that means I’ll be able to get CrashPlan working on my Synology again today!”

    Thanks so much!

  2. Thank-you!!! This worked for me.

  3. Works like a charm, thank you so much!!!

  4. Thank you for being smart.

  5. Working; thanks!

  6. Thanks! Will try in a couple of days, however it is my assupmtion that this didn’t happen due to the DSM upgrade. I did not upgrade yet and still I have the error of the Crashplan upgrade that failed.

  7. THANX!!
    My CrashPlan does work again… ;-)

  8. Worked like a charm!

  9. Thanks Chris, much appreciated! This worked for me on my DS412+.

  10. Replace CrashPlan with CrashPlanPRO in each command to fix CrashPlanPro version

  11. Don’t forget to add PRO to all of the (commands) paths if you are using the Professional version. ex. unzip -o /var/packages/CrashPlanPRO/target/upgrade/1425276000420.jar *.jar -d /var/packages/CrashPlanPRO/target/lib/ . It didn’t dawn on me why these statements weren’t working until after I navigated the file structure in SSH. Thanks for posting these commands, they worked like a charm.

  12. Thanks so much! Worked like a charm and files are backing up again =)

  13. I’m getting a permission denied message when I try that. I’m ssh as admin. Any idea why?
    Thanks in advance.

  14. Thank you so much, this worked perfectly! Thank you thank you thank you!!

  15. Never mind. Worked perfectly as root instead of admin.
    Thank you.

  16. If you see permission denied you need to make sure you are connecting via SSH as “root” and not “admin”. You use the admin’s password for the root account.

  17. Thanks a lot, got Crashplan working again after following your steps on my DS411+II.

  18. Thank you so much, great work!

  19. worked like a charm, thanks!

  20. OK…I have no idea what all these instructions did, but after figuring out how to use SSH (by finding “Putty” for Win7) and then copying / pasting the command lines, we’re back in business. It really is a miracle…so MANY THANKS to Chris and other Very Smart People who make advanced technology possible for the rest of us mortals.

  21. Sweet! Thanks!

  22. Thank you!

  23. For others who follow, execute the commands from /var/packages/Crashplan. Although absolute paths are specified, I got a “caution” message with first command when I executed outside Crashplan directory. Thank you Chris for your efforts in testing and posting

  24. Thank you again!

  25. Solution in case you have the following error when running:
    unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar *.jar -d /var/packages/CrashPlan/target/lib/

    Error:
    caution: filename not matched: 1425276000420.jar

    Just do the following instead of the above command (same outcome):
    unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar bcprov-jdk15on.jar -d /var/packages/CrashPlan/target/lib/
    unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar c42_protolib.jar -d /var/packages/CrashPlan/target/lib/
    unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar com.backup42.desktop.jar -d /var/packages/CrashPlan/target/lib/

    Now it is working well for me as well :). Thx a lot for writing this up!

  26. Thank you so much for taking the time to post this information, it’s very much appreciated!

  27. Thankyou kindly! Worked a charm, and I appreciate your help very much!

  28. Thanks – also worked for me on upgrade to DSM 5.2 CrashPlan 4.2.0

  29. Thank you so much for posting. Worked perfectly and now Crashplan is running again.

  30. You sir are a legend. My Thanks.

  31. Chris, thank you so much for posting this fix!

  32. Thank you!

  33. Awesome, thank you for sharing!

  34. Awesome! Worked for me too. Many thanks Chris – you’re a lifesaver!

  35. Thanks – Worked perfectly on my DS413

  36. You saved me LOTS of time and frustration! Thanks for sharing!

  37. I had the same issue that Patrick Boos mentioned. I’ll put the full instructions here in case anyone else needs them:

    unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar bcprov-jdk15on.jar -d /var/packages/CrashPlan/target/lib/
    unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar c42_protolib.jar -d /var/packages/CrashPlan/target/lib/
    unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar com.backup42.desktop.jar -d /var/packages/CrashPlan/target/lib/
    unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar lang/* -d /var/packages/CrashPlan/target/

    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

    I ALSO had an issue with getting the headless client to connect. I’ll share in the hope of helping others avoid wasting their time. I realized (when I was posting to ask about it here actually) that when my windows notepad showed one line for the ui.properties file:
    “#Fri Dec 09 09:50:22 CST 2005serviceHost=192.168.1.110servicePort=4243#pollerPeriod=1000…”
    It should translate to individual settings on separate lines:
    “#Fri Dec 09 09:50:22 CST 2005
    serviceHost=192.168.1.110
    servicePort=4243
    #pollerPeriod=1000…”

    but when i posted in this reply box serviceHost and servicePort were on the same line:
    “serviceHost=192.168.1.110servicePort=4243” which won’t work.

    The sad thing is I know about this issue with notepad and haven’t had an issue with it so didn’t think about it. lesson learned

  38. CP is happy again. Thanks!

  39. Hi everybody!

    I had the same issue so thanx heaven, aehem, thanx Chris for this article – it saved my butt! It was a second before starting all over with my Syno (10TB!).

    My question: is there a way to prevent the CP headless client from automatically updating?

    I froze even the Syno DSM Version cuz my 2415+ is doing everything I want from it – and it is doing everything fine! ;-) so it would be great if I could also prevent CP from updating (and crashing afterwords).

    Any advice?

    All the best,
    Jens.

  40. Thanks man! Saved me lots of time

  41. Thank you for this post! Worked perfect.

  42. Thank you for making this available!

 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)