Advertisement
CrashPlan Community Forum – Support & Assistance

CrashPlan for Small Business 6.7.0 Installation Fix for Synology (1512021600670_4503 February 2018)

Affiliate Links

The latest auto-upgrade from the CrashPlanPRO client for Synology is now pushing for installation of a newly branded engine: CrashPlan for Small Business (CrashPlanSMB), version 6.7.0. Here’s  the log for this:

02/03/18 05:02PM Synology extracting upgrade from /var/packages/CrashPlanPRO/target/upgrade/1512021600670_4503.jar

02/03/18 05:09PM CrashPlan for Small Business started, version 6.7.0, GUID 544550513805885703


You should block the auto-upgrade procedure and stick to CrashPlan PRO 4.9.0 until there is an updated package for the new CrashPlanSMB structure. When that’s available I’ll update this page.

If you did get your installation stuck, just grab the previous linux package for CrashPlan PRO 4.9.0  from crashplanpro.com > App Downloads, and use the previous guides to get it up and running, and then block the auto-upgrade procedure in the CrashPlanPRO folder.


Here’s a quick guide to rollback to 4.9.0 :

  1. Take note of your Java heap size to punch it again later on
  2. Get the 4.9.0 Linux package from crashplanpro.com > App Downloads and place it in your Synology’s public folder. I’ll be doing a dedicated Java setup, so do get jre-8u151-linux-x64.tar.gz from Oracle’s site and place it next to the CrashPlan PRO package.
  3. Uninstall your CrashPlan PRO (CPP) package using Synology’s Package Manager (SPM).
  4. Install it again, uncheck “Run after install”.
  5. Use ssh to disable the auto-upgrade process at this stage. You can also change the Java heap as well.
  6. Run the package,  and tail the log on a second ssh session:
    tail -f /var/packages/CrashPlanPRO/target/log/service.log.0
  7. Wait until you get something similar to:
    ****************************************************************
    READY! Unauthorized Listening ports are PEER=4242/4247, CPD=4243, HTTP=4244
    ****************************************************************
  8. Using SPM stop CPP‘s package. Wait for a “Service stopped normally” log entry. Start the package again and you should be seeing log entries such as “HISTORY:: Unable to apply upgrade(s), retrying in one hour”
  9. We should now be good to go. Let’s get .ui_info onto our client, login, and check if everything is looking good. Note that the client app is probably going to try and upgrade (mine wasn’t successful on macOS) and you may need to close it and login in once again. After login the client should report “CrashPlan PRO Upgrade Failed”.
  10. If you’re getting “Waiting for connection“, wait for a moment or double click the app’s icon and  issue reconnect.

 

Advertisement

8 comments for “CrashPlan for Small Business 6.7.0 Installation Fix for Synology (1512021600670_4503 February 2018)

  1. Alessandro Caredda
    February 4, 2018 at 09:57

    I followed the procedure, but at 9. my 6.7.0. PC client can’t connect to my Synology 4.9.0 server. Any hint?

    • an
      February 4, 2018 at 10:03

      Hmm – I wrote that it did upgrade, but I should have written “try to upgrade”, as in essence the client I’m using is actually still 4.9.0 (on macOS). You might want to try downloading the 4.9.0 client from crashplanpro.com and then block/remove permissions the the upgrade folder to all users (including SYSTEM, I think that did it in the past but I can’t say for sure).

      • Alessandro Caredda
        February 4, 2018 at 10:25

        Thank you for the quick answer. I tried to re-install the 4.9.0. client on my PC (Windows 10), but when I launch it, it suddenly upgrades to 6.7.0. I haven’t any idea on how to prevent upgrading on Windows.

        • an
          February 4, 2018 at 10:34

          I think you can by changing permissions to the upgrade folder (https://crashplanbackup.com/folder-locations-for-crashplan-common-system-files/). You need to try this by going to the folder’s Properties, and then Advanced Permissions, and denying permissions to all entries, Including the SYSTEM user. This would render the file inaccessible even for windows, and when you do want to upgrade later on you need use the same properties to take ownership of the file and reset the permissions in the process. Marking the folder as read-only is probably not enough.

          • Alessandro Caredda
            February 4, 2018 at 14:32

            I tried your solution and it works, thank you! The difficult is that the upgrade process seems to start during the installation. I succedeed deleting the “upgrade” folder inside C:Program FilesCrashplan and denying the permissions ASAP, deleting again the “upgrade” folder if it appears again.

          • an
            February 4, 2018 at 17:50

            Great, glad you got it working!

  2. Shane Jensen
    February 4, 2018 at 15:56

    After following the instructions above, the CPC was stating that an upgrade was in progress and would not move pass the login dialog. Exiting the CPC and and starting it again allowed the CPC to connect properly.

    • an
      February 4, 2018 at 17:49

      Yeah, that’s what happened to me as well, as mentioned in the last step. Thanks for sharing!

Leave a Reply

Here's what other Users are reading:

Affiliate Links
Advertisement