CrashPlan packages for Synology NAS

UPDATE – CrashPlan For Home (green branding) was retired by Code 42 Software on 22/08/2017. See migration notes below to find out how to transfer to CrashPlan for Small Business on Synology at the special discounted rate.

CrashPlan is a popular online backup solution which supports continuous syncing. With this your NAS can become even more resilient, particularly against the threat of ransomware.

There are now only two product versions:

  • Small Business: CrashPlan PRO (blue branding). Unlimited cloud backup subscription, $10 per device per month. Reporting via Admin Console. No peer-to-peer backups
  • Enterprise: CrashPlan PROe (black branding). Cloud backup subscription typically billed by storage usage, also available from third parties.

The instructions and notes on this page apply to both versions of the Synology package.

CrashPlanPRO-Windows

CrashPlan is a Java application which can be difficult to install on a NAS. Way back in January 2012 I decided to simplify it into a Synology package, since I had already created several others. It has been through many versions since that time, as the changelog below shows. Although it used to work on Synology products with ARM and PowerPC CPUs, it unfortunately became Intel-only in October 2016 due to Code 42 Software adding a reliance on some proprietary libraries.

Licence compliance is another challenge – Code 42’s EULA prohibits redistribution. I had to make the Synology package use the regular CrashPlan for Linux download (after the end user agrees to the Code 42 EULA). I then had to write my own script to extract this archive and mimic the Code 42 installer behaviour, but without the interactive prompts of the original.

 

Synology Package Installation

  • In Synology DSM’s Package Center, click Settings and add my package repository:
    Add Package Repository
  • The repository will push its certificate automatically to the NAS, which is used to validate package integrity. Set the Trust Level to Synology Inc. and trusted publishers:
    Trust Level
  • Now browse the Community section in Package Center to install CrashPlan:
    Community-packages
    The repository only displays packages which are compatible with your specific model of NAS. If you don’t see CrashPlan in the list, then either your NAS model or your DSM version are not supported at this time. DSM 5.0 is the minimum supported version for this package, and an Intel CPU is required.
  • Since CrashPlan is a Java application, it needs a Java Runtime Environment (JRE) to function. It is recommended that you select to have the package install a dedicated Java 8 runtime. For licensing reasons I cannot include Java with this package, so you will need to agree to the licence terms and download it yourself from Oracle’s website. The package expects to find this .tar.gz file in a shared folder called ‘public’. If you go ahead and try to install the package without it, the error message will indicate precisely which Java file you need for your system type, and it will provide a TinyURL link to the appropriate Oracle download page.
  • To install CrashPlan PRO you will first need to log into the Admin Console and download the Linux App from the App Download section and also place this in the ‘public’ shared folder on your NAS.
  • If you have a multi-bay NAS, use the Shared Folder control panel to create the shared folder called public (it must be all lower case). On single bay models this is created by default. Assign it with Read/Write privileges for everyone.
  • If you have trouble getting the Java or CrashPlan PRO app files recognised by this package, try downloading them with Firefox. It seems to be the only web browser that doesn’t try to uncompress the files, or rename them without warning. I also suggest that you leave the Java file and the public folder present once you have installed the package, so that you won’t need to fetch this again to install future updates to the CrashPlan package.
  • CrashPlan is installed in headless mode – backup engine only. This will configured by a desktop client, but operates independently of it.
  • The first time you start the CrashPlan package you will need to stop it and restart it before you can connect the client. This is because a config file that is only created on first run needs to be edited by one of my scripts. The engine is then configured to listen on all interfaces on the default port 4243.
 

CrashPlan Client Installation

  • Once the CrashPlan engine is running on the NAS, you can manage it by installing CrashPlan on another computer, and by configuring it to connect to the NAS instance of the CrashPlan Engine.
  • Make sure that you install the version of the CrashPlan client that matches the version running on the NAS. If the NAS version gets upgraded later, you will need to update your client computer too.
  • The Linux CrashPlan PRO client must be downloaded from the Admin Console and placed in the ‘public’ folder on your NAS in order to successfully install the Synology package.
  • By default the client is configured to connect to the CrashPlan engine running on the local computer. Run this command on your NAS from an SSH session:
    echo `cat /var/lib/crashplan/.ui_info`
    Note those are backticks not quotes. This will give you a port number (4243), followed by an authentication token, followed by the IP binding (0.0.0.0 means the server is listening for connections on all interfaces) e.g.:
    4243,9ac9b642-ba26-4578-b705-124c6efc920b,0.0.0.0
    port,--------------token-----------------,binding

    Copy this token value and use this value to replace the token in the equivalent config file on the computer that you would like to run the CrashPlan client on – located here:
    C:\ProgramData\CrashPlan\.ui_info (Windows)
    “/Library/Application Support/CrashPlan/.ui_info” (Mac OS X installed for all users)
    “~/Library/Application Support/CrashPlan/.ui_info” (Mac OS X installed for single user)
    /var/lib/crashplan/.ui_info (Linux)
    You will not be able to connect the client unless the client token matches on the NAS token. On the client you also need to amend the IP address value after the token to match the Synology NAS IP address.
    so using the example above, your computer’s CrashPlan client config file would be edited to:
    4243,9ac9b642-ba26-4578-b705-124c6efc920b,192.168.1.100
    assuming that the Synology NAS has the IP 192.168.1.100
    If it still won’t connect, check that the ServicePort value is set to 4243 in the following files:
    C:\ProgramData\CrashPlan\conf\ui_(username).properties (Windows)
    “/Library/Application Support/CrashPlan/ui.properties” (Mac OS X installed for all users)
    “~/Library/Application Support/CrashPlan/ui.properties” (Mac OS X installed for single user)
    /usr/local/crashplan/conf (Linux)
    /var/lib/crashplan/.ui_info (Synology) – this value does change spontaneously if there’s a port conflict e.g. you started two versions of the package concurrently (CrashPlan and CrashPlan PRO)
  • As a result of the nightmarish complexity of recent product changes Code42 has now published a support article with more detail on running headless systems including config file locations on all supported operating systems, and for ‘all users’ versus single user installs etc.
  • You should disable the CrashPlan service on your computer if you intend only to use the client. In Windows, open the Services section in Computer Management and stop the CrashPlan Backup Service. In the service Properties set the Startup Type to Manual. You can also disable the CrashPlan System Tray notification application by removing it from Task Manager > More Details > Start-up Tab (Windows 8/Windows 10) or the All Users Startup Start Menu folder (Windows 7).
    To accomplish the same on Mac OS X, run the following commands one by one:

    sudo launchctl unload /Library/LaunchDaemons/com.crashplan.engine.plist
    sudo mv /Library/LaunchDaemons/com.crashplan.engine.plist /Library/LaunchDaemons/com.crashplan.engine.plist.bak

    The CrashPlan menu bar application can be disabled in System Preferences > Users & Groups > Current User > Login Items

 

Migration from CrashPlan For Home to CrashPlan For Small Business (CrashPlan PRO)

  • Leave the regular green branded CrashPlan 4.8.3 Synology package installed.
  • Go through the online migration using the link in the email notification you received from Code 42 on 22/08/2017. This seems to trigger the CrashPlan client to begin an update to 4.9 which will fail. It will also migrate your account onto a CrashPlan PRO server. The web page is likely to stall on the Migrating step, but no matter. The process is meant to take you to the store but it seems to be quite flakey. If you see the store page with a $0.00 amount in the basket, this has correctly referred you for the introductory offer. Apparently the $9.99 price thereafter shown on that screen is a mistake and the correct price of $2.50 is shown on a later screen in the process I think. Enter your credit card details and check out if you can. If not, continue.
  • Log into the CrashPlan PRO Admin Console as per these instructions, and download the CrashPlan PRO 4.9 client for Linux, and the 4.9 client for your remote console computer. Ignore the red message in the bottom left of the Admin Console about registering, and do not sign up for the free trial. Preferably use Firefox for the Linux version download – most of the other web browsers will try to unpack the .tgz archive, which you do not want to happen.
  • Configure the CrashPlan PRO 4.9 client on your computer to connect to your Syno as per the usual instructions on this blog post.
  • Put the downloaded Linux CrashPlan PRO 4.9 client .tgz file in the ‘public’ shared folder on your NAS. The package will no longer download this automatically as it did in previous versions.
  • From the Community section of DSM Package Center, install the CrashPlan PRO 4.9 package concurrently with your existing CrashPlan 4.8.3 Syno package.
  • This will stop the CrashPlan package and automatically import its configuration. Notice that it will also backup your old CrashPlan .identity file and leave it in the ‘public’ shared folder, just in case something goes wrong.
  • Start the CrashPlan PRO Synology package, and connect your CrashPlan PRO console from your computer.
  • You should see your protected folders as usual. At first mine reported something like “insufficient device licences”, but the next time I started up it changed to “subscription expired”.
  • Uninstall the CrashPlan 4.8.3 Synology package, this is no longer required.
  • At this point if the store referral didn’t work in the second step, you need to sign into the Admin Console. While signed in, navigate to this link which I was given by Code 42 support. If it works, you should see a store page with some blue font text and a $0.00 basket value. If it didn’t work you will get bounced to the Consumer Next Steps webpage: “Important Changes to CrashPlan for Home” – the one with the video of the CEO explaining the situation. I had to do this a few times before it worked. Once the store referral link worked and I had confirmed my payment details my CrashPlan PRO client immediately started working. Enjoy!
 

Notes

  • The package uses the intact CrashPlan installer directly from Code 42 Software, following acceptance of its EULA. I am complying with the directive that no one redistributes it.
  • The engine daemon script checks the amount of system RAM and scales the Java heap size appropriately (up to the default maximum of 512MB). This can be overridden in a persistent way if you are backing up large backup sets by editing /var/packages/CrashPlan/target/syno_package.vars. If you are considering buying a NAS purely to use CrashPlan and intend to back up more than a few hundred GB then I strongly advise buying one of the models with upgradeable RAM. Memory is very limited on the cheaper models. I have found that a 512MB heap was insufficient to back up more than 2TB of files on a Windows server and that was the situation many years ago. It kept restarting the backup engine every few minutes until I increased the heap to 1024MB. Many users of the package have found that they have to increase the heap size or CrashPlan will halt its activity. This can be mitigated by dividing your backup into several smaller backup sets which are scheduled to be protected at different times. Note that from package version 0041, using the dedicated JRE on a 64bit Intel NAS will allow a heap size greater than 4GB since the JRE is 64bit (requires DSM 6.0 in most cases).
  • If you need to manage CrashPlan from a remote location, I suggest you do so using SSH tunnelling as per this support document.
  • The package supports upgrading to future versions while preserving the machine identity, logs, login details, and cache. Upgrades can now take place without requiring a login from the client afterwards.
  • If you remove the package completely and re-install it later, you can re-attach to previous backups. When you log in to the Desktop Client with your existing account after a re-install, you can select “adopt computer” to merge the records, and preserve your existing backups. I haven’t tested whether this also re-attaches links to friends’ CrashPlan computers and backup sets, though the latter does seem possible in the Friends section of the GUI. It’s probably a good idea to test that this survives a package reinstall before you start relying on it. Sometimes, particularly with CrashPlan PRO I think, the adopt option is not offered. In this case you can log into CrashPlan Central and retrieve your computer’s GUID. On the CrashPlan client, double-click on the logo in the top right and you’ll enter a command line mode. You can use the GUID command to change the system’s GUID to the one you just retrieved from your account.
  • The log which is displayed in the package’s Log tab is actually the activity history. If you are trying to troubleshoot an issue you will need to use an SSH session to inspect these log files:
    /var/packages/CrashPlan/target/log/engine_output.log
    /var/packages/CrashPlan/target/log/engine_error.log
    /var/packages/CrashPlan/target/log/app.log
  • When CrashPlan downloads and attempts to run an automatic update, the script will most likely fail and stop the package. This is typically caused by syntax differences with the Synology versions of certain Linux shell commands (like rm, mv, or ps). The startup script will attempt to apply the published upgrade the next time the package is started.
  • Although CrashPlan’s activity can be scheduled within the application, in order to save RAM some users may wish to restrict running the CrashPlan engine to specific times of day using the Task Scheduler in DSM Control Panel:
    Schedule service start
    Note that regardless of real-time backup, by default CrashPlan will scan the whole backup selection for changes at 3:00am. Include this time within your Task Scheduler time window or else CrashPlan will not capture file changes which occurred while it was inactive:
    Schedule Service Start

  • If you decide to sign up for one of CrashPlan’s paid backup services as a result of my work on this, please consider donating using the PayPal button on the right of this page.
 

