Jan 102015

If you recently upgraded to DSM 5.2 and had CrashPlan break, this is likely due to the CrashPlan 4.2.0 update. Please see http://chrisnelson.ca/2015/05/12/fixing-crashplan-4-2-0-on-synology-after-dsm-5-2-update/

NOTE: This manual fix should no longer be needed after the 0029 update from Patters:

0029 Updated to CrashPlan version 3.7.0, improved detection of temp folder (prevent use of /var/@tmp), added support for Annapurna Alpine AL514 CPU (armhf) in DS2015xs, added support for Marvell Armada 375 CPU (armhf) in DS215j, abandoned practical efforts to try to support Code42’s upgrade scripts, abandoned inotify support (realtime backup) on PowerPC after many failed attempts with self-built and pre-built jtux and jna libraries, back-merged older libffi support for old PowerPC binaries after it was removed in 0028 re-write

Archive content:
CrashPlan recently pushed an update (3.7.0) to all clients 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.6.4, GUID 574956158631543214
Upgrades available at central.crashplan.com:443
Downloading a new version of CrashPlan.
Download of upgrade complete – version 1388728800370.
Installing upgrade – version 1388728800370
Upgrade installed – version 1388728800370
CrashPlan stopped, version 3.6.4, GUID 574956158631543214

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/1388728800370.

After some investigation by Stig, Casper, and Harv on the comments for the package a working solution was found to manually install the update files and disable the failing upgrade.sh file. 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 3.7.0 update.

1. First, connect to Synology using SSH and the root account (uses admin password).  Connecting as the admin account will not give you enough permissions.
2. Run the following commands:

3. 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:

