CrashPlan Community Forum – Support & Assistance

CrashPlan 4.8.0 Installation Fix for Synology (1435813200480_331 November 2016)

Affiliate Links

Here we go again! Sorry about taking this long posting about this one in particular, I had to focus on other stuff. The worst part of the current way of fixing this is that it always ends up “synchronizing file information” again, which is painstakingly slow.

One quick reminder – you can “Submit Your Own Post” whenever you find a solution using the link on the top of the page and this way help other CrashPlan users!

So getting back to November’s update; one issue is apparently getting to connect to the client, for which you have to edit my.service.xml in order to make it work:

  • File: 
  • File Location:
  • Procedure:
    • Find: 
    • Replace with: 
    • Restart CrashPlan after the change.

If you’re struggling with the upgrade itself, report back to this method:

  1. Check if typing in cpio in Terminal doesn’t return this command’s instructions, copy cpio to /bin (this is probably necessary after DSM’s firmware is upgraded):
    • sudo cp /var/packages/CrashPlan/target/bin/cpio /bin/cpio
    • Or just symlink it instead of copying:  
      ln -s /var/packages/CrashPlan/target/bin/cpio /usr/local/bin/cpio
  2. Uninstall CrashPlan using DSM Package Manager
  3. Make sure you have Java8 from Synology installed. If not, install it.
  4. Reinstall CrashPlan and select “Default system Java Version” in the installer options. It may give out an error at the end of the install, but in the window behind you should see it running. Just close the error dialog box in front.
  5. Let it run for a while, until it stops (may be necessary to repeat start/stop). If you check the logs via Package Manager it will have tried to upgrade.
  6. Now SSH the NAS and edit the file /var/packages/CrashPlan/target/install.vars, redirecting to a correct Java Package:
    • Synology official Java 8 Package:
  7.  Start the package and wait. You should now see it running 4.8.0, via logs.
  8. After fixing .ui_token you’ll have to login on your client app.
  9. If you were using a custom Java heap size, don’t forget to change it again.
  10. You can also check the current version of your CrashPlan installation (double click top right CrashPlan icon > “version”). In this case I’m seeing:
4.8.0 - 1435813200480 (2015-07-02T05:00:00:480+0000) - Build: 331

As other community members have suggested, a way of checking if CrashPlan is actively listening is by using this command:

# netstat -na | grep LISTEN | grep 42

You should see something like this:

tcp 0 0* LISTEN
tcp 0 0* LISTEN

Lastly, a quick reminder: you can block the auto-upgrade process, I’ve been successful with this method on a Synology box that can’t have these hiccups at any moment:




Leave a Reply

Here's what other Users are reading:

Affiliate Links