Package scripts

For information, here are the package scripts so you can see what it’s going to do. You can get more information about how packages work by reading the Synology 3rd Party Developer Guide.

installer.sh

#!/bin/sh

#--------CRASHPLAN installer script
#--------package maintained at pcloadletter.co.uk


DOWNLOAD_PATH="http://download2.code42.com/installs/linux/install/${SYNOPKG_PKGNAME}"
CP_EXTRACTED_FOLDER="crashplan-install"
OLD_JNA_NEEDED="false"
[ "${SYNOPKG_PKGNAME}" == "CrashPlan" ] && DOWNLOAD_FILE="CrashPlan_4.8.3_Linux.tgz"
[ "${SYNOPKG_PKGNAME}" == "CrashPlanPRO" ] && DOWNLOAD_FILE="CrashPlanPRO_4.*_Linux.tgz"
if [ "${SYNOPKG_PKGNAME}" == "CrashPlanPROe" ]; then
  CP_EXTRACTED_FOLDER="${SYNOPKG_PKGNAME}-install"
  OLD_JNA_NEEDED="true"
  [ "${WIZARD_VER_483}" == "true" ] && { CPPROE_VER="4.8.3"; CP_EXTRACTED_FOLDER="crashplan-install"; OLD_JNA_NEEDED="false"; }
  [ "${WIZARD_VER_480}" == "true" ] && { CPPROE_VER="4.8.0"; CP_EXTRACTED_FOLDER="crashplan-install"; OLD_JNA_NEEDED="false"; }
  [ "${WIZARD_VER_470}" == "true" ] && { CPPROE_VER="4.7.0"; CP_EXTRACTED_FOLDER="crashplan-install"; OLD_JNA_NEEDED="false"; }
  [ "${WIZARD_VER_460}" == "true" ] && { CPPROE_VER="4.6.0"; CP_EXTRACTED_FOLDER="crashplan-install"; OLD_JNA_NEEDED="false"; }
  [ "${WIZARD_VER_452}" == "true" ] && { CPPROE_VER="4.5.2"; CP_EXTRACTED_FOLDER="crashplan-install"; OLD_JNA_NEEDED="false"; }
  [ "${WIZARD_VER_450}" == "true" ] && { CPPROE_VER="4.5.0"; CP_EXTRACTED_FOLDER="crashplan-install"; OLD_JNA_NEEDED="false"; }
  [ "${WIZARD_VER_441}" == "true" ] && { CPPROE_VER="4.4.1"; CP_EXTRACTED_FOLDER="crashplan-install"; OLD_JNA_NEEDED="false"; }
  [ "${WIZARD_VER_430}" == "true" ] && CPPROE_VER="4.3.0"
  [ "${WIZARD_VER_420}" == "true" ] && CPPROE_VER="4.2.0"
  [ "${WIZARD_VER_370}" == "true" ] && CPPROE_VER="3.7.0"
  [ "${WIZARD_VER_364}" == "true" ] && CPPROE_VER="3.6.4"
  [ "${WIZARD_VER_363}" == "true" ] && CPPROE_VER="3.6.3"
  [ "${WIZARD_VER_3614}" == "true" ] && CPPROE_VER="3.6.1.4"
  [ "${WIZARD_VER_353}" == "true" ] && CPPROE_VER="3.5.3"
  [ "${WIZARD_VER_341}" == "true" ] && CPPROE_VER="3.4.1"
  [ "${WIZARD_VER_33}" == "true" ] && CPPROE_VER="3.3"
  DOWNLOAD_FILE="CrashPlanPROe_${CPPROE_VER}_Linux.tgz"
fi
DOWNLOAD_URL="${DOWNLOAD_PATH}/${DOWNLOAD_FILE}"
CPI_FILE="${SYNOPKG_PKGNAME}_*.cpi"
OPTDIR="${SYNOPKG_PKGDEST}"
VARS_FILE="${OPTDIR}/install.vars"
SYNO_CPU_ARCH="`uname -m`"
[ "${SYNO_CPU_ARCH}" == "x86_64" ] && SYNO_CPU_ARCH="i686"
[ "${SYNO_CPU_ARCH}" == "armv5tel" ] && SYNO_CPU_ARCH="armel"
[ "${SYNOPKG_DSM_ARCH}" == "armada375" ] && SYNO_CPU_ARCH="armv7l"
[ "${SYNOPKG_DSM_ARCH}" == "armada38x" ] && SYNO_CPU_ARCH="armhf"
[ "${SYNOPKG_DSM_ARCH}" == "comcerto2k" ] && SYNO_CPU_ARCH="armhf"
[ "${SYNOPKG_DSM_ARCH}" == "alpine" ] && SYNO_CPU_ARCH="armhf"
[ "${SYNOPKG_DSM_ARCH}" == "alpine4k" ] && SYNO_CPU_ARCH="armhf"
[ "${SYNOPKG_DSM_ARCH}" == "monaco" ] && SYNO_CPU_ARCH="armhf"
[ "${SYNOPKG_DSM_ARCH}" == "rtd1296" ] && SYNO_CPU_ARCH="armhf"
NATIVE_BINS_URL="http://packages.pcloadletter.co.uk/downloads/crashplan-native-${SYNO_CPU_ARCH}.tar.xz"   
NATIVE_BINS_FILE="`echo ${NATIVE_BINS_URL} | sed -r "s%^.*/(.*)%\1%"`"
OLD_JNA_URL="http://packages.pcloadletter.co.uk/downloads/crashplan-native-old-${SYNO_CPU_ARCH}.tar.xz"   
OLD_JNA_FILE="`echo ${OLD_JNA_URL} | sed -r "s%^.*/(.*)%\1%"`"
INSTALL_FILES="${DOWNLOAD_URL} ${NATIVE_BINS_URL}"
[ "${OLD_JNA_NEEDED}" == "true" ] && INSTALL_FILES="${INSTALL_FILES} ${OLD_JNA_URL}"
TEMP_FOLDER="`find / -maxdepth 2 -path '/volume?/@tmp' | head -n 1`"
#the Manifest folder is where friends' backup data is stored
#we set it outside the app folder so it persists after a package uninstall
MANIFEST_FOLDER="/`echo $TEMP_FOLDER | cut -f2 -d'/'`/crashplan"
LOG_FILE="${SYNOPKG_PKGDEST}/log/history.log.0"
UPGRADE_FILES="syno_package.vars conf/my.service.xml conf/service.login conf/service.model"
UPGRADE_FOLDERS="log cache"
PUBLIC_FOLDER="`synoshare --get public | sed -r "/Path/!d;s/^.*\[(.*)\].*$/\1/"`"
#dedicated JRE section
if [ "${WIZARD_JRE_CP}" == "true" ]; then
  DOWNLOAD_URL="http://tinyurl.com/javaembed"
  EXTRACTED_FOLDER="ejdk1.8.0_151"
  #detect systems capable of running 64bit JRE which can address more than 4GB of RAM
  [ "${SYNOPKG_DSM_ARCH}" == "x64" ] && SYNO_CPU_ARCH="x64"
  [ "`uname -m`" == "x86_64" ] && [ ${SYNOPKG_DSM_VERSION_MAJOR} -ge 6 ] && SYNO_CPU_ARCH="x64"
  if [ "${SYNO_CPU_ARCH}" == "armel" ]; then
    JAVA_BINARY="ejdk-8u151-linux-arm-sflt.tar.gz"
    JAVA_BUILD="ARMv5/ARMv6/ARMv7 Linux - SoftFP ABI, Little Endian 2"
  elif [ "${SYNO_CPU_ARCH}" == "armv7l" ]; then
    JAVA_BINARY="ejdk-8u151-linux-arm-sflt.tar.gz"
    JAVA_BUILD="ARMv5/ARMv6/ARMv7 Linux - SoftFP ABI, Little Endian 2"
  elif [ "${SYNO_CPU_ARCH}" == "armhf" ]; then
    JAVA_BINARY="ejdk-8u151-linux-armv6-vfp-hflt.tar.gz"
    JAVA_BUILD="ARMv6/ARMv7 Linux - VFP, HardFP ABI, Little Endian 1"
  elif [ "${SYNO_CPU_ARCH}" == "ppc" ]; then
    #Oracle have discontinued Java 8 for PowerPC after update 6
    JAVA_BINARY="ejdk-8u6-fcs-b23-linux-ppc-e500v2-12_jun_2014.tar.gz"
    JAVA_BUILD="Power Architecture Linux - Headless - e500v2 with double-precision SPE Floating Point Unit"
    EXTRACTED_FOLDER="ejdk1.8.0_06"
    DOWNLOAD_URL="http://tinyurl.com/java8ppc"
  elif [ "${SYNO_CPU_ARCH}" == "i686" ]; then
    JAVA_BINARY="ejdk-8u151-linux-i586.tar.gz"
    JAVA_BUILD="x86 Linux Small Footprint - Headless"
  elif [ "${SYNO_CPU_ARCH}" == "x64" ]; then
    JAVA_BINARY="jre-8u151-linux-x64.tar.gz"
    JAVA_BUILD="Linux x64"
    EXTRACTED_FOLDER="jre1.8.0_151"
    DOWNLOAD_URL="http://tinyurl.com/java8x64"
  fi
fi
JAVA_BINARY=`echo ${JAVA_BINARY} | cut -f1 -d'.'`
source /etc/profile


pre_checks ()
{
  #These checks are called from preinst and from preupgrade functions to prevent failures resulting in a partially upgraded package
  if [ "${WIZARD_JRE_CP}" == "true" ]; then
    synoshare -get public > /dev/null || (
      echo "A shared folder called 'public' could not be found - note this name is case-sensitive. " >> $SYNOPKG_TEMP_LOGFILE
      echo "Please create this using the Shared Folder DSM Control Panel and try again." >> $SYNOPKG_TEMP_LOGFILE
      exit 1
    )

    JAVA_BINARY_FOUND=
    [ -f ${PUBLIC_FOLDER}/${JAVA_BINARY}.tar.gz ] && JAVA_BINARY_FOUND=true
    [ -f ${PUBLIC_FOLDER}/${JAVA_BINARY}.tar ] && JAVA_BINARY_FOUND=true
    [ -f ${PUBLIC_FOLDER}/${JAVA_BINARY}.tar.tar ] && JAVA_BINARY_FOUND=true
    [ -f ${PUBLIC_FOLDER}/${JAVA_BINARY}.gz ] && JAVA_BINARY_FOUND=true
     
    if [ -z ${JAVA_BINARY_FOUND} ]; then
      echo "Java binary bundle not found. " >> $SYNOPKG_TEMP_LOGFILE
      echo "I was expecting the file ${PUBLIC_FOLDER}/${JAVA_BINARY}.tar.gz. " >> $SYNOPKG_TEMP_LOGFILE
      echo "Please agree to the Oracle licence at ${DOWNLOAD_URL}, then download the '${JAVA_BUILD}' package" >> $SYNOPKG_TEMP_LOGFILE
      echo "and place it in the 'public' shared folder on your NAS. This download cannot be automated even if " >> $SYNOPKG_TEMP_LOGFILE
      echo "displaying a package EULA could potentially cover the legal aspect, because files hosted on Oracle's " >> $SYNOPKG_TEMP_LOGFILE
      echo "server are protected by a session cookie requiring a JavaScript enabled browser." >> $SYNOPKG_TEMP_LOGFILE
      exit 1
    fi
  else
    if [ -z ${JAVA_HOME} ]; then
      echo "Java is not installed or not properly configured. JAVA_HOME is not defined. " >> $SYNOPKG_TEMP_LOGFILE
      echo "Download and install the Java Synology package from http://wp.me/pVshC-z5" >> $SYNOPKG_TEMP_LOGFILE
      exit 1
    fi

    if [ ! -f ${JAVA_HOME}/bin/java ]; then
      echo "Java is not installed or not properly configured. The Java binary could not be located. " >> $SYNOPKG_TEMP_LOGFILE
      echo "Download and install the Java Synology package from http://wp.me/pVshC-z5" >> $SYNOPKG_TEMP_LOGFILE
      exit 1
    fi

    if [ "${WIZARD_JRE_SYS}" == "true" ]; then
      JAVA_VER=`java -version 2>&1 | sed -r "/^.* version/!d;s/^.* version \"[0-9]\.([0-9]).*$/\1/"`
      if [ ${JAVA_VER} -lt 8 ]; then
        echo "This version of CrashPlan requires Java 8 or newer. Please update your Java package. "
        exit 1
      fi
    fi
  fi
}


