CrashPlan Community Forum – Support & Assistance

CrashPlan 4.8.2 Installation Fix for Synology (1436674800482_4 April 2017)

Affiliate Links

NEW for CrashPlan for Small Business users: note that the correct package paths will now begin with ´/var/packages/CrashPlanPRO/…´.


Following up the discussion on this thread from our forums, here’s what I’ve gathered about this new version upgrade. FYI the auto-upgrade block procedure continues to work just fine, preventing CrashPlan from breaking inadvertedly.

Edit: use this to whenever possible to follow the log tail in realtime:

tail -f /var/packages/CrashPlan/target/log/service.log.0

Solution 1 (Dedicated Java install):

Considering I’ve been experiencing some server timeouts while CrashPlan is running, when accessing my DS412+, I chose to use the dedicated install instead, to see if that makes a difference. It worked and upgraded fairly easily to 4.8.2 and it is now synchronising (without any adoption). Here goes:

  1. Take note of your current Java Heap size (issue java mx on your client’s CLI)
  2. Using terminal, copy cpio:
    sudo cp /volume1/@appstore/CrashPlan/bin/cpio /bin/cpio
  3. Place the Java SE Runtime file in your public share (you need a Oracle login to get it from here, the latest version of patters’ package requires not the latest Java package, but version 8u121: jre-8u121-linux-x64.tar.gz)
  4. Uninstall CrashPlan using DSM Package Manager
  5. Install CrashPlan using DSM Package Manager and disable the “Run after installation” checkbox.
  6. Wait a moment and try to run it (in my case it wouldn’t run so I uninstalled/reinstalled one more time). A good option is to check the tail log, as suggested at the beginning of this post, for “Upgrade complete” and related messages.
  7. You can read the real time log with terminal open:
    tail -f /var/packages/CrashPlan/target/log/service.log.0
  8. You should see the install script starting the upgrade and finishing with “Service stopped normally”.
  9. Wait a moment and try to run the package again; if it fails, wait some more time and run again. The tail log should now show lots of output, which means it’s running.
  10. After this, don’t forget:
    1. Change the .ui_info file contents, using this guide. Note that this first time the headless .ui_info may be ending in – this means that the next time you restart CrashPlan it will change, and then showing the correct headless server IP.
    2. Check if the GUI is properly connecting and login
    3. Change your Java Max Heap size if necessary, using this guide (Solution 2 for persistence) and restart
    4. Verify your .ui_info connection info again – it may have been broken after the restart
  11. You may now block the auto-upgrade process, using this guide
  12. Check if the GUI is properly connecting.


Solution 2 (built-in Java install), quote from user @krachvik ‘s experience:

  1. Uninstalled Crashplan
  2. Confirmed Built-In Synology Java8 is installed
  3. Reinstalled Crashplan
    1. chose Built-in Java (NOT dedicated)
    2. unchecked the option to start service upon completion)
  4. Disabled Auto-update process
  5. Connected to the Crashplan server from client and logged on using my credentials at which point it said “Updating client” but nothing happened because it couldn’t update (auto-update is disabled)
    1. did not close the client window (reused at step 8)
  6. Re-enabled Auto-update process
  7. Plugged in my credentials again at the client windows I already had opened
  8. Crashplan window came up
    2. while the client window was still up, double clicked the Crashplan logo and typed in “java mx 1536, restart” as per An’s suggestion
  9. Crashplan service stopped
  10. Started Crashplan service
    1. was informed it failed
  11. Started Crashplan again and this time it stayed running

Thanks for all the feedback and help. I suppose I’ll be back when it fails again.



Here's what other Users are reading:

Affiliate Links