4. After the above completes, you should be able to start the CrashPlan package again in Synology and get it running once more.

  191 Responses to “Fixing CrashPlan on Synology after the 3.7.0 update (Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1388728800370. )”

  1. Worked perfectly, thanks for the info!

  2. Thanks, this made it work again…

  3. Worked like a charm. Thanks for the easy instructions!

  4. Cool exactly what I needed – worked perfectly on Xpenology DSM5.0 – 4528 Update 2

  5. Although crashplan on the Synology is up and running now, I am no longer able to access it from a crashplan client on my Mac.
    Although I also updated the client and directed its ui.properties to the Synology, the crashplan client still shows the status of my Mac’s backup.
    I was wondering if anyone has experienced similar issues. If so, I’m curious if and how you were able to solve them. Or maybe I’m missing something simple? Thanks in advance for sharing!

  6. Brilliant, thanks a lot! Worked like a charm on my DS214Play. For SSH commands, I’m using WinSCP for user friendly client on Windows.

  7. Thanks for putting this info out there. Just got bit myself and was thinking I did something silly.

  8. Thanks Brother. That got my CrashPlan service up and running again on my 1513+.

  9. Thank you for posting this guide. It worked perfectly.

    Crashplan should really just get in the game and create their own installer for synology, but I tip my hat to everyone who has made it as painless as it currently is.

  10. Perfect, thanks so much.

  11. My CrashPlan (DS415+, DSM 5.1-5021) stopped working coincident with the 3.7.0 update. I do not have the same error messages, rather the following in /var/packages/CrashPlan/target/log/engine_output.log:

    [01.11.15 17:21:50.107 INFO main root ] JVM temp directory /tmp/@tmp does not exist!

    The upgrade/*.jar files do not exist either…



  12. I upgraded to DSM 5.1-5021 Update 2 and restarted CrashPlan. No luck.

    I found that /tmp/@tmp did not exist, but /volume1/@tmp did, so I:

    ln -s /volume1/@tmp/ /tmp/@tmp

    and restarted the CrashPlan package. It appears to be working fine now. The CrashPlan service on the Synology appears to still be running 3.6.4, though:


    3.6.4 – 1388642400364 (2014-01-02T06:00:00:364+0000)

    so I may still face the issue you documented.

  13. Excellent. Thanks so much for this. Worked for me – it had been bugging me for ages.

  14. Brilliant work! Thanks for taking the time to post this… I’ve been pouring over the web trying to figure out this issue and here it’s laid out in 4 easy to follow steps. A HUGE thank you!

  15. Much appreciated!!!

  16. Thanks a million. This worked perfectly! Just got done restoring 5.5TB via Crashplan after a multi-disk failure and can’t imagine life without Crashplan at this point.

  17. Good stuff – nice work! Thank you for posting this!

  18. Hmmmm.. After installing crashplan, my Synology (DS213, crashplan versoin 3.6.4-0028) I never get the “”Download of upgrade complete” after “Downloading o new version of CrashPlan”

    instead it stops it, and says it is unable to apply upgrade (duh) and will retry in an hour.

    Bummer. I wonder why it can’t get it online. Hopefully it is a temporary issue.

  19. Thank you for sharing this! Made my day a lot better :)

  20. Thanks so much for posting this information. I was tearing my hair out last night. Will have a look at this later when I get home!

  21. The only thing I did slightly differently was to cd directly into the directory 1388728800370.whatevervalue and then use the following cp commands to copy the files:

    cp -p *.jar ../../lib/
    cp -p run.conf ../../bin
    cp -p lang/* ../..


    mv upgrade.sh upgrade.sh.old

    The net result was the same. I have version 3.70 running perfectly on my DSM 5.1.5022 release on DS412+. Thank you SO much for the concise posting!

  22. This is still a mess.
    – as soon as i start Crashplan, the log file says ‘unable to apply updates, Trying again in one hour’
    – the remote client states ‘Crashplan Upgrade Faild. Crashplan failed to apply an upgrade and will try again automatically in one hour’. I can delete that notification easily though.
    – i have to issue the command ‘rz’ via the client to connect to my crashplan central account (double click the crashplan logo in the upper right corner and issue ‘rz’).

    Im afraid what will happen in 1 hour….

  23. Amazing, thank you so much!

  24. Sure thing, Crashplan stopped after an hour because it has performed the update again. Is there any way to stop the automatic update proces alltogether?

  25. Awesome! – Good work, fellas

  26. Thanks for commands. The engine started but I can not connect from GUI.

  27. Ah, so I’m not the only one that has that problem ;)

  28. hey! Craig Rice’s observation was right on with my issue. I was able to get the package working after that.. thanks!

  29. It worked perfectly. Thanks

  30. I had the issue with GUI as well. I noticed that the GUI was still 3.6.4.

    I downloaded and installed the 3.7 software on my client system, disabled the Crashplan service and updated the ui.properties file in the C:\program files\Crashplan\conf directory. I uncommented the ServiceHost line and replaced with the IP address of my Synology server.

    After that I opened the desktop GUI and voila I could see my Crashplan service on the DSM system again.

  31. Oops…posted the response above regarding the installation of 3.7 desktop to fix the GUI issue using my wife’s account. Should be this one.

  32. Left a reply earlier but it seems to have gone. Anyways let me say thanks for sorting this out – worked for me too! Now just have to sort out the remote client!

  33. Great information – worked perfectly, thanks very much!

  34. Nice Job

  35. Thanks for posting that. Seems to have worked for me too – at least for now!

  36. Brilliant. Thank you for the very clear explanation!

  37. Thanks for the article, was a great help to solving my issue also.

  38. Well I’ll be damned… This actually worked! Thanks for your help!!!

  39. I had the same issue as Crahg Rice. His fix helped me…..BUT after a reboot the situation is the same. CP headless client just starts and stops immediately :o(

    BR Jeppe

  40. Worked great, thank you for sharing!

  41. Worked like a charm! thanks a lot.
    You rock!

  42. Brilliant. Thank you for the very clear explanation! YOU ARE MY GANDALF!!!!!! :-)

 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="">