preinst ()
{
  pre_checks
  cd ${TEMP_FOLDER}
  for WGET_URL in ${INSTALL_FILES}
  do
    WGET_FILENAME="`echo ${WGET_URL} | sed -r "s%^.*/(.*)%\1%"`"
    [ -f ${TEMP_FOLDER}/${WGET_FILENAME} ] && rm ${TEMP_FOLDER}/${WGET_FILENAME}
    wget ${WGET_URL}
    if [[ $? != 0 ]]; then
      if [ -d ${PUBLIC_FOLDER} ] && [ -f ${PUBLIC_FOLDER}/${WGET_FILENAME} ]; then
        cp ${PUBLIC_FOLDER}/${WGET_FILENAME} ${TEMP_FOLDER}
      else     
        echo "There was a problem downloading ${WGET_FILENAME} from the official download link, " >> $SYNOPKG_TEMP_LOGFILE
        echo "which was \"${WGET_URL}\" " >> $SYNOPKG_TEMP_LOGFILE
        echo "Alternatively, you may download this file manually and place it in the 'public' shared folder. " >> $SYNOPKG_TEMP_LOGFILE
        exit 1
      fi
    fi
  done
 
  exit 0
}


postinst ()
{
  if [ "${WIZARD_JRE_CP}" == "true" ]; then
    #extract Java (Web browsers love to interfere with .tar.gz files)
    cd ${PUBLIC_FOLDER}
    if [ -f ${JAVA_BINARY}.tar.gz ]; then
      #Firefox seems to be the only browser that leaves it alone
      tar xzf ${JAVA_BINARY}.tar.gz
    elif [ -f ${JAVA_BINARY}.gz ]; then
      #Chrome
      tar xzf ${JAVA_BINARY}.gz
    elif [ -f ${JAVA_BINARY}.tar ]; then
      #Safari
      tar xf ${JAVA_BINARY}.tar
    elif [ -f ${JAVA_BINARY}.tar.tar ]; then
      #Internet Explorer
      tar xzf ${JAVA_BINARY}.tar.tar
    fi
    mv ${EXTRACTED_FOLDER} ${SYNOPKG_PKGDEST}/jre-syno
    JRE_PATH="`find ${OPTDIR}/jre-syno/ -name jre`"
    [ -z ${JRE_PATH} ] && JRE_PATH=${OPTDIR}/jre-syno
    #change owner of folder tree
    chown -R root:root ${SYNOPKG_PKGDEST}
  fi
   
  #extract CPU-specific additional binaries
  mkdir ${SYNOPKG_PKGDEST}/bin
  cd ${SYNOPKG_PKGDEST}/bin
  tar xJf ${TEMP_FOLDER}/${NATIVE_BINS_FILE} && rm ${TEMP_FOLDER}/${NATIVE_BINS_FILE}
  [ "${OLD_JNA_NEEDED}" == "true" ] && tar xJf ${TEMP_FOLDER}/${OLD_JNA_FILE} && rm ${TEMP_FOLDER}/${OLD_JNA_FILE}

  #extract main archive
  cd ${TEMP_FOLDER}
  tar xzf ${TEMP_FOLDER}/${DOWNLOAD_FILE} && rm ${TEMP_FOLDER}/${DOWNLOAD_FILE} 
  
  #extract cpio archive
  cd ${SYNOPKG_PKGDEST}
  cat "${TEMP_FOLDER}/${CP_EXTRACTED_FOLDER}"/${CPI_FILE} | gzip -d -c - | ${SYNOPKG_PKGDEST}/bin/cpio -i --no-preserve-owner
  
  echo "#uncomment to expand Java max heap size beyond prescribed value (will survive upgrades)" > ${SYNOPKG_PKGDEST}/syno_package.vars
  echo "#you probably only want more than the recommended 1024M if you're backing up extremely large volumes of files" >> ${SYNOPKG_PKGDEST}/syno_package.vars
  echo "#USR_MAX_HEAP=1024M" >> ${SYNOPKG_PKGDEST}/syno_package.vars
  echo >> ${SYNOPKG_PKGDEST}/syno_package.vars

  cp ${TEMP_FOLDER}/${CP_EXTRACTED_FOLDER}/scripts/CrashPlanEngine ${OPTDIR}/bin
  cp ${TEMP_FOLDER}/${CP_EXTRACTED_FOLDER}/scripts/run.conf ${OPTDIR}/bin
  mkdir -p ${MANIFEST_FOLDER}/backupArchives    
  
  #save install variables which Crashplan expects its own installer script to create
  echo TARGETDIR=${SYNOPKG_PKGDEST} > ${VARS_FILE}
  echo BINSDIR=/bin >> ${VARS_FILE}
  echo MANIFESTDIR=${MANIFEST_FOLDER}/backupArchives >> ${VARS_FILE}
  #leave these ones out which should help upgrades from Code42 to work (based on examining an upgrade script)
  #echo INITDIR=/etc/init.d >> ${VARS_FILE}
  #echo RUNLVLDIR=/usr/syno/etc/rc.d >> ${VARS_FILE}
  echo INSTALLDATE=`date +%Y%m%d` >> ${VARS_FILE}
  [ "${WIZARD_JRE_CP}" == "true" ] && echo JAVACOMMON=${JRE_PATH}/bin/java >> ${VARS_FILE}
  [ "${WIZARD_JRE_SYS}" == "true" ] && echo JAVACOMMON=\${JAVA_HOME}/bin/java >> ${VARS_FILE}
  cat ${TEMP_FOLDER}/${CP_EXTRACTED_FOLDER}/install.defaults >> ${VARS_FILE}
  
  #remove temp files
  rm -r ${TEMP_FOLDER}/${CP_EXTRACTED_FOLDER}
  
  #add firewall config
  /usr/syno/bin/servicetool --install-configure-file --package /var/packages/${SYNOPKG_PKGNAME}/scripts/${SYNOPKG_PKGNAME}.sc > /dev/null
  
  #amend CrashPlanPROe client version
  [ "${SYNOPKG_PKGNAME}" == "CrashPlanPROe" ] && sed -i -r "s/^version=\".*(-.*$)/version=\"${CPPROE_VER}\1/" /var/packages/${SYNOPKG_PKGNAME}/INFO

  #are we transitioning an existing CrashPlan account to CrashPlan For Small Business?
  if [ "${SYNOPKG_PKGNAME}" == "CrashPlanPRO" ]; then
    if [ -e /var/packages/CrashPlan/scripts/start-stop-status ]; then
      /var/packages/CrashPlan/scripts/start-stop-status stop
      cp /var/lib/crashplan/.identity ${PUBLIC_FOLDER}/crashplan-identity.bak
      cp -R /var/packages/CrashPlan/target/conf/ ${OPTDIR}/
    fi  
  fi

  exit 0
}


preuninst ()
{
  `dirname $0`/stop-start-status stop

  exit 0
}


postuninst ()
{
  if [ -f ${SYNOPKG_PKGDEST}/syno_package.vars ]; then
    source ${SYNOPKG_PKGDEST}/syno_package.vars
  fi
  [ -e ${OPTDIR}/lib/libffi.so.5 ] && rm ${OPTDIR}/lib/libffi.so.5

  #delete symlink if it no longer resolves - PowerPC only
  if [ ! -e /lib/libffi.so.5 ]; then
    [ -L /lib/libffi.so.5 ] && rm /lib/libffi.so.5
  fi

  #remove firewall config
  if [ "${SYNOPKG_PKG_STATUS}" == "UNINSTALL" ]; then
    /usr/syno/bin/servicetool --remove-configure-file --package ${SYNOPKG_PKGNAME}.sc > /dev/null
  fi

 exit 0
}


preupgrade ()
{
  `dirname $0`/stop-start-status stop
  pre_checks
  #if identity exists back up config
  if [ -f /var/lib/crashplan/.identity ]; then
    mkdir -p ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/conf
    for FILE_TO_MIGRATE in ${UPGRADE_FILES}; do
      if [ -f ${OPTDIR}/${FILE_TO_MIGRATE} ]; then
        cp ${OPTDIR}/${FILE_TO_MIGRATE} ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/${FILE_TO_MIGRATE}
      fi
    done
    for FOLDER_TO_MIGRATE in ${UPGRADE_FOLDERS}; do
      if [ -d ${OPTDIR}/${FOLDER_TO_MIGRATE} ]; then
        mv ${OPTDIR}/${FOLDER_TO_MIGRATE} ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig
      fi
    done
  fi

  exit 0
}


postupgrade ()
{
  #use the migrated identity and config data from the previous version
  if [ -f ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/conf/my.service.xml ]; then
    for FILE_TO_MIGRATE in ${UPGRADE_FILES}; do
      if [ -f ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/${FILE_TO_MIGRATE} ]; then
        mv ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/${FILE_TO_MIGRATE} ${OPTDIR}/${FILE_TO_MIGRATE}
      fi
    done
    for FOLDER_TO_MIGRATE in ${UPGRADE_FOLDERS}; do
    if [ -d ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/${FOLDER_TO_MIGRATE} ]; then
      mv ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/${FOLDER_TO_MIGRATE} ${OPTDIR}
    fi
    done
    rmdir ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/conf
    rmdir ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig
    
    #make CrashPlan log entry
    TIMESTAMP="`date "+%D %I:%M%p"`"
    echo "I ${TIMESTAMP} Synology Package Center updated ${SYNOPKG_PKGNAME} to version ${SYNOPKG_PKGVER}" >> ${LOG_FILE}
  fi
  
  exit 0
}
 

start-stop-status.sh

#!/bin/sh

#--------CRASHPLAN start-stop-status script
#--------package maintained at pcloadletter.co.uk


TEMP_FOLDER="`find / -maxdepth 2 -path '/volume?/@tmp' | head -n 1`"
MANIFEST_FOLDER="/`echo $TEMP_FOLDER | cut -f2 -d'/'`/crashplan" 
ENGINE_CFG="run.conf"
PKG_FOLDER="`dirname $0 | cut -f1-4 -d'/'`"
DNAME="`dirname $0 | cut -f4 -d'/'`"
OPTDIR="${PKG_FOLDER}/target"
PID_FILE="${OPTDIR}/${DNAME}.pid"
DLOG="${OPTDIR}/log/history.log.0"
CFG_PARAM="SRV_JAVA_OPTS"
JAVA_MIN_HEAP=`grep "^${CFG_PARAM}=" "${OPTDIR}/bin/${ENGINE_CFG}" | sed -r "s/^.*-Xms([0-9]+)[Mm] .*$/\1/"` 
SYNO_CPU_ARCH="`uname -m`"
TIMESTAMP="`date "+%D %I:%M%p"`"
FULL_CP="${OPTDIR}/lib/com.backup42.desktop.jar:${OPTDIR}/lang"
source ${OPTDIR}/install.vars
source /etc/profile
source /root/.profile


