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. ewfzapp's avatarewfzapp

    Hi, first of all, excuse me for mi poor english (i’m french).
    I have a ds212+, and since 2 or 3 days, my crashplan is stopped and it is impossible to make it work again… I’ve desinstalled java 7 and installed java 8, i have desiinstalled crashplan and reinstalled it again, and nothing works…
    The log indicates that Crashplan made an upgrade (version 1388728800370) and then stopped. Maybe it’s this upgrade that doesn’t work with the nas?

    thx for your help!

    Reply
  2. FreaKai81's avatarFreaKai81

    Please help me anyone:

    I am using the Diskstation as Friend Backup Location. But after every Update of Crashplan on Diskstation all the Backups are gone or deleted and the Backup starts all over. So the oldest Backup is the one from today.

    How can i keep the old Backups? Which folder do i ahve to copy? or which COnfig do i need?

    its very very frustrating!

    Please Help me!

    Reply
  3. Fabien's avatarFabien

    Hello all,

    I’m having a problem with the latest version (system was previously working).

    I have a Disk Station 413 and DSM 5. running DSM 5.1-5022 and latest version of the Crashplan package and Java 1.7.

    Running the above steps, I’ve upgraded the server syno package and a windows client to CP 3.7.
    All goes to plan, and the client will talk to the server.

    But the backup itself never starts, remaining stuck with a status of “Waiting for backup” (even, when an immediate backup is requested).

    Looking at the server logs, I see the following warnings in /volume1/@appstore/CrashPlan/log/engine_error.log :

    Exception in thread “W15536577_ScanWrkr” java.lang.NoClassDefFoundError: Could n
    at com.code42.jna.inotify.JNAInotifyFileWatcherDriver.(JNAInotifyF
    at com.code42.backup.path.BackupSetsManager.initFileWatcherDriver(Backup
    at com.code42.backup.path.BackupSetsManager.startScheduledFileQueue(Back
    at com.code42.backup.path.BackupSetsManager.access$1600(BackupSetsManage
    at com.code42.backup.path.BackupSetsManager$ScanWorker.delay(BackupSetsM
    at com.code42.utils.AWorker.run(AWorker.java:158)
    at java.lang.Thread.run(Thread.java:745)

    It seems to be a JAVA issue, I have tried to reinstall several times and check that /var/@tmp was exisitng.

    This is a very frustrating problem.
    Could you please help ?

    Thank you.

    Fabien

    Reply
  4. Stefan's avatarStefan

    After I did the manual upgrade to 3.7.0 to Crashplan on my Synology (as described on http://chrisnelson.ca), Crashplan seems to run again on the Synology. But my Windows client is unable to connect to the Synology: “Waiting for connection” all the time. Any thoughts?

    Reply
      1. Stefan's avatarStefan

        Yes, the client version is 3.7.0 – 1388728800370. Still, I am unable to connect toe Crashplan on my Synology (waiting for connection)

      2. Consulting This's avatarConsulting This

        I had the same problem, but the desktop client is able to connect again after I stopped and started CrashPlan package. Thank you patters!

      3. patters's avatarpatters Post author

        Yep, you always have to stop it and restart it for the config to get amended to allow remote client connections. The config file doesn’t exist to edit before the first run.

      4. Stefan's avatarStefan

        I have restarted the Crashplan on my Synology several times, and am still unable to connect. Is anyone else having this problem? I have Crashplan 3.7.0-0030 running on my Synology, and the Crashplan client 3.7.0 running on both a Windows 8.1 and a Mac laptop. Both clients are unable to connect to the Synology (I want to backup my laptops on my Synology via Crashplan, not my Synology on CrashPlan Central). I am currently not sure how to find out what’s going wrong on my machine.

      5. nickzeff's avatarnickzeff

        Hi. I am having the same issue as Stefan. I am running the new client (3.7 32 bit), trying to get it to connect to my Synology service.

        The new 3.7 service on the NAS appears to be working fine. The website indicates that the my NAS has connected and succeeded.

        However, even after ensuring that my local conf\ui.properties file is updated as necessary, the crashplan tray status (hovering over the icon) shows “unable to connect…”. As an experiment I started my local Windows crashplan service, and the tray status changed to “waiting for login”. So it appears it is NOT paying any attention to the servicehost entry in ui.properties.

        Anybody else having this issue?

      6. nickzeff's avatarnickzeff

        Hi Stefan. I found out what was causing this issue on my system. Not sure if it will help you, but after many hours of frustration, this appears to be a privileges issue.

        If I try to open the Crashplan desktop app normally, it does not appear to start. However, if I open it as Administrator, this seems to give it the privileges needed to connect to my NAS correctly. I have no idea why. This is at least a workaround if I want to use the client.

        This is far from ideal and I have tried to change the security on the ui.properties file to allow all users full control, but still the Crashplan client would not open unless I opened it as Administrator. I’m not really a Windows expert, so not sure how to resolve this one properly.

      7. Stefan's avatarStefan

        Nick, thanks for your update. Running the client as administrator does not help on my side, the client is still waiting for connection. Actually, I have installed a Mac client on another Mac I have, and I have the same connection problem, so I am not sure whether this is a client-side problem…

  5. William Lagerberg's avatarWilliam Lagerberg

    Hi there nice post.

    Is there a way to install an old crashplanpro version 2010-03-08 i am still running a Crashplan server with the old license and like to keep it this way, but I really need to backup my Synology to this backup server.
    Have been looking into your files, but that doesn’t help :-( on my website there is a link to download 2010-03-08 http://www.elcanet.nl/en/downloads/category/12-software?download=27:crashplan-pro-2010-03-08-linux by the way there are a lot of old Crashplan installers there :-))

    Regards William

    Reply
  6. Mike's avatarMike

    I see that you now have support for the DS2015xs, but is that only for java? I’m not seeing it available in the package manager for install (and I’ve added the source and your other packages show up.) Thanks for all your work on this!

    Reply
      1. joshuaabrams2014's avatarjoshuaabrams2014

        Patters, this is just a THANK YOU for the update. 7.5 days without backup was getting a little nervous . You have done a great job with this. THANK YOU!

      2. Brian's avatarBrian

        patters: first off, thank you for all your work on this – with all the updates it seems like it’s a full time job…

        I have a DS713+ with latest DSM; last week the 3.7.0 update made it stop working so I applied the fix mentioned on this site which restored everything back to normal. However, now when I go to apply your package update it says “Failed to update CrashPlan”. Is there somewhere I can look for additional troubleshooting info?

        Thanks.

      3. goslow2gofast's avatargoslow2gofast

        Worked like a champ for me. I had not manually upgraded yet, was living without CrashPlan for a bit while this sorted out. Applied the update you just released and it worked fine on my system (DS413 @ DSM 5.1-5022).

        Thanks!

      4. mgittelman's avatarmgittelman

        Crashplan is now showing up in the packages for my 2015xs, and I’ve installed Java 1.7.0_75-0030 but now that crashplan has installed successfully, it won’t start. It just says failed to run the package service. What am I doing wrong? Thanks!

      5. Stuart's avatarStuart

        i apply chris nelson fix as posted earlier and now when i update the crashplan package (29) i get the following error prompt ‘failed to run the package service’.

        /var/log/messages shows these entries.

        Jan 21 20:38:04 Disk entry.cgi_SYNO.Core.Package.Control[1].start[13816]: pkgstartstop.cpp:182 Failed to start package CrashPlan, [2]
        Jan 21 20:38:11 Disk entry.cgi_SYNO.Core.Package.Control[1].start[14139]: pkgstartstop.cpp:182 Failed to start package CrashPlan, [2]
        Jan 21 20:39:46 Disk entry.cgi_SYNO.Core.Package.Control[1].start[14539]: pkgstartstop.cpp:182 Failed to start package CrashPlan, [2]
        Jan 21 20:43:49 Disk entry.cgi_SYNO.Core.Package.Control[1].start[15177]: pkgstartstop.cpp:182 Failed to start package CrashPlan, [2]

        what can i do to fix problem?

      6. Brian's avatarBrian

        Patters: Thank you – you were right, the logs were useful…they showed an error with the package signature. FYI for others: If you go to update and get a generic “Failed to update CrashPlan”, it may be because the Package Center trust level needs to be set to “Any Publisher”. Thanks again.

  7. Chermette's avatarChermette

    Hi,
    I’ve manually upgraded the headless client on my Synology, as explained in the site that’s been posted… But, for the past 2 days, nothing is being backed up any more. Here are the message that keeps repeated every 13mn exactly:
    hh:mm CrashPlan is started, version 3.7.0, GUID xxxx
    hh:mm Backup planned to be always executed
    hh:mm Analyse of files to be backed up
    hh:mm Start of backup: XX files (YYMB)
    hh:mm+13mn Stopping CrashPlan

    What can I do to make the service restart?

    Thank you very much in advance
    Best regards

    Reply
    1. Chris's avatarChris

      I am having a similar issue where I keep getting the “Stopping CrashPlan” message. I uninstalled the package for both CrashPlan and Java 7 and then reinstalled both packages and stopped and restarted CrashPlan from within my DS413J running DSM 5.1-5022. In the history I see that there are files to back up in the TO DO list, however, it shows that it is analyzing a random file and then the backup stops and I see “Stopping CrashPlan” in the history. I also see the status set to “next back up in 14 hours”

      Reply
    2. Chermette's avatarChermette

      Hi,
      I’ve now upgraded CrashPlan to the last update, along with Java SE8, to no extent. I’m still having this issue, and I can’t backup anything…
      Is there a log file I should go and look at?

      Thanks in advance

      Reply
  8. 1aadeals's avatar1aadeals

    doesn’t work for me. I had manually upgraded before. When I’ve applied the update, crashplan fails to start.

    Reply
  9. Dan1911's avatarDan1911

    Hi Patters

    First a big thanks for you wonderful job.
    I have a little problem with the Synology Package.
    My NAS is a DS713+ with DSM 5.1
    Because of the 3.7 upgrade I made the fix http://chrisnelson.ca/2015/01/10/fixing-crashplan-on-synology-after-the-3-7-0-update-synology-repairing-upgrade-in-varpackagescrashplantargetupgrade1388728800370/
    When I have tried to upgrade the CRASHPLAN Package to 3.7 version I had an error message.
    So I decided to uninstall it to reinstall it after. But it’s impossible to do. I always have this message (in French but I will translate it) “Echec de l’installation de CrashPlan” “The installation of CrashPlan failed”
    Can you help me please ?
    ++

    D.

    Reply
      1. Chermette's avatarChermette

        Bonjour
        Il faut cocher l’option “ni’mporte quel éditeur” du paragraphe “autoriser l’installation de paquets de”, dans les paramètres des paquets

        —–
        Hi

        you need to check “from all editors”, in “authorize the installation of packages from”, in the package parameters

  10. 10waystogetrich's avatar10waystogetrich

    Doesn’t work for me. the new update.

    I had manually patched the previous version to get it to work. I’ve tried to the update, it fails to start. I’ve uninstalled and installed new release fresh, it still fails to work.

    Now, I’m stuck with no crash plan at all :(

    Reply
      1. urban's avatarurban

        cat /var/log/messages is giving me this line:

        Jan 21 23:30:31 DS413j entry.cgi_SYNO.Core.Package.Control[1].start[9787]: pkgstartstop.cpp:182 Failed to start package CrashPlan, [2]

      2. mgittelman's avatarmgittelman

        cat /vars/logs/messages shows
        Jan 21 15:20:11 nas entry.cgi_SYNO.Core.Package.Control[1].start[6305]: pkgstartstop.cpp:182 Failed to start package CrashPlan, [2]

        /var/packages/CrashPlan/scripts/start-stop-status start Shows:

        grep: /var/packages/CrashPlan/target/bin/run.conf: No such file or directory
        Starting CrashPlan …
        sed: /var/packages/CrashPlan/target/bin/restartLinux.sh: No such file or directory
        find: /var/packages/CrashPlan/target/upgrade: No such file or directory
        sh: -lt: argument expected
        sed: /var/packages/CrashPlan/target/bin/run.conf: No such file or directory
        grep: /var/packages/CrashPlan/target/bin/run.conf: No such file or directory
        sed: /var/packages/CrashPlan/target/bin/run.conf: No such file or directory
        grep: /var/packages/CrashPlan/target/bin/run.conf: No such file or directory
        sed: /var/packages/CrashPlan/target/bin/run.conf: No such file or directory
        /var/packages/CrashPlan/scripts/start-stop-status: /var/packages/CrashPlan/scripts/start-stop-status.sh: line 5: can’t create : nonexistent directory
        /var/packages/CrashPlan/scripts/start-stop-status: source: line 5: can’t open ‘/var/packages/CrashPlan/target/bin/run.conf’

        In /var/packages/Crashplan/target/bin I only have:
        CrashPlan-install cpio jna-3.2.5.jar libjtux.so

      3. falexpop's avatarfalexpop

        I had this more than one /volume?/ issue and 0030 has fixed it and crashplan is working again. Thanks Alex

      4. gord's avatargord

        I got the same messages as urban. Looking in “/var/packages/CrashPlan/target/bin/” there is no run.conf and no restartLinux.sh file.

  11. liveforpixel's avatarliveforpixel

    Amazing work.
    I have only recently purchased a Synology NAS, and you have by far provided the most useful package.

    I had done the manual fix, but did the update you provided and was working within a minute. (DS414) Thanks heaps for your hard work.

    Remember all, if this really makes a difference for you, buy a cup of coffee (donate) for the developer.

    Reply
    1. P,K's avatarP,K

      Mine is NOT working either. Got error below.

      DiskStation> /var/packages/CrashPlan/scripts/start-stop-status start
      find: unrecognized: /volume2/@tmp

      grep: /var/packages/CrashPlan/target/bin/run.conf: No such file or directory
      /var/packages/CrashPlan/scripts/start-stop-status: source: line 22: can’t open ‘ /root/.profile’

      Reply
      1. P,K's avatarP,K

        Works!! THANK YOU SOOOOOOOO MUCH!!!

        Someone earlier suggested setting up a forum. I can set it up and host it for you. I just help in moderating it at the moment. Please let me know if I can help in any way. Let me know if you need my email address. You can contact me at the one I used to post this message. thanks again!!!

  12. mgorbach's avatarmgorbach

    In case this helps anybody:
    There is a find command in the installation script for the package that is bad: it is not properly quoted. Specifically, if you have more than 1 folder like /volume?/@tmp, it will fail. If there is only one folder matching that pattern (for any character replacing the question mark), it will be OK. To patch over this problem temporarily without changing the script, before installing / upgrading Crashplan, move, delete, or rename all but one of the your /volume?/@tmp folders.

    Reply
    1. patters's avatarpatters Post author

      Thanks for spotting this, I was starting to guess the link between failure and the presence of a volume2. None of my test Synos have it. I’ve uploaded new versions of CrashPlan and Java packages with this issue fixed.

      Reply
      1. mgorbach's avatarmgorbach

        Thanks, patters. I’m sure that dealing with support like this is a PITA, but for what it’s worth your work is very much appreciated here.

  13. ace's avatarace

    Did an uninstall and re-install and it didnt work either. My log is now blank and the bin directory in ./target/ is empty as well. On DSM 5.0.x

    Reply
  14. roma0803's avatarroma0803

    Sorry to tell that the .29 update doesn’t start on my Syno DS412+ either. Uninstalled fully, rebooted, installed .29, no show.

    Reply
      1. roma0803's avatarroma0803

        Yes! It works. Installed fine. Stops and starts normal and I can connect to it from my laptop. Thank you very much for your support and the quick solution. I really appreciate it.

  15. Suzan M's avatarSuzan M

    Also broken after upgrade to 0029 today. (Had problems with previous package and was able to get it running manually then.) Have uninstalled, reinstalled, etc. “Package failed to start” and nothing in the package center logs. Oddly, I also note that there is no longer a “crashplan” user on my box and reinstalling didn’t re-create it. I’m also a volume2 install, if that helps.

    Reply
      1. Suzan M's avatarSuzan M

        Everything appears to be running again. Thanks *so* much for quick turnaround, and also for the explanation about the switch from the crashplan user to root.

    1. patters's avatarpatters Post author

      Version 0030 corrects this issue for NAS units with multiple volumes. The package runs as root since the substantial re-write for version 0028. This aligns with how Synology seem to do things with their own packages, and saves you having to mess about re-doing permissions each time the package upgrades.

      Reply
  16. ahershler's avatarahershler

    @patters: first of all a huge thank you for all your work on this package!
    Here is a small suggestion: I have noticed that even though we really are like a small community of people helping each other with issues that pop up, many people post comments reporting the same issue as others, often even after an earlier follow-up comment presented a solution. I think this happens because this single thread of comments on your post now contains 3,184 replies and no one reads through all of them before commenting with their own issue…
    If we were to create a forum with separate threads for the various issues, it would be a lot easier for folks to find others reporting a similar issue, and finding helpful comments of others who provided tips on resolving that particular issue.
    I am sure that if we ask nicely, such a forum could be hosted as a sub-forum on one of the Synology forums (under third party or mods or something like that). I am also sure that if you ask this community of yours, we can find a volunteer or two to admin the sub-forum so you don’t have to deal with it if you don’t want to.
    Over here, you could then post a link to the sub-forum so that everyone knows where to look for the community of users of your solution.
    What do you think?

    Reply
    1. My2Furballz's avatarMy2Furballz

      Hi There…

      I’m happy to set up a forum on one of my domains. I have a spare vBulletin license that is not being used.

      But only if Patter’s would like that..!!!

      Reply
      1. patters's avatarpatters Post author

        Thanks, but I think putting it in the Third Party Apps subforum on Synology’s official forum would be the best place.

    2. patters's avatarpatters Post author

      True. Part of the problem is how out of date the content on this actual blog post is though, which I will soon update.

      I wouldn’t really want to host a forum myself but asking Synology for a subforum is a good idea. I’ll ask my contact.

      Reply
  17. Mala's avatarMala

    Does anyone else using Crashplan Green get poor upload backup speeds?

    According to my router. I have a 40/7 (40 down 7 up) fibre connection, a speed-test verifies that my connection is very close to this too.
    My average upload speed to CP central is 800 Kbps, a far cry from the upload speed I was hoping to get after upgrading my broadband.

    Has anyone figured out a way to improve upload speeds, Ideally I would like to double or triple my speed, but leaving redundancy to stream to Plex remote clients.

    Would love to hear other peoples experiences.

    Reply
      1. David Swallow's avatarDavid Swallow

        Hi, it seems as though my upload speed has drastically decreased since the upgrade from 3.6.4 to 3.7.0.x. I’m not sure if Crashplan changed their code to throttle more. Anyone else seen this type of upload speed slowdown?

      2. CJ's avatarCJ

        Patters, I’ve also noticed that after the update my upload speed has drastically decreased. I’ve don’t all the modifications as before to the my.service file. Before the update I was uploading at 18-20mbs and minutes later I’m only at 4.6mbs. Not sure where to go from here. Both files on the headless client and my desktop have beeb modified…

        Any help?

      3. David Swallow's avatarDavid Swallow

        I rebooted my router and my upload rates are back to normal, so most likely a coincidence with the crash plan upgrade.

  18. Alex800's avatarAlex800

    Hello, I’m trying to update CrashPlan to ver 3.7.0-0030 but getting error “Failed to update CrashPlan” I had similar issue with Java 6 and end up installing Java manager and Java 7. Not sure how I can upgrade Crash Plan at this point.

    TIA

    Reply
  19. Eponym's avatarEponym

    Patters. Many thanks for all your efforts in keeping this solution up an running. All is good with your latest Java and Crashplan updates. I hope you appreciate a small donation.

    Reply
  20. Davy Lowet's avatarDavy Lowet

    Hey Patters,
    The upgrade doesn’t work for me. It reports can’t upgrade crashplan.

    The current version doesn’t want to start anymore. Is it a good idea to uninstall the current version first and do a fresh install? I don’t like to sync >50GB again,…

    Thanks for all the effort!

    Reply
    1. patters's avatarpatters Post author

      You can uninstall without re-syncing everything. You will need to adopt a previous system. When you first connect the client you see the advertising sponsored client window. Once you sign in with your account that has an active CrashPlan subscription it will ask if you want to adopt a previous backup. Do that and it will re-scan all your content but only sync stuff that has changed.

      If you’re really cautious, you can make a backup of your current CrashPlan install before you uninstall, just in case:
      mkdir /volume1/public/CP-Backup
      cp -R /volume1/@appstore/CrashPlan /volume1/public/CP-Backup

      Then you can delete that once you’re satisfied it’s all working.

      Reply
  21. MacGregor's avatarMacGregor

    I have a DS1512+ with CrashPlanPro 3.6.4-0028 working great. I click the update for 3.7.0-0030 — the update downloads, I accept the license agreement, and ‘Apply’ at ‘Confirm Settings’– then I just see: Failed to update “Crashplan PRO”.

    Reply
      1. MacGregor's avatarMacGregor

        I see there was an earlier reply on 5 Jan with the fix: “go to the package manager settings and allow packages from anyone.”

        3.3.0-0030 is working for me now. Thank you, patters, for all your work on this. It is fantastic.

  22. WiFied's avatarWiFied

    0030 update working great! I updated DSM to latest, uninstalled and reinstalled your java 7, updated crashplan on both Synology and on my laptop. Everything is working great.

    But, when I try to make a donation, I get an error, and it will not take me to the donation page. Would love to contribute to your excellent work.

    Reply
    1. WiFied's avatarWiFied

      Here’s the error:

      The requested URL /gan_click?lid=41000000035688872&pubid=21000000000532076 was not found on this server. That’s all we know

      Reply
      1. WiFied's avatarWiFied

        I do have ads blocked on Chrome and Firefox, but I keep Internet Explorer installed for this reason. But this link won’t work on any of these browsers.

  23. xkelly's avatarxkelly

    Just updated. Working great. Uninstalled both Java 6 and old CP app. Updated DSM to the latest (may as well do it now), installed latest JAVA 6 for Intel (still can’t use J7 for CP on Intel, right?), then installed CP. Works like a charm. Oh, yeah, send donation. That worked well, too. Cheers, Patters.

    Reply
  24. Chris's avatarChris

    Hey Patters,

    Great work on all of this! Any idea why I continue to get the “Stopping CrashPlan” message. I uninstalled the package for both CrashPlan and Java 7 and then reinstalled both packages and stopped and restarted CrashPlan from within my DS413J running DSM 5.1-5022. In the history I see that there are files to back up in the TO DO list, however, when the backup finally attempts to start after going through the “Synchronizing block information” for about 4 hours, it shows that it is analyzing a random file and then the backup stops and I see “Stopping CrashPlan” in the history. I also see the status set to “next back up in 14 hours”. I should note that this is still my initial backup of 5.9TB. I have completed about 4TB and there is about 1.9TB left. What logs can I check specifically to get at the root of the issue?

    Thanks again

    Reply
  25. Chris's avatarChris

    I am seeing these entries in /var/log/messages right before I reinstalled CrashPlan and Java:

    Jan 22 09:56:10 synouser: quota_clean.c:39 failed to clean quota of user [crashplan] in [/dev/md2][0x1D00 quota_clean.c:37]
    Jan 22 09:56:10 synouser: quota_clean_all_volumes.c:77 Failed to clean quota on /dev/md2, errno=0x1D00
    Jan 22 09:56:10 synouser: user_delete.c:289 SYNOQuotaCleanAllVols failed [0x1D00 quota_clean.c:37]
    Jan 22 09:56:10 synouser: user_delete.c:556 SYNOUserDbGet(CRASHPLAN) failed [0x1D00 user_db_get.c:53]
    Jan 22 09:56:59 entry.cgi_SYNO.Core.Package.Installation[1].install[11574]: pkginstall.cpp:405 Failed to run preinst script for CrashPlan, [1]

    Reply
  26. Funky's avatarFunky

    Hi,
    First I want to say Thank you for your time and work for this project.

    I installed 3.7.0-0030 and Java 7 1.7.0_75-0031 on my DS413 and was now able to finish scan. But after analyzing a few files the Desktop client stops without any error message. Protocol shows that the service stopped.

    /var/log/messages shows

    Jan 22 19:51:37 DiskStation synouser: quota_clean.c:39 failed to clean quota of user [crashplan] in [/dev/vg1000/lv][0x1D00 quota_clean.c:37]
    Jan 22 19:51:37 DiskStation synouser: quota_clean_all_volumes.c:77 Failed to clean quota on /dev/vg1000/lv, errno=0x1D00
    Jan 22 19:51:37 DiskStation synouser: user_delete.c:289 SYNOQuotaCleanAllVols failed [0x1D00 quota_clean.c:37]
    Jan 22 19:51:37 DiskStation synouser: user_delete.c:556 SYNOUserDbGet(CRASHPLAN) failed [0x1D00 user_db_get.c:53]

    I increased heap size to 1280M but still the same issue :( Any hints?

    Reply
  27. corpoblogger's avatarcorpoblogger

    Hi,

    I’ve updated both Java and Crasplan but now I seem to be missing the “Crashplan” user in my synology users list and the client cannot connect to my DS214 destination, nor can it “see” any files that are otherwise accesible on it and need to be backed up. I guess something is quite screwed here? Can you please advise?

    Many thanks!

    Reply
  28. MAFletch's avatarMAFletch

    Thank you Patters for another version update. I noticed that my log now seems to be using GMT rather than local (EST) time as I thought it had been previously. Anyone else seeing this behavior?

    Reply
      1. corpoblogger's avatarcorpoblogger

        I’ve already sorted it out – the missing user (which apparently has been replaced with ‘root’) was not the issue. I had to set up inbound backup again on the DS214 server and then I was able to connect the client to it properly.

        I also had to reinstall Crashplan desktop client and set it to run with my own user privilges so it could access the files on the DS214.

        So thanks. But how was the CP package updated in the first place if I do not have auto updates enabled in my package center?

  29. richard's avatarrichard

    Thank you Patters for the update. Everything working perfectly on both my DS413 and DS212. Small donation of my appreciation has been sent.

    Reply
    1. Funky's avatarFunky

      Hi richard,
      do you simply update the CP headless service? My DS413 is restarting the service after analyzing the first folder. Which max heap size do you have?

      It would really help me to bring my backup back online.

      Thanks

      Reply
  30. Chris's avatarChris

    Anyone else experiencing what Funky and I are experiencing? Any ideas on what can be done to resolve the issue? I am dead in the water…Any help would be appreciated.

    Thank you in advance

    Reply
  31. Nigel's avatarNigel

    Hi Patters – thanks for posting these instructions (and hosting the packages!).

    I’m trying to install the Crashplan package on a new DS215j running DSM-5.1-5022. I’ve installed the Java 7 package and that looks good but the Crashplan package gives an error message stating: “This package is not supported on the platform of DiskStation”. I tried the CrashplanPro package and that seems to start the install OK. Is there a work around for this?

    Reply
      1. Nigel's avatarNigel

        Actually, having the same problem as NF. It’s now installed but not starting and there aren’t any log messages.

      2. Nigel's avatarNigel

        Out of curiosity I tried installing and running the Pro version but it has the same problem: it won’t start up and there aren’t any log files.

  32. NF's avatarNF

    I have been eagerly waiting to be able to install this on my DS215J, and I see now that it should be supported.
    The good news is that I’m now able to see the Crashplan package, but when I do try to install it, I get a message saying “This package is not supported on the platform of DiskStation”.
    I have installed the latest Jave 7 /1.7.0_75-0031.

    Anything I have missed that I need to do first?

    Reply
      1. NF's avatarNF

        Yes, it now allows me to install the package.

        However, I’m not able to start the service. It keeps saying “stopped”.
        When I select “Run”, I do get a message saying it should be running, but the status remains “Stopped”, and the log is empty.
        I have tried to uninstall Java 7, and go for Java 8 instead (and do a Crashplan re-install after that), but it’s the same result.

        Any ideas, or hints I should try to provide more info, is much appreciated.

  33. Chris's avatarChris

    To expand on what has been happening for me…the backup starts and stops about every 8 minutes and appears to back up one file and then stop….

    Reply
  34. Jens D's avatarJens D

    I am following these posts since my first installation of the 3.6.3-027 package with Patters’ Java 1.7.0_60-0026 on my DS213j in July 2014 – and my Crashplan is working perfectly since: When Code 42 released 3.6.4, I had to restart Crashplan twice and install the new client on my PC; after the release of 3.7.0 I had to start Crashplan only once and install the 3.7.0 client on my PC – and it keeps backing up without errors. I always updated to the latest DSM version – again with no issues.
    Regarding resource usage: When there are new files to backup, the memory usage goes up to 83% or even 96%, but then drops to something between 10% and 20% again. OK – I only have 110 k files with a total of 330 GB backed up, but it works perfectly even with this small box – and still with Patters’ 0027 package – reading all these posts regarding problems I didn’t dare touching my running system (I probably should update the package some time..?).
    Is it only me going through all updates with no issues or are there more to share my good experience?

    Reply
  35. Min's avatarMin

    Hi Patters, thank you for this update. Works perfectly on my DS112+. However there’s a small problem, since updating to 3.7.0, my Synology has been unable to hibernate. It could sleep like a baby before. Just wondering is this a common problem? Thank you

    Reply
  36. Roy's avatarRoy

    Im getting “failed to start the package service” when trying to install 3.7. It was working about 4 days ago, and then stopped and wouldnt start. Then I noticed it had an update in package center. Now I get the error above. I do see in install in the @appstore directory, but it wonts start.

    Manually running restartlinux.sh outputs this:
    Fri Jan 23 22:32:59 EST 2015 : /var/packages/CrashPlan/target/bin/restart.sh
    Fri Jan 23 22:32:59 EST 2015 : APP_BASENAME=CrashPlan
    Fri Jan 23 22:32:59 EST 2015 : DIR_BASENAME=crashplan
    Fri Jan 23 22:32:59 EST 2015 : Stopping using ./CrashPlanEngine…
    ./restartLinux.sh: line 17: ./CrashPlanEngine: not found
    Fri Jan 23 22:32:59 EST 2015 : Sleeping 10 seconds…
    Fri Jan 23 22:33:09 EST 2015 : Starting using ./CrashPlanEngine…
    ./restartLinux.sh: line 21: ./CrashPlanEngine: not found
    Fri Jan 23 22:33:09 EST 2015 : New Service Process below:
    Fri Jan 23 22:33:09 EST 2015 : Exiting restart script

    Reply
  37. iamroddo's avatariamroddo

    Is it possible to maintain the current state of Crashplan across DSM upgrades when disk format is required? I presume that if it is possible that something (/volume1/@appstore/CrashPlan perhaps?) would need to backed and restored.

    Reply
    1. patters's avatarpatters Post author

      I’m not aware of a DSM upgrade that has forced a wipe of a data volume. But yes you could keep a copy of that whole folder. Then install CrashPlan from fresh, stop the package and switch back your old folder.

      Reply
  38. sonomofo's avatarsonomofo

    Last week CrashPlan version 3.6.4 stopped working. The log shows it attempted to update CrashPlan downloading it from Code42, but then the logs shows “Unable to backup, destination unavailable” and some messages failing to repair the install. I tried unisntalling and re-installing the package; it downloads the package, version 3.7.0, I approve the EULA, confirm settings (version 3.7.0-0030) but then it just pops up a message “Failed to install CrashPlan”.

    I can’t find any problems in the DSM logs. I’m running DSM 5.1-5022 Update 1.

    Any ideas?

    Reply
  39. Chermette's avatarChermette

    Hi Patters

    I’ve been trying to solve this for the last 4-5 days, but I can’t seem to find a solution. Everything worked fine, until the moment where the upgrade script didn’t work (around a week ago). I tried, at that time, every solution I found on the internet, one of which was to manually restart CrashPlan from the command line.
    When the solution had been found (comment out the upgrade in a script), CrashPlan would stop&start every 13mns, without backuping anything. On Tuesday/Wednesday, there’s been the package upgrade issue… Which, once upgraded, didn’t solve my issue. I tried and allocated more RAM (by increasing the -Mx paramater), to no extent.
    After digging a lot into the log files, I see this Exception a lot:
    BWQ-Security::-0_673 de42.messaging.security.SecurityProvider] SP:: GeneralSecurityException: finalizeExchange, remote client likely has an invalid PbK. Closing session. Session[id=xxx, closed=false, isLocal=true, lat=2015-01-24T13:56:39:585, lrt=2015-01-24T13:56:39:585, lwt=2015-01-24T13:56:39:348, #pending=0, enqueued=false, local=xxx:4242, remote=xxx:60720, usingProtoHeaders=true, usingEncryptedHeaders=false, LAN], javax.crypto.BadPaddingException: Decryption error

    I found a post in this thread from 2012 that stated this issue, coming from a manual stop&start. I hence tried the solution that was described at that time…. to no extent. I’m still having the above Exception.
    After 13mns (or now 15mns after my increase of allocated RAM), I have an OutOfMemory Exception.

    I tried and uninstalled and reinstalled CrashPlan, deleted the .identity before reinstalling CrashPlan… Nothing works… It’s been a week that I’ve been trying……..

    Do you know what I can now try?

    Thank you very much in advance
    Best regards

    Reply

Leave a comment