start_daemon ()
{
  #check persistent variables from syno_package.vars
  USR_MAX_HEAP=0
  if [ -f ${OPTDIR}/syno_package.vars ]; then
    source ${OPTDIR}/syno_package.vars
  fi
  USR_MAX_HEAP=`echo $USR_MAX_HEAP | sed -e "s/[mM]//"`

  #do we need to restore the identity file - has a DSM upgrade scrubbed /var/lib/crashplan?
  if [ ! -e /var/lib/crashplan ]; then
    mkdir /var/lib/crashplan
    [ -e ${OPTDIR}/conf/var-backup/.identity ] && cp ${OPTDIR}/conf/var-backup/.identity /var/lib/crashplan/
  fi

  #fix up some of the binary paths and fix some command syntax for busybox 
  #moved this to start-stop-status.sh from installer.sh because Code42 push updates and these
  #new scripts will need this treatment too
  find ${OPTDIR}/ -name "*.sh" | while IFS="" read -r FILE_TO_EDIT; do
    if [ -e ${FILE_TO_EDIT} ]; then
      #this list of substitutions will probably need expanding as new CrashPlan updates are released
      sed -i "s%^#!/bin/bash%#!$/bin/sh%" "${FILE_TO_EDIT}"
      sed -i -r "s%(^\s*)(/bin/cpio |cpio ) %\1/${OPTDIR}/bin/cpio %" "${FILE_TO_EDIT}"
      sed -i -r "s%(^\s*)(/bin/ps|ps) [^w][^\|]*\|%\1/bin/ps w \|%" "${FILE_TO_EDIT}"
      sed -i -r "s%\`ps [^w][^\|]*\|%\`ps w \|%" "${FILE_TO_EDIT}"
      sed -i -r "s%^ps [^w][^\|]*\|%ps w \|%" "${FILE_TO_EDIT}"
      sed -i "s/rm -fv/rm -f/" "${FILE_TO_EDIT}"
      sed -i "s/mv -fv/mv -f/" "${FILE_TO_EDIT}"
    fi
  done

  #use this daemon init script rather than the unreliable Code42 stock one which greps the ps output
  sed -i "s%^ENGINE_SCRIPT=.*$%ENGINE_SCRIPT=$0%" ${OPTDIR}/bin/restartLinux.sh

  #any downloaded upgrade script will usually have failed despite the above changes
  #so ignore the script and explicitly extract the new java code using the chrisnelson.ca method 
  #thanks to Jeff Bingham for tweaks 
  UPGRADE_JAR=`find ${OPTDIR}/upgrade -maxdepth 1 -name "*.jar" | tail -1`
  if [ -n "${UPGRADE_JAR}" ]; then
    rm ${OPTDIR}/*.pid > /dev/null
 
    #make CrashPlan log entry
    echo "I ${TIMESTAMP} Synology extracting upgrade from ${UPGRADE_JAR}" >> ${DLOG}

    UPGRADE_VER=`echo ${SCRIPT_HOME} | sed -r "s/^.*\/([0-9_]+)\.[0-9]+/\1/"`
    #DSM 6.0 no longer includes unzip, use 7z instead
    unzip -o ${OPTDIR}/upgrade/${UPGRADE_VER}.jar "*.jar" -d ${OPTDIR}/lib/ || 7z e -y ${OPTDIR}/upgrade/${UPGRADE_VER}.jar "*.jar" -o${OPTDIR}/lib/ > /dev/null
    unzip -o ${OPTDIR}/upgrade/${UPGRADE_VER}.jar "lang/*" -d ${OPTDIR} || 7z e -y ${OPTDIR}/upgrade/${UPGRADE_VER}.jar "lang/*" -o${OPTDIR} > /dev/null
    mv ${UPGRADE_JAR} ${TEMP_FOLDER}/ > /dev/null
    exec $0
  fi

  #updates may also overwrite our native binaries
  [ -e ${OPTDIR}/bin/libffi.so.5 ] && cp -f ${OPTDIR}/bin/libffi.so.5 ${OPTDIR}/lib/
  [ -e ${OPTDIR}/bin/libjtux.so ] && cp -f ${OPTDIR}/bin/libjtux.so ${OPTDIR}/
  [ -e ${OPTDIR}/bin/jna-3.2.5.jar ] && cp -f ${OPTDIR}/bin/jna-3.2.5.jar ${OPTDIR}/lib/
  if [ -e ${OPTDIR}/bin/jna.jar ] && [ -e ${OPTDIR}/lib/jna.jar ]; then
    cp -f ${OPTDIR}/bin/jna.jar ${OPTDIR}/lib/
  fi

  #create or repair libffi.so.5 symlink if a DSM upgrade has removed it - PowerPC only
  if [ -e ${OPTDIR}/lib/libffi.so.5 ]; then
    if [ ! -e /lib/libffi.so.5 ]; then
      #if it doesn't exist, but is still a link then it's a broken link and should be deleted first
      [ -L /lib/libffi.so.5 ] && rm /lib/libffi.so.5
      ln -s ${OPTDIR}/lib/libffi.so.5 /lib/libffi.so.5
    fi
  fi

  #set appropriate Java max heap size
  RAM=$((`free | grep Mem: | sed -e "s/^ *Mem: *\([0-9]*\).*$/\1/"`/1024))
  if [ $RAM -le 128 ]; then
    JAVA_MAX_HEAP=80
  elif [ $RAM -le 256 ]; then
    JAVA_MAX_HEAP=192
  elif [ $RAM -le 512 ]; then
    JAVA_MAX_HEAP=384
  elif [ $RAM -le 1024 ]; then
    JAVA_MAX_HEAP=512
  elif [ $RAM -gt 1024 ]; then
    JAVA_MAX_HEAP=1024
  fi
  if [ $USR_MAX_HEAP -gt $JAVA_MAX_HEAP ]; then
    JAVA_MAX_HEAP=${USR_MAX_HEAP}
  fi   
  if [ $JAVA_MAX_HEAP -lt $JAVA_MIN_HEAP ]; then
    #can't have a max heap lower than min heap (ARM low RAM systems)
    $JAVA_MAX_HEAP=$JAVA_MIN_HEAP
  fi
  sed -i -r "s/(^${CFG_PARAM}=.*) -Xmx[0-9]+[mM] (.*$)/\1 -Xmx${JAVA_MAX_HEAP}m \2/" "${OPTDIR}/bin/${ENGINE_CFG}"
  
  #disable the use of the x86-optimized external Fast MD5 library if running on ARM and PPC CPUs
  #seems to be the default behaviour now but that may change again
  [ "${SYNO_CPU_ARCH}" == "x86_64" ] && SYNO_CPU_ARCH="i686"
  if [ "${SYNO_CPU_ARCH}" != "i686" ]; then
    grep "^${CFG_PARAM}=.*c42\.native\.md5\.enabled" "${OPTDIR}/bin/${ENGINE_CFG}" > /dev/null \
     || sed -i -r "s/(^${CFG_PARAM}=\".*)\"$/\1 -Dc42.native.md5.enabled=false\"/" "${OPTDIR}/bin/${ENGINE_CFG}"
  fi

  #move the Java temp directory from the default of /tmp
  grep "^${CFG_PARAM}=.*Djava\.io\.tmpdir" "${OPTDIR}/bin/${ENGINE_CFG}" > /dev/null \
   || sed -i -r "s%(^${CFG_PARAM}=\".*)\"$%\1 -Djava.io.tmpdir=${TEMP_FOLDER}\"%" "${OPTDIR}/bin/${ENGINE_CFG}"

  #now edit the XML config file, which only exists after first run
  if [ -f ${OPTDIR}/conf/my.service.xml ]; then

    #allow direct connections from CrashPlan Desktop client on remote systems
    #you must edit the value of serviceHost in conf/ui.properties on the client you connect with
    #users report that this value is sometimes reset so now it's set every service startup 
    sed -i "s/<serviceHost>127\.0\.0\.1<\/serviceHost>/<serviceHost>0\.0\.0\.0<\/serviceHost>/" "${OPTDIR}/conf/my.service.xml"
    #default changed in CrashPlan 4.3
    sed -i "s/<serviceHost>localhost<\/serviceHost>/<serviceHost>0\.0\.0\.0<\/serviceHost>/" "${OPTDIR}/conf/my.service.xml"
    #since CrashPlan 4.4 another config file to allow remote console connections
    sed -i "s/127\.0\.0\.1/0\.0\.0\.0/" /var/lib/crashplan/.ui_info
     
    #this change is made only once in case you want to customize the friends' backup location
    if [ "${MANIFEST_PATH_SET}" != "True" ]; then

      #keep friends' backup data outside the application folder to make accidental deletion less likely 
      sed -i "s%<manifestPath>.*</manifestPath>%<manifestPath>${MANIFEST_FOLDER}/backupArchives/</manifestPath>%" "${OPTDIR}/conf/my.service.xml"
      echo "MANIFEST_PATH_SET=True" >> ${OPTDIR}/syno_package.vars
    fi

    #since CrashPlan version 3.5.3 the value javaMemoryHeapMax also needs setting to match that used in bin/run.conf
    sed -i -r "s%(<javaMemoryHeapMax>)[0-9]+[mM](</javaMemoryHeapMax>)%\1${JAVA_MAX_HEAP}m\2%" "${OPTDIR}/conf/my.service.xml"

    #make sure CrashPlan is not binding to the IPv6 stack
    grep "\-Djava\.net\.preferIPv4Stack=true" "${OPTDIR}/bin/${ENGINE_CFG}" > /dev/null \
     || sed -i -r "s/(^${CFG_PARAM}=\".*)\"$/\1 -Djava.net.preferIPv4Stack=true\"/" "${OPTDIR}/bin/${ENGINE_CFG}"
   else
    echo "Check the package log to ensure the package has started successfully, then stop and restart the package to allow desktop client connections." > "${SYNOPKG_TEMP_LOGFILE}"
  fi

  #increase the system-wide maximum number of open files from Synology default of 24466
  [ `cat /proc/sys/fs/file-max` -lt 65536 ] && echo "65536" > /proc/sys/fs/file-max

  #raise the maximum open file count from the Synology default of 1024 - thanks Casper K. for figuring this out
  #http://support.code42.com/Administrator/3.6_And_4.0/Troubleshooting/Too_Many_Open_Files
  ulimit -n 65536

  #ensure that Code 42 have not amended install.vars to force the use of their own (Intel) JRE
  if [ -e ${OPTDIR}/jre-syno ]; then
    JRE_PATH="`find ${OPTDIR}/jre-syno/ -name jre`"
    [ -z ${JRE_PATH} ] && JRE_PATH=${OPTDIR}/jre-syno
    sed -i -r "s|^(JAVACOMMON=).*$|\1\${JRE_PATH}/bin/java|" ${OPTDIR}/install.vars
    
    #if missing, set timezone and locale for dedicated JRE   
    if [ -z ${TZ} ]; then
      SYNO_TZ=`cat /etc/synoinfo.conf | grep timezone | cut -f2 -d'"'`
      #fix for DST time in DSM 5.2 thanks to MinimServer Syno package author
      [ -e /usr/share/zoneinfo/Timezone/synotztable.json ] \
       && SYNO_TZ=`jq ".${SYNO_TZ} | .nameInTZDB" /usr/share/zoneinfo/Timezone/synotztable.json | sed -e "s/\"//g"` \
       || SYNO_TZ=`grep "^${SYNO_TZ}" /usr/share/zoneinfo/Timezone/tzname | sed -e "s/^.*= //"`
      export TZ=${SYNO_TZ}
    fi
    [ -z ${LANG} ] && export LANG=en_US.utf8
    export CLASSPATH=.:${OPTDIR}/jre-syno/lib

  else
    sed -i -r "s|^(JAVACOMMON=).*$|\1\${JAVA_HOME}/bin/java|" ${OPTDIR}/install.vars
  fi

  source ${OPTDIR}/bin/run.conf
  source ${OPTDIR}/install.vars
  cd ${OPTDIR}
  $JAVACOMMON $SRV_JAVA_OPTS -classpath $FULL_CP com.backup42.service.CPService > ${OPTDIR}/log/engine_output.log 2> ${OPTDIR}/log/engine_error.log &
  if [ $! -gt 0 ]; then
    echo $! > $PID_FILE
    renice 19 $! > /dev/null
    if [ -z "${SYNOPKG_PKGDEST}" ]; then
      #script was manually invoked, need this to show status change in Package Center      
      [ -e ${PKG_FOLDER}/enabled ] || touch ${PKG_FOLDER}/enabled
    fi
  else
    echo "${DNAME} failed to start, check ${OPTDIR}/log/engine_error.log" > "${SYNOPKG_TEMP_LOGFILE}"
    echo "${DNAME} failed to start, check ${OPTDIR}/log/engine_error.log" >&2
    exit 1
  fi
}

stop_daemon ()
{
  echo "I ${TIMESTAMP} Stopping ${DNAME}" >> ${DLOG}
  kill `cat ${PID_FILE}`
  wait_for_status 1 20 || kill -9 `cat ${PID_FILE}`
  rm -f ${PID_FILE}
  if [ -z ${SYNOPKG_PKGDEST} ]; then
    #script was manually invoked, need this to show status change in Package Center
    [ -e ${PKG_FOLDER}/enabled ] && rm ${PKG_FOLDER}/enabled
  fi
  #backup identity file in case DSM upgrade removes it
  [ -e ${OPTDIR}/conf/var-backup ] || mkdir ${OPTDIR}/conf/var-backup 
  cp /var/lib/crashplan/.identity ${OPTDIR}/conf/var-backup/
}

daemon_status ()
{
  if [ -f ${PID_FILE} ] && kill -0 `cat ${PID_FILE}` > /dev/null 2>&1; then
    return
  fi
  rm -f ${PID_FILE}
  return 1
}

wait_for_status ()
{
  counter=$2
  while [ ${counter} -gt 0 ]; do
    daemon_status
    [ $? -eq $1 ] && return
    let counter=counter-1
    sleep 1
  done
  return 1
}


case $1 in
  start)
    if daemon_status; then
      echo ${DNAME} is already running with PID `cat ${PID_FILE}`
      exit 0
    else
      echo Starting ${DNAME} ...
      start_daemon
      exit $?
    fi
  ;;

  stop)
    if daemon_status; then
      echo Stopping ${DNAME} ...
      stop_daemon
      exit $?
    else
      echo ${DNAME} is not running
      exit 0
    fi
  ;;

  restart)
    stop_daemon
    start_daemon
    exit $?
  ;;

  status)
    if daemon_status; then
      echo ${DNAME} is running with PID `cat ${PID_FILE}`
      exit 0
    else
      echo ${DNAME} is not running
      exit 1
    fi
  ;;

  log)
    echo "${DLOG}"
    exit 0
  ;;

  *)
    echo "Usage: $0 {start|stop|status|restart}" >&2
    exit 1
  ;;

esac
 

install_uifile & upgrade_uifile

[
  {
    "step_title": "Client Version Selection",
    "items": [
      {
        "type": "singleselect",
        "desc": "Please select the CrashPlanPROe client version that is appropriate for your backup destination server:",
        "subitems": [
          {
            "key": "WIZARD_VER_483",
            "desc": "4.8.3",
            "defaultValue": true
          },          {
            "key": "WIZARD_VER_480",
            "desc": "4.8.0",
            "defaultValue": false
          },
          {
            "key": "WIZARD_VER_470",
            "desc": "4.7.0",
            "defaultValue": false
          },
          {
            "key": "WIZARD_VER_460",
            "desc": "4.6.0",
            "defaultValue": false
          },
          {
            "key": "WIZARD_VER_452",
            "desc": "4.5.2",
            "defaultValue": false
          },
          {
            "key": "WIZARD_VER_450",
            "desc": "4.5.0",
            "defaultValue": false
          },
          {
            "key": "WIZARD_VER_441",
            "desc": "4.4.1",
            "defaultValue": false
          },
          {
            "key": "WIZARD_VER_430",
            "desc": "4.3.0",
            "defaultValue": false
          },
          {
            "key": "WIZARD_VER_420",
            "desc": "4.2.0",
            "defaultValue": false
          },
          {
            "key": "WIZARD_VER_370",
            "desc": "3.7.0",
            "defaultValue": false
          },
          {
            "key": "WIZARD_VER_364",
            "desc": "3.6.4",
            "defaultValue": false
          },
          {
            "key": "WIZARD_VER_363",
            "desc": "3.6.3",
            "defaultValue": false
          },
          {
            "key": "WIZARD_VER_3614",
            "desc": "3.6.1.4",
            "defaultValue": false
          },
          {
            "key": "WIZARD_VER_353",
            "desc": "3.5.3",
            "defaultValue": false
          },
          {
            "key": "WIZARD_VER_341",
            "desc": "3.4.1",
            "defaultValue": false
          },
          {
            "key": "WIZARD_VER_33",
            "desc": "3.3",
            "defaultValue": false
          }
        ]
      }
    ]
  },
  {
    "step_title": "Java Runtime Environment Selection",
    "items": [
      {
        "type": "singleselect",
        "desc": "Please select the Java version which you would like CrashPlan to use:",
        "subitems": [
          {
            "key": "WIZARD_JRE_SYS",
            "desc": "Default system Java version",
            "defaultValue": false
          },
          {
            "key": "WIZARD_JRE_CP",
            "desc": "Dedicated installation of Java 8",
            "defaultValue": true
          }
        ]
      }
    ]
  }
]
 

Changelog:

  • 0031 Added TCP 4242 to the firewall services (computer to computer connections)
  • 0047 30/Oct/17 – Updated dedicated Java version to 8 update 151, added support for additional Intel CPUs in x18 Synology products.
  • 0046 26/Aug/17 – Updated to CrashPlan PRO 4.9, added support for migration from CrashPlan For Home to CrashPlan For Small Business (CrashPlan PRO). Please read the Migration section on this page for instructions.
  • 0045 02/Aug/17 – Updated to CrashPlan 4.8.3, updated dedicated Java version to 8 update 144
  • 0044 21/Jan/17 – Updated dedicated Java version to 8 update 121
  • 0043 07/Jan/17 – Updated dedicated Java version to 8 update 111, added support for Intel Broadwell and Grantley CPUs
  • 0042 03/Oct/16 – Updated to CrashPlan 4.8.0, Java 8 is now required, added optional dedicated Java 8 Runtime instead of the default system one including 64bit Java support on 64 bit Intel CPUs to permit memory allocation larger than 4GB. Support for non-Intel platforms withdrawn owing to Code42’s reliance on proprietary native code library libc42archive.so
  • 0041 20/Jul/16 – Improved auto-upgrade compatibility (hopefully), added option to have CrashPlan use a dedicated Java 7 Runtime instead of the default system one, including 64bit Java support on 64 bit Intel CPUs to permit memory allocation larger than 4GB
  • 0040 25/May/16 – Added cpio to the path in the running context of start-stop-status.sh
  • 0039 25/May/16 – Updated to CrashPlan 4.7.0, at each launch forced the use of the system JRE over the CrashPlan bundled Intel one, added Maven build of JNA 4.1.0 for ARMv7 systems consistent with the version bundled with CrashPlan
  • 0038 27/Apr/16 – Updated to CrashPlan 4.6.0, and improved support for Code 42 pushed updates
  • 0037 21/Jan/16 – Updated to CrashPlan 4.5.2
  • 0036 14/Dec/15 – Updated to CrashPlan 4.5.0, separate firewall definitions for management client and for friends backup, added support for DS716+ and DS216play
  • 0035 06/Nov/15 – Fixed the update to 4.4.1_59, new installs now listen for remote connections after second startup (was broken from 4.4), updated client install documentation with more file locations and added a link to a new Code42 support doc
    EITHER completely remove and reinstall the package (which will require a rescan of the entire backup set) OR alternatively please delete all except for one of the failed upgrade numbered subfolders in /var/packages/CrashPlan/target/upgrade before upgrading. There will be one folder for each time CrashPlan tried and failed to start since Code42 pushed the update
  • 0034 04/Oct/15 – Updated to CrashPlan 4.4.1, bundled newer JNA native libraries to match those from Code42, PLEASE READ UPDATED BLOG POST INSTRUCTIONS FOR CLIENT INSTALL this version introduced yet another requirement for the client
  • 0033 12/Aug/15 – Fixed version 0032 client connection issue for fresh installs
  • 0032 12/Jul/15 – Updated to CrashPlan 4.3, PLEASE READ UPDATED BLOG POST INSTRUCTIONS FOR CLIENT INSTALL this version introduced an extra requirement, changed update repair to use the chrisnelson.ca method, forced CrashPlan to prefer IPv4 over IPv6 bindings, removed some legacy version migration scripting, updated main blog post documentation
  • 0031 20/May/15 – Updated to CrashPlan 4.2, cross compiled a newer cpio binary for some architectures which were segfaulting while unpacking main CrashPlan archive, added port 4242 to the firewall definition (friend backups), package is now signed with repository private key
  • 0030 16/Feb/15 – Fixed show-stopping issue with version 0029 for systems with more than one volume
  • 0029 21/Jan/15 – 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
  • 0028 22/Oct/14 – Substantial re-write:
    Updated to CrashPlan version 3.6.4
    DSM 5.0 or newer is now required
    libjnidispatch.so taken from Debian JNA 3.2.7 package with dependency on newer libffi.so.6 (included in DSM 5.0)
    jna-3.2.5.jar emptied of irrelevant CPU architecture libs to reduce size
    Increased default max heap size from 512MB to 1GB on systems with more than 1GB RAM
    Intel CPUs no longer need the awkward glibc version-faking shim to enable inotify support (for real-time backup)
    Switched to using root account – no more adding account permissions for backup, package upgrades will no longer break this
    DSM Firewall application definition added
    Tested with DSM Task Scheduler to allow backups between certain times of day only, saving RAM when not in use
    Daemon init script now uses a proper PID file instead of Code42’s unreliable method of using grep on the output of ps
    Daemon init script can be run from the command line
    Removal of bash binary dependency now Code42’s CrashPlanEngine script is no longer used
    Removal of nice binary dependency, using BusyBox equivalent renice
    Unified ARMv5 and ARMv7 external binary package (armle)
    Added support for Mindspeed Comcerto 2000 CPU (comcerto2k – armhf) in DS414j
    Added support for Intel Atom C2538 (avoton) CPU in DS415+
    Added support to choose which version of CrashPlan PROe client to download, since some servers may still require legacy versions
    Switched to .tar.xz compression for native binaries to reduce web hosting footprint
  • 0027 20/Mar/14 – Fixed open file handle limit for very large backup sets (ulimit fix)
  • 0026 16/Feb/14 – Updated all CrashPlan clients to version 3.6.3, improved handling of Java temp files
  • 0025 30/Jan/14 – glibc version shim no longer used on Intel Synology models running DSM 5.0
  • 0024 30/Jan/14 – Updated to CrashPlan PROe 3.6.1.4 and added support for PowerPC 2010 Synology models running DSM 5.0
  • 0023 30/Jan/14 – Added support for Intel Atom Evansport and Armada XP CPUs in new DSx14 products
  • 0022 10/Jun/13 – Updated all CrashPlan client versions to 3.5.3, compiled native binary dependencies to add support for Armada 370 CPU (DS213j), start-stop-status.sh now updates the new javaMemoryHeapMax value in my.service.xml to the value defined in syno_package.vars
  • 0021 01/Mar/13 – Updated CrashPlan to version 3.5.2
  • 0020 21/Jan/13 – Fixes for DSM 4.2
  • 018 Updated CrashPlan PRO to version 3.4.1
  • 017 Updated CrashPlan and CrashPlan PROe to version 3.4.1, and improved in-app update handling
  • 016 Added support for Freescale QorIQ CPUs in some x13 series Synology models, and installer script now downloads native binaries separately to reduce repo hosting bandwidth, PowerQUICC PowerPC processors in previous Synology generations with older glibc versions are not supported
  • 015 Added support for easy scheduling via cron – see updated Notes section
  • 014 DSM 4.1 user profile permissions fix
  • 013 implemented update handling for future automatic updates from Code 42, and incremented CrashPlanPRO client to release version 3.2.1
  • 012 incremented CrashPlanPROe client to release version 3.3
  • 011 minor fix to allow a wildcard on the cpio archive name inside the main installer package (to fix CP PROe client since Code 42 Software had amended the cpio file version to 3.2.1.2)
  • 010 minor bug fix relating to daemon home directory path
  • 009 rewrote the scripts to be even easier to maintain and unified as much as possible with my imminent CrashPlan PROe server package, fixed a timezone bug (tightened regex matching), moved the script-amending logic from installer.sh to start-stop-status.sh with it now applying to all .sh scripts each startup so perhaps updates from Code42 might work in future, if wget fails to fetch the installer from Code42 the installer will look for the file in the public shared folder
  • 008 merged the 14 package scripts each (7 for ARM, 7 for Intel) for CP, CP PRO, & CP PROe – 42 scripts in total – down to just two! ARM & Intel are now supported by the same package, Intel synos now have working inotify support (Real-Time Backup) thanks to rwojo’s shim to pass the glibc version check, upgrade process now retains login, cache and log data (no more re-scanning), users can specify a persistent larger max heap size for very large backup sets
  • 007 fixed a bug that broke CrashPlan if the Java folder moved (if you changed version)
  • 006 installation now fails without User Home service enabled, fixed Daylight Saving Time support, automated replacing the ARM libffi.so symlink which is destroyed by DSM upgrades, stopped assuming the primary storage volume is /volume1, reset ownership on /var/lib/crashplan and the Friends backup location after installs and upgrades
  • 005 added warning to restart daemon after 1st run, and improved upgrade process again
  • 004 updated to CrashPlan 3.2.1 and improved package upgrade process, forced binding to 0.0.0.0 each startup
  • 003 fixed ownership of /volume1/crashplan folder
  • 002 updated to CrashPlan 3.2
  • 001 30/Jan/12 – intial public release
 
 

6,692 thoughts on “CrashPlan packages for Synology NAS

  1. Hans's avatarHans

    How do I make the recent upgrade from Code 42 to run? I tried to make some changes to the upgrade.sh script, but with no succes.

    Reply
  2. Dale's avatarDale

    Crashplan PRO auto updated sometime during the night. Running version 4.2.0-31 on the Synology DS214+. The 4.2.0 client on my PC refuses to connect, and the service repeatedly stops on the NAS. Manually updated to 4.3.0 on the client, and reinstalled the synology package. Tried the echo `cat /var/lib/crashplan/.ui_info` command in ssh but it reports that the .ui_info file does not exist. Further exploration reveals that the /var/lib/crashplan directory appears to be empty. The service will run on the synology for a while after reinstallation, but inevitably stops and cannot be restarted, and the client refuses to connect.

    Reply
  3. CorpRoadie's avatarCorpRoadie

    I am getting an error when I SSH in and try to echo.

    cat: can’t open ‘/var/lib/crashplan/.ui_info’: No such file or directory

    Reply
      1. Gary's avatarGary

        I’m having the same problem as well. I do not have a /var/lib/crashplan directory.

        DiskStation> ls /var/lib
        nfs

        If I create one and then restart the service, it gets removed. I’m logged in as root.

      2. streetographer's avatarstreetographer

        I’m having the same problem as well. I do not have a /var/lib/crashplan directory.

        DiskStation> ls /var/lib
        nfs

        If I create one and then restart the service, it gets removed. I’m logged in as root.

      3. patters's avatarpatters Post author

        Download this on your computer:
        http://packages.pcloadletter.co.uk/downloads/old/crashplan4.2.0-merged-0031.spk

        and use it to manually upgrade in DSM (over the top of your 3.6.3-0027 version). Start and stop the package a couple of times, giving it a minute to start properly (check the log). This will ensure your settings from the legacy package with the dedicated ‘crashplan’ user account are migrated to root. Once you’ve done that, use Package Center to upgrade to the latest one from the repo.

      4. patters's avatarpatters Post author

        I know you have now upgraded your DSM, but I should mention that the DSM 5.0 minimum requirement isn’t only about the repository – the package itself now has dependencies on binaries that are only present on DSM 5.0 or later systems. Intel CPU Synos finally gained inotify support via CrashPlan and the ability to run Java newer than version 6 at DSM 5.0 so it was an important baseline.

  4. Dale's avatarDale

    Apparently, after I had applied the fix for 1427864400430 it auto-updated to 1427864410430 and stopped again. After applying the fix to 1427864410430 I am able to connect and it immediately began synchronizing. It appears that all is well and the backup selection was maintained.

    Reply
    1. Gary's avatarGary

      I am not able to connect at all. Mine is trying to update to from 4400430 to 4410430 but after it finishes, Crashplan stops running. I attempt to run it again the log tells me it attempts to apply the upgrade again then goes into an infinite loop of Synology repair attempts. I am running an Intel DS 1815+ with DSM 5.2-5592 with Crashplan version-4.2.0-0031. My last log line “Synology repairing upgrade in var/packages/CrashPlan/target/upgrade/14278644……long string of numbers.”

      This line repeats each time I attempt to run CrashPlan. I have uninstalled CrashPlan and reinstalled it several times. I have restarted the DS several times. I have tried to install the old version of CrashPlan and have it not update so it will run. I am just not able to get this last update to run. Please help if you can.

      Reply
    2. Fabien's avatarFabien

      Hi Dale,

      I’ve done the same thing, everyhting seems to be fine from a Server Crashplan perspective, but I’m not able to connect to server through client.

      Do you have an idea ?

      Thank you.

      Fabien

      Reply
      1. stevens420's avatarstevens420

        You may need to copy your GUID from the server to the ui_info file in C:\ProgramData\CrashPlan\.ui_info

        After that I was able to connect. Read the updated notes at the top of the thread, which covers this.

      1. Wendell de Moura's avatarWendell de Moura

        So I installed the new update (4.3.0) and the service is now running smoothly on the server, however I cannot connect the client to it, I have changed both the .ui_info and ui.properties to match my setup but the client just hangs on the splash and eventually times out. Anything else I am missing?

  5. john kenny's avatarjohn kenny

    Hi – I upgraded to 4.2.0-0031 running on DSM 5.2-5592. The service will not start and the log says:

    CrashPlan stopped, version 4.2.0 GUID 629248240205693169
    “Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1427864400430.1436311417269”

    Have tried uninstalling and reinstalling CrashPlan and also reboted the Synology….

    Reply
    1. john kenny's avatarjohn kenny

      Hi – I upgraded to 4.2.0-0031 running on DSM 5.2-5592. The service will not start.

      I tried reinstalling and rebooting but still had the same problem.
      I then uninstalled and reinstalled both Java and CrashPlan and initially it worked…however after a short time it stopped and now I cannot restart it again.
      Looking at the log, I am thinking that it works until a background upgrade is performed and then it stops and cannot be restarted again…..log below:

      I 07/08/15 01:37AM CrashPlan started, version 4.2.0, GUID 629248240205693169
      I 07/08/15 10:37AM Stopping CrashPlan
      I 07/08/15 01:38AM CrashPlan started, version 4.2.0, GUID 629248240205693169
      I 07/08/15 01:38AM Upgrades available at central.crashplan.com:443
      I 07/08/15 01:38AM Downloading a new version of CrashPlan.
      I 07/08/15 01:39AM Download of upgrade complete – version 1427864400430.
      I 07/08/15 01:39AM Download of upgrade complete – version 1427864410430.
      I 07/08/15 01:39AM CrashPlan has downloaded an update and will restart momentarily to apply the update.
      I 07/08/15 01:40AM Installing upgrade – version 1427864400430
      I 07/08/15 01:40AM Upgrade installed – version 1427864400430
      I 07/08/15 01:40AM CrashPlan stopped, version 4.2.0, GUID 629248240205693169
      I 07/08/15 10:40AM Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1427864400430.1436319614344
      I 07/08/15 10:43AM Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1427864400430.1436319614344

      Reply
  6. Per's avatarPer

    Hi Patters,

    Do you think that your pkg would run on a DS715 or DS215+ without any modifcations? I’m planning to finally replace my DS213+.

    Regards,
    Per

    Reply
    1. Robbert Marrink's avatarRobbert Marrink

      Please tell me what fix. It seems my package stopped again on my Synology and I’m unable to start it again. Same upgrade issue 1427864400430 to 1427864410430

      Reply
    2. Fabien's avatarFabien

      Hello,
      The fix is not working on my NAS DS415+.

      I have both 1427864400430 and 1427864410430 jar files and also a 1427864400430.* folder.

      I tried to apply fix but it’s not working.

      Package doesn’t launch and log still shows :
      Synology repairing upgrade……

      Could anyobody help please ?

      Thank you.

      Fabien

      Reply
  7. Gary's avatarGary

    I was not as lucky as Dale. My DS 1815+ applied the fix for 1427864400430 it auto-updated to 1427864410430 and stopped again. After applying the fix to 1427864410430, the DS stopped CrashPlan and is in a constant loop of attempting to repair the “upgrade” according to the log. I do not know what fix Dale applied to 1427864410430 that enabled his DS to connect and backup again. Please advise. Thanks a ton.

    Reply
  8. JK's avatarJK

    I am having trouble with the step to run the SSH to get the GUID, running echo `cat /var/lib/crashplan/.ui_info` in putty connected as root. is that the way to do this please?

    Reply
  9. Jake's avatarJake

    @Dale – what fix did you apply? I’m having the same issue on my 1511+ and can’t seem to fix it yet.

    Reply
  10. Jon Kensy's avatarJon Kensy

    Hey guys – had this setup between a windows VM and my friends DS214. It was working fine for a long time and now his Crashplan won’t start on his DS214. His DS214 reports Crashplan is 4.2.0-0031 – his DSM version is DSM 5.2-5565 Update 2. I try to “Run” the package as it shows “stopped” and it just comes back “stopped”.

    Reply
  11. Anil's avatarAnil

    Patters, can you please provide a link to the Crashplan package for DSM4.x. I really need this because I cannot afford to buy a new DS with DSM5.x and my backups are not running.

    Thanks in advance.

    Reply
    1. patters's avatarpatters Post author

      If you have a Synology which is stuck on DSM 4.3 then it must be a DSx09. The Java package would not run on PowerPC systems until DSM 5.0 so I’m afraid I cannot help. There was a package that used a chroot environment specifically for those older models, but I don’t know if it’s being actively maintained:
      http://chreggy.fr/thegeek/2012/01/10/crashplan-sur-un-synology-powerpc-ds109/

      EDIT – Never mind, I see from other posts it’s a DS209 which is a Marvell CPU.

      Reply
  12. Chris Rogers's avatarChris Rogers

    Will you be updating your repo to host the latest version of crashplan 4.3.0 soon? I’m setting up a new installation and the desktop app won’t connect to the Synology Headless app without an update. Thanks in advance.

    Reply
  13. R Griffin's avatarR Griffin

    Thank you for all your work on this – I’m sure it is not easy keeping up with the recent changes that CrashPlan has been making. With that said, I have not been able to get this application/pkg to work in almost a month. You mention 4.3 in your updated notes but the SynRepo package is still 4.2x – I am not sure whether this is my issue or something else but essentially I am trying to do two things…

    1. Use a W7 PC as the Client. This may be the first issue b/c the only download available from CrashPlan (for Home Edition) on their website is for the 4.3 Client version. I’m not sure if the 4.3 Client -> 4.2 Server is causing a problem, but even after make the GUID changes you suggested above I still cannot access the backend.

    2. Change the JVM Heap Size. I have a fairly large dataset to backup (and enough memory to support an increase in the application’s usage). CP suggests on thier website 1024M per TB of data to backup; however, anytime I change the variable value by editing /volume1/@appstore/CrashPlan/syno_package.vars to anything higher than 1024M your Synology package will not start…it trys too, but then just churns and ultimately shows “Stopped” again.

    Extra Info:
    JavaSE Version: jdk-7u79-linux-i586.tar (Downloaded from Oracle site & in the Public Folder @ time of install of CP on Synology)

    Any assistance/insight you can provide would be greatly appreciated. I could not find your email address on your website but I’d be glad to provide additional details on setup if you can let me know where you’d like me to send it.

    Thanks,
    R

    Reply
    1. patters's avatarpatters Post author

      The reason I hadn’t updated the repo with a new version is that Code42 were publishing another update which was breaking fresh installs. It’s sorted now. Their installer has been updated, and I have hopefully improved this latest package to tolerate those updates moving forward.

      Reply
    2. John's avatarJohn

      Extra Info for you: Read the instructions / discussion before asking questions already answered few dozen times. Patters is not here to provide support pro bono. If you want to follow unofficial ways, be prepared to use your own head.

      Reply
  14. michal's avatarmichal

    Again it’s stopped working after the latest automatic update. Is there a way to disable these automatic updates and get it reliably working?

    Reply
  15. Brian Fox's avatarBrian Fox

    I’m in a holding pattern looking for the 4.3 package. I never upgrade the package since the last major changes and so I’m still running as the crash plan user. I was able to get the upgrade working ok but I’m not able to connect the client due to permissions on the /var folder preventing it from storing the token. In the meantime at least my backups run.

    Reply
    1. patters's avatarpatters Post author

      Brian, BEFORE you upgrade in Package Center, make sure you manually install this first:
      http://packages.pcloadletter.co.uk/downloads/old/crashplan4.2.0-merged-0031.spk

      The latest package hasn’t got the legacy pre-version 0028 version migration stuff in any more because I didn’t think there would be any people still running legacy package versions. Install that one, run it for a minute or so, then put the latest one from the repo over the top.

      Reply
  16. vibhavgupta's avatarvibhavgupta

    I just upgraded to DSM 5.2 on Synology 1512+ from DSM 4.3 and Crashplan has stopped working. I currently have on Synology: Java 7 running and Crashplan 4.2-0031. When I launch desktop client it prompts for email/password upon entering it gives me the message that upgrading Crahsplan. Then it crashes and when i go back into DSM, It shows Crashplan package stopped running. Then it does not start back again in DSM. I have tried uninstalling/reinstalling multiple times with no use. it was working good for the last couple of years… Please help. Thanks.

    My System: Mac with Mavericks, Synology 1512+, DSM 5.2

    Reply
  17. ST's avatarST

    Crashplan does not start again as of Jul-7. Says upgrading to new version from xxx.crashplan.com and nothing after that.
    Would you please check? DS413.

    Reply
  18. Graham's avatarGraham

    Same issue here – won’t start after the upgrade on 7th July. Looking at the scripts it looks like it makes use of nice, but this isn’t installed. Maybe Synology removed it?

    Reply
    1. Ryan's avatarRyan

      Give it some time, it’ll quit again. That same fix has “worked” for me twice now before CP has stopped again.

      About ready to throw in the towel and go with a more supported solution.

      Reply
    2. rstavely's avatarrstavely

      It’s “worked” for me twice now, before CP fails again.

      I’m about ready to throw in the towel and go with a more supported solution. I love CP, but if they’re not going to support my hardware, it’s time to vote with me wallet.

      Reply
    3. Chuck's avatarChuck

      This worked for me as well (following christnelson at ca)… I had to do this manual thing before… this time around, with the manual update, then waiting for it to die, and then doing the manual update to 4.3… then the whole GUID thing (which on a mac involves googling to set the finder to show hidden files (which is another terminal command). I love what Patters has done… and REALLY appreciate Chris Nelson’s workaround. I have a large amount of data stored… and if this died for ~30 days then I think it would vanish and take an eternity to backup again. I am starting to think that Crashplan hates us Syno folks.
      You know, I would gladly pay double if Crashplan would support the syno and stop breaking things. I actually have an older Syno a couple thousand miles away now that I backup files to… it works, but I also like this system since I took the trouble to do it. I have to say, if Code 42 breaks (and won’t support us officially) to a point where I lose my archive, then I am going to fully invest in the dual syno setup.

      Once again, though… thanks to Patters for the long term support… and to others for figuring out these wacky workarounds when Code 42 decides to upset our apple cart. :-)

      Reply
  19. patters's avatarpatters Post author

    New package version 4.3.0-0032 is released finally. The “chrisnelson” method is built in now, so hopefully this version should survive future Code42 published updates without having to fix their scripts. Thank you for your patience.

    Reply
  20. Jeff 3F's avatarJeff 3F

    Thank you!!!!
    (I am still having trouble getting the windows client to get into the Synology by using the ui.properties file after doing the ‘chrisnelson’ fix, so I’m going to uninstall/reinstall and then retry.

    A couple hours burned up, but I now know a LOT more (SSH commands, etc.).

    Reply
  21. Richard's avatarRichard

    Thanks Patters,

    New packaged upgraded nicely and it’s running. It also created the files I was missing under /var/lib/crashplan so I was able to dump the GUID. But when I try to launch the client after updating .ui.info file it still won’t connect. Can’t telnet on port 4243 either.

    Reply
    1. richZ's avatarrichZ

      I am having this same problem.. installed the newest version on a newest install. I dumped the GUID but I cant connect. This is a fresh isntall as I had to blow away the nas.. but I am familar with selling the GUID as I did it before blew things away.

      Reply
      1. richZ's avatarrichZ

        I did restarted the package a few times but the connection still doesnt accept. I have installed your package few times over the last year or two on a few synology nas units so I am fairly familiar with that requirement. I actually had crashplan 4.3 running on this nas as an upgrade before i blew it away.(I rebuilt the server for reasons unrelated to crashplan)

        I started with a brand new install of the 5.2 DSM. Actually I did it twice tonight the first time I did a restore of some user settings from the .dss file, the second time I just installed java and this package. I grabed the guid and adjusted the ip in conf/ui.properties. I then restarted the package and restarted my client just in case. I see these ports under netstat when I fire up the package and i can see that the engine is running but it fails to connect.

        tcp 0 0 0.0.0.0:4242 0.0.0.0:* LISTEN
        tcp 0 0 localhost:4243 0.0.0.0:* LISTEN
        tcp 0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN

        I can see the client is hitting right ip and port

        [07.12.15 19:42:56.420 INFO main com.backup42.desktop.CPDesktop ] Loaded permissions in 286ms
        [07.12.15 19:42:56.421 INFO main com.backup42.desktop.CPDesktop ] Adding shutdown hook.
        [07.12.15 19:42:56.421 INFO connect com.backup42.desktop.CPDesktop ] Connecting to service at 192.168.0.136:4243
        [07.12.15 19:42:58.226 INFO connect com.backup42.desktop.CPDesktop ] FAILED on attempt #1, retrying in 4000ms
        [07.12.15 19:43:03.226 INFO connect com.backup42.desktop.CPDesktop ] FAILED on attempt #2, retrying in 4000ms

        Is there any other logs i can look at? Is there another way I can try and connect to the server to eliminate something stupid on my side

      1. marc's avatarmarc

        I restarted the crashplan, rebooted the synology and pc a few times. The client still can not connect. Any log file to look at. The last few lines of service.log.o is:

        [07.13.15 00:50:00.017 INFO W32024695_SystemWatc com.code42.messaging.nio.MessageQueue ] MW:: STATS:UI: numWorkers=2, queue.size=0, MessageQueueStats[num=0, numSinceLast=0, handling=Counter[count = 0, rate = 0.00, rollingRate = 0.00], waiting=Counter[count = 0, rate = 0.00, rollingRate = 0.00], workload=1.000]
        [07.13.15 00:50:00.019 INFO W32024695_SystemWatc com.code42.messaging.nio.MessageQueue ] MW:: STATS:Peer: numWorkers=4, queue.size=0, MessageQueueStats[num=8, numSinceLast=0, handling=Counter[count = 3239, rate = 0.00, rollingRate = 0.00], waiting=Counter[count = 267876, rate = 0.00, rollingRate = 0.00], workload=1.000]
        Data>

      2. marc's avatarmarc

        I am trying to debug, I grep all my logs on windows for the guid from the ui_info file. I do not find the id I used and saved in the .ui_info file. I do find this in the log, a guid different than the one in the .ui_info. Are there 2 guid’s I am confusing or is crashplan finding a different config for some reason?

        [07.12.15 22:03:43.400 INFO main com.backup42.service.IdentityInfo ] GUID from file! guid=682589253873959180, file=C:/ProgramData/CrashPlan/.identity
        [07.12.15 22:03:43.400 INFO main com.backup42.service.IdentityInfo ] GUID loaded! guid=682589253873959180

  22. Shane's avatarShane

    Patters. THANK YOU THANK YOU THANK YOU. When I was looking for a solution for backing up data (I used backblaze with some Drobos that were connected via USB/Firewire and found them not reliable) I ran across CrashPlan and your web site. I then bought a Synology 1512+ and have had it working for over two years. You and others have been able to resolve every issue that has come up.

    My job allowed me to purchase a Synology 1815+ and CrashPlan (which I will get working tomorrow).

    May I suggest something. For the last two years that I have been following this group and updating every time you fix something (thank you again) the instructions may not be clear to everyone. I do not believe everyone here is as technical savvy as you (I am not). Would it be a good idea to have the update instructions a bit more simple? I am not sure what the solution is. Maybe there are those that need to read a bit more before asking questions (I do that – I jump before I read sometimes). Don’t know.

    What I don’t want to do is say anything bad about what you and others do to ensure that this package keeps going no matter what Code42 seems to do.

    You have gotten this going enough that I am going to send you something, not sure what just yet but I will (might take a week or two).

    Again, I cannot thank you enough for the time you take personally (way from your family and other obligations) to ensure this community is taken care of. It is people like you that make working with technology that much easier and fun – in my opinion.

    If anyone has used this forum or his package and have not yet donated to Patters I suggest and challenge you to do so. I feel like I did back in the ’80s and ’90s when I had my Amiga and purchased software from those that I tried and found that worked. None of this lets just steal and use it.

    I know I have gone on a bit much. Thanks.

    Reply
    1. Anil's avatarAnil

      @Shane great post! Count me in for full support for Patters. Let me know how I could donate.. I might have missed the “donate” section on this site. I have been using CrashPlan on Synology and had been loving until a week ago and now I am forced to buy a new Synology DS so as to have DSM5.X. I have been a bit upset but I believe in Attitude of Gratitude and accepting the situation with a positive “twist”…

      Best,
      Anil

      Reply
    2. patters's avatarpatters Post author

      Thanks for the feedback and appreciation. I have now finally updated the instructions on this page, and on the Java page since they were both very out of date. I had been focussing my available time on the actual packages, but clearly the documentation is important. In re-writing it I had looked for ways to simplify it, but unfortunately running CrashPlan on an unsupported headless system is a complicated process. All the info on this page is needed. It would be a lot of work to screenshot every single thing, tell users how to use SSH etc. Some knowledge has to be assumed. I have considered integrating some help documentation into the package using the native DSM Help application in DSM 5.0 and later, but that will be time consuming.

      Reply
      1. Flavio Endo's avatarFlavio Endo

        What would help people, it is a forum.
        Where things are discussed not on a single tread as here, instead each item/doubt would be on a specific topic / section. And people would be helping more each other.

        Yeah.. that is something else to take care.. but I guess It would save time to constantly repeat instructions.

        And this could be lead by someone else.. sorry I don’t have the skills and knowledge to build a Forum.

        Thanks again patters for all efforts.
        My donation was done around 2 to 3 years ago, and another one last year.
        Flavio Endo

  23. Tyuser's avatarTyuser

    The update works fine but the client still can not connect.
    I restarted the crashplan, rebooted the synology. In the log I see that crashplan try to connect to the correct ip and port but connection fail.

    Reply
      1. Gert's avatarGert

        Same problem here.
        Installed the latest crashplan package without any problems, but can’t connect anymore from my desktop computer. Tried everything and I know about the client guid etc… I hadn’t any problems with package version 0031.

        Via “telnet 192.168.0.6 4243” on my computer:
        could not open connection to the host.

        Via “netstat -na | grep LISTEN | grep 42” I see this:
        tcp 0 0 0.0.0.0:4242 0.0.0.0:* LISTEN
        tcp 0 0 127.0.0.1:4243 0.0.0.0:* LISTEN

        Somebody has a solution for this?
        I rebooted my NAS, removed and installed the crasplan package, nothing helps…

      2. patters's avatarpatters Post author

        Your NAS is listening but only for connections from localhost. If you stop and restart the package it should work (the script will change that 127.0.0.1 to 0.0.0.0).

      3. wilhelmsvenselius's avatarwilhelmsvenselius

        Same issue here. Was working just fine on previous package version, but now I can’t connect. I know about the GUID thing but it never even gets that far, connection refused on port 4243.

        engine_output.log:

        Connectivity testing localhost, port=4242, connectionTimeout(ms)=100, retryDuration(ms)=100
        Failed to connect after duration=116, retryDuration=100, address=localhost, connectTimeout=100, e=Connection refused
        Connectivity testing localhost, port=4243, connectionTimeout(ms)=100, retryDuration(ms)=100
        Failed to connect after duration=103, retryDuration=100, address=localhost, connectTimeout=100, e=Connection refused
        Loaded port=4243 and token from location=/var/lib/crashplan/.ui_info

        engine_error.log is empty.

        I have uninstalled/reinstalled CrashPlan on the NAS (DS415+) and tried connecting from a freshly installed client. No dice. Since I am getting connection refused, problem is probably on the server side rather than client.

        I am seeing a peculiar error in service.log.0:

        [07.13.15 14:34:31.034 WARN BWQ-Security::-0_698 de42.messaging.security.SecurityProvider] SP:: GeneralSecurityException: finalizeExchange, remote client likely has an invalid PbK. Closing session. Session[id=698010821804030173, closed=false, isAcceptor=true, lat=2015-07-13T14:34:30:986, lrt=2015-07-13T14:34:30:986, lwt=2015-07-13T14:34:30:982, #pending=0, enqueued=false, local=192.168.0.131:4242, remote=192.168.0.100:10604, usingProtoHeaders=true, usingEncryptedHeaders=false, LAN], javax.crypto.BadPaddingException: Decryption error

        192.168.0.100 is my machine, but this error is NOT when attempting to connect using the client, rather I have tracked it down as being triggered by the server process on my computer. Most likely it’s trying to talk to the CrashPlan server on the NAS as it is a possible backup destination.

        I get no errors in service.log.0 when attempting to connect from any client.

      4. Gert's avatarGert

        Hi Patters!
        I restarted the package several times, with enough time between starting and stopping, still the same: tcp 0 0 127.0.0.1:4243 0.0.0.0:* LISTEN

        Do I need to install 0031 package first and then update?
        That shouldn’t be needed, right?

        Gert

      5. patters's avatarpatters Post author

        This must be yet another change with version 4.3. The default value used to be “127.0.0.1” not “localhost”. I hadn’t encountered this problem because my own my.service.xml was migrated when I upgraded. It affects fresh installs of version 4.3 only. Looks like I need to put out a new package version.

      6. Gert's avatarGert

        @wilhelmsvenselius: many thanks for this solution, problem solved!
        @patters: also a big thanks to you for the package off course!

    1. Ronald's avatarRonald

      I had the same problem, checked the client GUID. (My synology was still ‘fresh’)

      Now it’s working, don’t know what did the trick but, my steps:

      – uninstall Crashplan (synology)
      – (i’m not sure this has anything to do with it, but) Activated Homefolders;
      (Log in to your Synology from a web browser. Go to the Control Panel, then User, then User Home and click “Enable User Home Service.” This will give the future “crashplan” user a “place to live.”)
      -Installed crashplan4.2.0-merged-0031.spk, like Patters mentioned above.
      “BEFORE you upgrade in Package Center, make sure you manually install this first:
      http://packages.pcloadletter.co.uk/downloads/old/crashplan4.2.0-merged-0031.spk

      Reply
      1. Ronald's avatarRonald

        after this, stopped crashplan and started. (it couldn’t start). Then Choose update crashplan from the package center.

  24. cemjack's avatarcemjack

    I have crash plan working on DS1513 and client on macbook. If I intend to run crashplan to backup both the Synology DS1513 and the macbook, how do I setup the client. Currently, I’ve made the changes to allow assess to DS1513. Do I need to edit the .ui_info file and conf/ui.properties in the CrashPlan folder (#serviceHost=127.0.0.1) overtime I want to switch back and forth or is there an easier way?

    Reply
    1. patters's avatarpatters Post author

      Unfortunately I think you would indeed need to keep editing the configs to switch between the two. This GUID change for the 4.3 client is adding considerable complication.

      Reply
  25. Dave's avatarDave

    I am having issues similar to a few of the guys above where client doesn’t connect with a new install. I did the restart and edited guid file. Yesterday I did a new install of the package on a newly setup ds214. I restarted package and did the fix to file with guid but my client doesn’t connect. Ports seem to be open. I can telnet to port 4242 and get a response. The ui log on client show correct IP address and port and that connection failed but doesn’t show much else. I see in server logs tat crash plan is working okay. But I don’t see any connections attempts in login server

    Questions
    1)anything other then net stat I should do to check the ports are open? I can telnet to 4242 but nothing repo index on 4243. Being able to telnet to 4242 is same as when I connect my desktop
    2)is there a Linux client I can run right on the nas?
    3)anyway to turn on more detailed logging at client

    Reply
  26. Christopher Exline's avatarChristopher Exline

    The ui_.properties no longer contains the serviceHost. This appears to be in the my.service.xml. I have updated both with my IP, but an unable to connect the client. I have stopped and stated the CrashPlan service several times. I have retrieved the headless key from the .ui_info file via SSH and put this in the file, but still no luck. Any help is appreciated.

    Reply
  27. admintoojee's avataradmintoojee

    Hi !
    I have trouble de connect to crashplan:
    – I have copy de guid on crashplan 4.3.0 on windows 7
    – crashplan package is running on NAS

    But i can’t connect… Before that I follow instructions of chris nelson with your 4.2.0 package, and it worked just in manual, when I launch crashplan on windows.
    I have restarted NAS, and your package several times.
    How can I do to dectect the issue? Can I uninstall all and start fresh? I have tried to uninstall yourt package and reinstall but no success so far.

    Reply
  28. rich's avatarrich

    This was the fix I needed… – I” resolved my issue by changing the service host in my.service.xml. It was reading “localhost”. Changing it to 0.0.0.0 let my client connect.” log in as root – find that file and make that change.

    Reply
    1. Mark Wilson's avatarMark Wilson

      Are you sure you are looking in the right place?

      On a Mac it is /System/Library/Application Support/CrashPlan if using SublimeText or some other text editor, you can press cmd+shift+. in the file selector to show hidden files and you can then see .ui_info

      Reply
  29. Richard's avatarRichard

    Thanks Patters!

    Updated package worked like a charm. Able to get the client to connect, just had to adopt the previous instance of the Synology. Just doing the file check now.

    Reply
    1. Marten's avatarMarten

      Same here, works again. I did have to persistently click ‘run’ quite a few times in the package manager.

      I didn’t even have to adopt the previous instance for some reason.

      Reply
  30. Patrick's avatarPatrick

    I have been using Patter’s solutions for a long time now and with some gymnastics always got it to work after upgrades.
    I have really tried hard several times with all the above steps (guid, etc.) including several clean installs, but I can’t get my client to talk to the Synology DS214play.
    Is there some other bug or setting I’m missing?

    Reply
  31. FZ00's avatarFZ00

    @Patrick

    I had the same problem as you .. the solution was

    In the directory c:\programdata\crashplan\conf is a file named like your windows user account (ui_xxxxxxx.properties)

    Open it and delete the service port entry .. save it … thats it

    Reply
      1. Patrick's avatarPatrick

        Like what? I don’t see anything.
        I’m on OS X, how does the solution of FZ100 work on a Mac?

      2. patters's avatarpatters Post author

        Ignore – I got confused between
        C:\programdata\CrashPlan
        and
        C:\programdata\CrashPlan\conf

        On your Mac, the equivalent would be /Library/Application Support/CrashPlan/conf/ui_USERNAME.properties (if it exists)
        Make sure that servicePort=4243

        If you’re installing on a client system where that port was already in use this value could be set to something different (e.g. you might have been connected to a remote NAS with SSH tunnelling enabled on 4243 at the time of installing, which has happened to me).

  32. planetwilson's avatarplanetwilson

    I installed all this from fresh last night. My Mac has the following files:-

    /Library/Application Support/CrashPlan/.ui_info (hidden file)
    /Library/Application Support/CrashPlan/ui_mark.properties
    /Applications/CrashPlan.app/Contents/Resources/Java/conf/ui.properties

    All of which look like they could take serviceHost and port entries…
    The first one needed updating with the Guid and the third one with the serviceHost in order to make my client connect.

    Reply
    1. Patrick's avatarPatrick

      Thank you, this worked perfectly! I did again a clean install of the client on the Mac and got those three files which I modified according to your notes above.
      => What is really strange: On the Synology I had to add the CrashPlan app again as a Firewall exception in Control Panel / Security / Firewall. It was there before, but must have been removed by the CrashPlan update on the Synology…

      Reply
      1. patters's avatarpatters Post author

        I’m not entirely certain what the precise Firewall behaviour is. The package registers CrashPlan in the Firewall’s list of built-in applications but doesn’t create any rules – that’s left for the user to do. It only removes this application definition if the Package Center action is “Uninstall”, so in theory at least a firewall rule containing this should survive a package upgrade.

      1. planetwilson's avatarplanetwilson

        I hope I wasn’t insinuating otherwise :) just some people seemed to be having trouble.

  33. Brennok's avatarBrennok

    I previously did the manual update via Chris Nelson’s page. I saw the new package was out so I decided to upgrade via the package installer even though it was working fine. I noticed now though the time in the log is an hour off and shows an hour earlier. The only time it shows the correct time is during the Stopping Crashplan message in the log. Prior to the package update, the time was correct.

    Reply
  34. jxgw's avatarjxgw

    I noticed that I now have a firewall rule for all interfaces to allow CrashPlan ports for all interfaces. I did not create that rule and for the way i have things configured this rule is unnecessary. Was this rule created during one of the updates? If I do remove this rule will it be recreated in the future? Is it more recommended that I simply uncheck this rule so that it is not enabled? Or is it OK for me to simply remove the rule?

    Reply
    1. patters's avatarpatters Post author

      The package registers CrashPlan in the Firewall’s list of built-in applications but doesn’t create any rules – that’s left for the user to do. Is it possible you might have created this manually some other time while experimenting?

      Reply
      1. jxgw's avatarjxgw

        I do like that it is registered as a built in application. But I really don’t think that i would have created the rule on the all all interfaces section. However, since no one else is chiming in that they saw similar issues I will not rule out that this is something I did. I will remove that rule and watch to see if it comes back in the future. Thanks for your help.

  35. Ethan's avatarEthan

    Do I actually need to run the client on my Mac or is just the NAS portion good enough? Was working prior to 4.3, and I have 4.3 now working fine on the NAS, but can’t get the Mac to connect. if it is working without the Mac and I can access on line would that be OK?

    Reply
    1. George's avatarGeorge

      Ethan,
      If you do not need to configure Crashplan on the NAS, then you don’t need to run the client. My upgrades have gone successfully (with all the “patches”) and the Crashplan server is running fine on NAS and I don’t need to change anything. I can check the crashplan log on NAS using the Synology admin interface and can also verify backups are working using the crashplan client locally (I use NAS as backup target for my local machines). I only use crashplan client to modify backup settings from client to NAS.

      Reply
    2. George's avatarGeorge

      Log into NAS via web browser and open Pakage Centre. Then click on Crashplan and you will see a link View Log. This shows you CP log for CP on NAS

      Reply

Leave a reply to Patrick Cancel reply