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.

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:

- 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:

- Now browse the Community section in Package Center to install CrashPlan:

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:

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:
- 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:
- 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

I seem to have the backup up working again, but the crash plan tray icon is greyed out and states “waiting for login”. When I click on the icon it opens correctly and everything seems to be working correctly. Does anybody know if this is a problem? Thanks
The tray icon is probably reporting on the status of the CrashPlan engine instance that’s running on your computer. You can disable that completely if you want. See the main post Client Installation section for details how.
Thanks, I have just noticed (your very small) paypal button so I have made a small donation for all your hard work & support.
Thank you kindly – much appreciated!
Me too much appreciated
Is there a way to have 2 CrashPlan client instances on one machine? One for the NAS and one for the local machine?
I have reinstall the CrashPlanProe and I can’t the file “C:\ProgramData\CrashPlan\.ui_info” (Windows)
http://prntscr.com/7uqygc
copy it from the nas /var/lib/Crashplan/.ui_info to c:\Documents and Settings\All User\Application Data\Crashplan
Hi,
The .ui_info should copy to “C:\Documents and Settings\All User\Application Data\Crashplan” or ” “C:\ProgramData\CrashPlan”?
How? I can telnet into the NAS, I can get to that specific folder and see the .ui_info file, but I’m not sure how to copy it to either A) My local machine or B) copy it to another directory (Share drive) on NAS so I can copy it through Windows explorer that way.
Any tips? Thanks!
OK, here’s what I did to help others.
I used Putty to SSH into the NAS as Admin. I then found the path of the file, and then the path to my Share Drive, and then did this command: cp /var/lib/crashplan/.ui_info /volume1/Share/.ui_info
This copied it to my share drive path. I then went to FIle Explorer in the NAS (DSM Manager) and then found the file, and pressed “Download”. Browser downloaded it to my desktop on Windows, and then I moved it to the folders as the rest of this documentation is talking about.
Hope this helps others!
Hi,
recently got hands on a friends DS215+ and noticed due to the new CPU the architecture naming got extended to “alpine4k” for this model, so you’re packages won’t be listed in the package center.
Any plans to make ’em compatible to this new(upgraded) arch? Very happy to serve as a guinea pig ;-)
Same here. Would be very happy to be able to use crashplan on my new DS215+ :)
Same here – would also really like to use it on my shiny DS215+ –
First step – can you try to install the Java 8 package? I just updated it to support alpine4k. Once it’s installed can you look in the Java package log in Package Center and check that it reports the HotSpot version like this:
java version “1.8.0_51”
Java(TM) SE Embedded Runtime Environment (build 1.8.0_51-b07, headless)Java HotSpot(TM) Embedded Client VM (build 25.51-b07, mixed mode)
I still don’t see your java package on the available apps (only craftbukkit, minecraft, and openremote).
Sorry – although I added support to the package, I forgot to update the supported architectures on the repo. It’s fixed now. Let me know if it works and whether you can run:
java -versionCan you also run:
uname -aThanks.
output:
a-nas> java -version
java version “1.8.0_51”
Java(TM) SE Embedded Runtime Environment (build 1.8.0_51-b07)
Java HotSpot(TM) Embedded Client VM (build 25.51-b07, mixed mode)
a-nas> uname -a
Linux liloak-nas 3.2.40 #5592 SMP Wed Jul 29 14:39:21 CST 2015 armv7l GNU/Linux synology_alpine4k_ds215+
liloak-nas>
Great! Can you also run:
cat /proc/cpuinfoThen after that please can you try the following:
cd /volume1/@tmpmkdir ffmpeg
cd ffmpeg
wget http://packages.pcloadletter.co.uk/downloads/serviio1.5-native-armhfneon.tar.xz
tar xvJf serviio1.5-native-armhfneon.tar.xz
./ffmpeg
ldd ./ffmpeg
This will tell me whether code built with the alpine toolchain is also ok for alpine4k (since there is not yet a Synology distributed toolchain).
Results below.
—
a> cat /proc/cpuinfo
Processor : ARMv7 Processor rev 4 (v7l)
processor : 0
BogoMIPS : 2793.47
processor : 1
BogoMIPS : 2793.47
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc0f
CPU revision : 4
Hardware : AnnapurnaLabs Alpine (Device Tree)
Revision : 0000
Serial : 0000000000000000
a> cd /volume1/@tmp
a> mkdir ffmpeg
a> cd ffmpeg
a> wget http://packages.pcloadletter.co.uk/downloads/serviio1.5-native-armhfneon.tar.xz
–2015-08-11 20:17:21– http://packages.pcloadletter.co.uk/downloads/serviio1.5-native-armhfneon.tar.xz
Resolving packages.pcloadletter.co.uk… 82.147.22.211
Connecting to packages.pcloadletter.co.uk|82.147.22.211|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 6482288 (6.2M) [application/x-tar]
Saving to: ‘serviio1.5-native-armhfneon.tar.xz’
100%[===================================================================================================================================================>] 6,482,288 800KB/s in 10s
2015-08-11 20:17:31 (630 KB/s) – ‘serviio1.5-native-armhfneon.tar.xz’ saved [6482288/6482288]
a> tar xvJf serviio1.5-native-armhfneon.tar.xz
ffmpeg
libass.so.5
libavcodec.so.56
libavdevice.so.56
libavfilter.so.5
libavformat.so.56
libavutil.so.54
libfontconfig.so.1
libfribidi.so.0
libgnutls.so.28
libhogweed.so.2
libnettle.so.4
libpostproc.so.53
librtmp.so.1
libspeex.so.1
libswresample.so.1
libswscale.so.3
libx264.so.146
a> ./ffmpeg
ffmpeg version 2.7.1-compiled_by_patters_for_Serviio Copyright (c) 2000-2015 the FFmpeg developers
built with gcc 4.6.4 (crosstool-NG 1.18.0) 20130102 (prerelease)
configuration: –arch=arm –cpu=cortex-a9 –enable-thumb –enable-cross-compile –cross-prefix=/usr/local/arm-cortexa9-linux-gnueabi/bin/arm-cortexa9-linux-gnueabi- –target-os=linux –prefix=/usr/local/arm-cortexa9-linux-gnueabi –enable-shared –disable-static –enable-pic –disable-ffplay –disable-ffserver –disable-debug –enable-pthreads –enable-libmp3lame –enable-librtmp –enable-libass –enable-libspeex –enable-gpl –enable-libx264 –enable-gnutls –pkg-config=pkg-config –extra-version=compiled_by_patters_for_Serviio
libavutil 54. 27.100 / 54. 27.100
libavcodec 56. 41.100 / 56. 41.100
libavformat 56. 36.100 / 56. 36.100
libavdevice 56. 4.100 / 56. 4.100
libavfilter 5. 16.101 / 5. 16.101
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.100 / 1. 2.100
libpostproc 53. 3.100 / 53. 3.100
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]… {[outfile options] outfile}…
Use -h to get full help or, even better, run ‘man ffmpeg’
a> ldd ./ffmpeg
libavdevice.so.56 => /volume1/@tmp/ffmpeg/libavdevice.so.56 (0x2ab31000)
libavfilter.so.5 => /volume1/@tmp/ffmpeg/libavfilter.so.5 (0x2ab44000)
libavformat.so.56 => /volume1/@tmp/ffmpeg/libavformat.so.56 (0x2ac22000)
libavcodec.so.56 => /volume1/@tmp/ffmpeg/libavcodec.so.56 (0x2ad5c000)
libpostproc.so.53 => /volume1/@tmp/ffmpeg/libpostproc.so.53 (0x2bb72000)
libswresample.so.1 => /volume1/@tmp/ffmpeg/libswresample.so.1 (0x2ab02000)
libswscale.so.3 => /volume1/@tmp/ffmpeg/libswscale.so.3 (0x2bb87000)
libavutil.so.54 => /volume1/@tmp/ffmpeg/libavutil.so.54 (0x2bbe6000)
libm.so.6 => /lib/libm.so.6 (0x2bc5f000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x2bc42000)
libpthread.so.0 => /lib/libpthread.so.0 (0x2bccf000)
libc.so.6 => /lib/libc.so.6 (0x2bcee000)
libass.so.5 => /volume1/@tmp/ffmpeg/libass.so.5 (0x2be1e000)
librtmp.so.1 => /volume1/@tmp/ffmpeg/librtmp.so.1 (0x2be43000)
libz.so.1 => /lib/libz.so.1 (0x2be62000)
libgnutls.so.28 => /volume1/@tmp/ffmpeg/libgnutls.so.28 (0x2be79000)
libx264.so.146 => /volume1/@tmp/ffmpeg/libx264.so.146 (0x2bf2f000)
libspeex.so.1 => /volume1/@tmp/ffmpeg/libspeex.so.1 (0x2c079000)
libmp3lame.so.0 => /lib/libmp3lame.so.0 (0x2c09c000)
/lib/ld-linux-armhf.so.3 (0x2aada000)
libfribidi.so.0 => /volume1/@tmp/ffmpeg/libfribidi.so.0 (0x2c106000)
libfontconfig.so.1 => /volume1/@tmp/ffmpeg/libfontconfig.so.1 (0x2c124000)
libexpat.so.1 => /lib/libexpat.so.1 (0x2c158000)
libfreetype.so.6 => /lib/libfreetype.so.6 (0x2c177000)
libhogweed.so.2 => /volume1/@tmp/ffmpeg/libhogweed.so.2 (0x2c1ed000)
libnettle.so.4 => /volume1/@tmp/ffmpeg/libnettle.so.4 (0x2c219000)
libgmp.so.10 => /lib/libgmp.so.10 (0x2c24f000)
libdl.so.2 => /lib/libdl.so.2 (0x2bc54000)
libbz2.so.1.0 => /lib/libbz2.so.1.0 (0x2c298000)
libpng16.so.16 => /lib/libpng16.so.16 (0x2c2ac000)
Thanks for that. I’ll be able to add support for the DS215+ to the other packages now.
CrashPlan packages have been updated to support DS215+.
And it’s working !
Thanks !
GREAT WORK. It is running on the DS215+ :-)
I had posted an issue with CrashPlan on synology failing to start recently. I just applied the 4.3.0-0033 update that popped up on my friends Synology and the unit now connects to my file server and is backing up! Thanks to the devs for this awesome app (and automatic fix)!
At the moment I’m running DSM version DSM 5.2-5592 Update 1 on a DS212+ with the CrashPlan client 4.3.0-0033, Java 1.8.0_51-0033 and the 4.3.0 Crashplan client on Windows 8.1.
I have modified the .ui_info according to the http://chrisnelson.ca/2015/07/02/fixing-crashplan-4-3-0-on-synology/ article, but I still cannot get a connection.
Anyone suggestions what else to look at?
SAme is here…
I do not see my Synology files from the CrashPlan client anymore and therefore I can’t configure backup to the Cloud. It seems that CrashPlan guys changed something in the recent release in the way that some of the technical files are missing or misplaced. As a result no internet instructions “How to” are useful anymore…
I’m in the same boat here as well. Even booted up another Windows instance to make sure it wasn’t something wrong there. I can’t see my NAS unit anymore even though the ssh tunnel is active and the .ui_conf file is adjusted.
My crashplan instance is stuck at “Waiting for backup”. I tried contacting support but they didn’t have any suggestions since this isn’t an an offically supported configuration. Any tips to debug and resolve? I tried to SSH but I don’t know what where all the logs are and what’s important.
I can backup local computers in the same network and setting the ip adress of my synology.
How can i backup a remote computer, over the internet, to my synology with public ip adress?
Hello All…
I’m about to setup my new NAS to run Crashplan. Would someone please be so kind as to let me know whether it is best to run Java 7 or 8..?
My older NAS is running Java 7 with no issues.
Thank you all.
Hi Patters, i have recently apply the Mac os X El Capitan and in the same time, the DSM 5.2 Update 2 was applied too. the chrisnelson.ca method seems to be not working, but that’s not the truth, the chrisnelson.ca method corrects well and fix the DSM Update damage but in my case my client doesn’t work on my Mac os x client and works fine on my Synology server. This morning a new update for El Capitan has arrived and like a sharm my Crashplan client opens again !. So wait a lot and apply the fix from Mac os X El capitan or … don’t apply this bêta.
Thank’s a lot for your work Crashplan for Synology is a really good tool.
Dom
Hi Patters,
just a quick question. Been using your app for a few months and it’s working great. I have 11 different backup sets, each about 300-500 GB.
Is it a good idea to leave the default scheduling settings for each backup set or could this be optimized? Every backup set has the following options:
Backup will run: Always
Verify selection every: 1 days at 03:00
Is this a good idea? My NAS is online 24/7
And where are the settings for my backup sets stored? On my client machine or/and on my NAS? Would be a good idea to backup Crashplan as well in case of a disaster!?
On the DSM 5.2 the crashplan headless client is running. I followed the steps to install the client on windows including copying the guid from the nas to the.ui_info file. The client still hangs when we start it.
Me too. Anyone else know how to fix this?
Using 4.3.0 on a Synology DS411+II.
It appears that Code42 have made some more changes over the weekend. On the Windows PC that runs my admin client, I found that ui.properties had been replaced by a new ui_[username].properties, and both it and .ui_info had been reset to defaults. After copying .ui_info from the NAS, and adding serviceHost=ip.address.of.nas back into ui_[username].properties, the local client was able to resume connection to the headless client on the NAS.
Oh, and while I’m here, I noticed that the NAS client is timestamping everything one hour in the past – it appears that whatever DST bug was previously fixed, has regressed.
I can’t find the .ui_info file anywhere? I tried a re-install of the client on the Mac but still not there. Do I do a deeper uninstall? Other ideas?
@ethan
.ui_info is a hidden file.
view view it in finder like this: http://lifehacker.com/188892/show-hidden-files-in-finder
or navigate to folder via terminal, and edit with VI. “vi .ui_info”
http://www.washington.edu/computing/unix/vi.html
Same problem here on W8.1 pro and W 10 pro
I’m waiting tot a solution. This was the 3rd time in tal months
Made all the changes noted – no luck. Launch CP on mac and just hangs on the green launch screen
Under ‘Notes’ above, Patters says: “It kept restarting the backup engine every few minutes until I increased the heap to 1024MB.”
Does anyone know how to increase the heap?
I am using Crashplan on the Synology headlessly via my Mac.
installed the 033, it works once, and thats it.
Now the same problem agian.
Hi,
I successfully migrated a Crashplan setup from an old DS213+ to a new DS715 with all backup sets intact. Crashplan, Java package and the headless setup (on a Windows 10 PC) worked without any issues. It was just to follow all the instructions.
Thx Patters for your work making this easy. A small donation is coming your way too.
//Per
Good day,
I have instaled Crashplan on a Synology DS 1815+. Everything worked fine until the update. Now ich cannot connect the headless client from my computer. I’ve copied the ui-properties but this doesn’t work either.
What can I do to connect again?
Please help me.
Thx, DocP
OK, I’ve found the Problem. There is a new UI_Username. I’ve put in die Servicehost and now it works again… Thx!
+1
it solved my problem :)
I’m finding lately that my .ui_info file occasionally updates itself to some random GUID and I can no longer get the UI to open. Then I have to “fight” with CrashPlan to get it to accept the GUID that I put in. I have no idea why it keeps changing itself.
Could it be that the CrashPlan service is running on your PC, which isn’t needed if you only use the client to access your NAS instance. Perhaps the service occasionally installs an update which pushes the PC’s GUID back into that config file.
Well, I do use the client on the PC as well, so I’d prefer not to disable the service. As for the service, occasionally installing an update, I cannot say, but I do know that I changed it 3 times in a 5 minute span this morning trying to get it to connect to the Synology. Finally, I changed it and set the “read-only” file attribute in the hope that it wouldn’t get replaced. So far, it’s stayed correct for almost 3 hours now, but I don’t know if that change might cause problems later.
Does anybody know what the maximum usable USR_MAX_HEAP setting is? I’ve tried setting mine to 8192M (of 16GB of RAM on my 1815+), but CrashPlan won’t even start. 4096M seems to have the same problem.
Could never get the client to connect on Win8.1
Upgraded to Win10
Uninstalled crashplan
Reinstalled
Noticed the path had all changed, .exe is not in Programs anymore, but in
C:\Users\\AppData\Local\Programs\CrashPlan
Killed the tray icon
Changed the ID of the .ui_info file to the one of my NAS
Started crashplan, and IT WORKED! :D
Whay do you mean by ‘Changed the ID of the .ui_info file to the one of my NAS’
Very did you find the ID of the NAS
From the instructions at the top of this thread.
Starting with CrashPlan version 4.3.0 you will also need to run this command on your NAS from an SSH session:
echo `cat /var/lib/crashplan/.ui_info`
Hi, Any idea why some clients can connect to my NAS and others can’t? Since some are succesfully connected I think my network settings are correct. But why can’t all the external clients connect normally? Anyone else having the same problems?
Hi Patters,
I succesfully installed the 4.3.0 and I can connect to the nas but I cannot login in to the cloud.
When I open the client and I insert username and password I receive the message “Unable to connect, check your network”.
The firewall rules on NAS are ok, the firewall rules on router are ok…the nas can succesfully connect to internet (in fact I installed your new vesion).
Please help me because are 7 months that I cannot make a backup on cloud.
What can I check? What log can I read to undestand why it doesn’t connect?
Thank you
Hi Patters,
I have a Ds412+ and have been running Crashplan for a couple years. I have uploaded almost 6 TB with another TB to go. After uninstalling CrashPlan and Java, I rebooted and then reinstalled the apps following the instructions above. About every hour of the day, it says CrashPlan started, version 4.3.0, GUID 54____________, Then it says Starting backup to Crashplan Central 1,085 files (673.12GB) to back up, Then an hour later it says Stopping Crashplan. It does this every day. I updated syno_package.vars to have a max of 2056. That is the maximum of my NAS. Can I increase the memory to an amount larger than what I have installed? Should I resort to different Backup Sets?
Not sure about the RAM question, but I believe from people’s experience on here that different backup sets will help.
Hi Michael, I have the same problem, but haven’t even got as far as you, yet. How do I increase the heap to 2056 or greater. I am using a Mac to run ‘headlessly’ my NAS. Is that the same for you? Do I use Terminal? What do I type in? Any help appreciated.
Hi Sam, I am running CrashPlan headlesslly on my Synology drive. To change the heap size, open a Mac Terminal and type in SSH root@192.168.X.X where the ip address is the ip address of your NAS drive and the password for root is the same as the password for your admin account on the drive. That will put you at the terminal on the NAS. Type in VI /volume1/@appstore/CrashPlan/syno_package.vars and remove the # in front of #USR_MAX_HEAP=XXXX and making XXXX=1536
If you aren’t familiar with the VI editor, open a web browser and google VI COMMANDS to help. Once done, you restart the application in package manager on DSM.
Many thanks Michael, hugely appreciated
Hi,
Can anyone can help me to fix my crashplanproe? I have upgraded to 4.3 version and not able to access anymore using my windows 7 client.
I have try to copy .ui_info and still no luck.
I’m willing to pay for your service and time.
Email me @ dannygohks@gmail.com
If is not appropriate, please delete the comment.
Pingback: Cloud Cover | iand.net
Hi Patters
My crashplan stopped working a while back.
I have upgraded the Java package and clicked the crashplan install (there is no upgrade option).
the app goes through the process correctly downloads the latest package and then runs literally for 30 minutes or longer. Eventually it comes back with “failed to instal” message. On the action back it has the status “installing”. I have to reboot the DS414j to get rid of “installing”.
What am i doing wrong?
C:\ProgramData\CrashPlan\.ui_info (Windows)
Should have been C:\ProgramData\CrashPlan\conf\.ui_info (Windows)
Seems like the port changes to 14243 after restart and there after I am not able to connect.
Have tried editing the port in my.service.xml but it gets changed back after restart as well.
Backups seem to be running fine according to the log. But as of now the only way I can gain connection to the headless install is:
– Uninstall
– Install clean
– Copy the ui_info files
– Update the ui.properties to connect to the NAS
Make changes restores etc.
But as soon as the NAS has been rebooted or the service restarted ui_info and my.service.xml changes port to 14243 and connection is not possible.
Anyone else with similar problem?
I have been running Crashplan on a Synology Diskstation DS415+ for a few months.
After the latest upgrade it stopped working. I have uninstalled crashplan, uninstalled Java and reinstalled everything according to the instructions above.
The client can connect to the service, but nothing is being backed up. The history.log.0 contains pages and pages of restart information, see below.
What can I do to try to remedy the problem?
Log file clippings:
I 08/26/15 05:45PM Stopping CrashPlan
I 08/26/15 05:45PM [Default] Scanning for files stopped
I 08/26/15 05:46PM CrashPlan started, version 4.3.0, GUID 651660719697690647
I 08/26/15 05:46PM Backup scheduled to always run
I 08/26/15 05:46PM [Default] Scanning for files to back up
I 08/26/15 05:46PM [Default] Starting backup to CrashPlan Central: 1 file (1KB) to back up
I 08/26/15 05:47PM Stopping CrashPlan
I 08/26/15 05:47PM [Default] Scanning for files stopped
I 08/26/15 05:47PM CrashPlan started, version 4.3.0, GUID 651660719697690647
I 08/26/15 05:47PM Backup scheduled to always run
I 08/26/15 05:47PM [Default] Scanning for files to back up
I 08/26/15 05:47PM [Default] Starting backup to CrashPlan Central: 1 file (1KB) to back up
I 08/26/15 05:48PM Stopping CrashPlan
I 08/26/15 05:48PM [Default] Scanning for files stopped
I 08/26/15 05:49PM CrashPlan started, version 4.3.0, GUID 651660719697690647
I 08/26/15 05:49PM Backup scheduled to always run
I 08/26/15 05:49PM [Default] Scanning for files to back up
I 08/26/15 05:49PM [Default] Starting backup to CrashPlan Central: 1 file (1KB) to back up
I 08/26/15 05:50PM Stopping CrashPlan
It’s running out of memory. Increase the JAVA heap size as described earlier in the support thread.
Thanks a lot, Marc. I will try this immediately.
It works now. 1GB was not enough (it kept crashing) but 1.5GB works. My backup set i 2.6TB.
I took the plunge and upgraded the RAM in the DS415+ from 2 to 8GB and now I have allocated 3GB to Java. This should work for some time.
Thanks again.
Had the exact same problem as Ole Overgaard with a DS713+. I would have been absolutely stuck except for looking at the support you guys have here. I bought 4GB RAM (Kingston KVR13S9S8/4) and upgraded the NAS from 1GB to 4GB. I increased the heap size to 2048M and started Crashplan. I thought that would solve it but read further and had to uninstall Crashplan and Java. Upon re-installing Java SE 8 I needed a new Java Distro (which I uploaded to public folder). I then was able to install Java and then re-install Crashplan per above instructions (including getting the new ui.info.
I was then able to log into Crashplan from the PC client and it is now synchonizing. I’m not precisely sure how long my client had failed. I had a very large backup set and I’m hoping that Crashplan doesn’t have to start from scratch.
In any event, thank you for maintaining this site. I’ve sent you guys a donation in appreciation for your work.
I recently upgraded the RAM in my DS415+ and am trying to figure out the maximum java heap size. 2GB is too small for my backup sets, 4GB doesn’t work at all, 3GB seems to work well. Is there a way to determine the maximum heap size that can be allocated? Anyone know why 4GB doesn’t work?
Thanks in advance.
No idea, I tried 4096M too but it just doesn’t want to accept it (maybe something to do with 32bit max memory? I don’t know). But I’ve found that 2048M works well even for a 10TB+ backup (although I settled for 3072M because I can spare it).
Ditto. I used 2048M and it didn’t even use up the entire amount I allocated.
Great work :-) … I got a bit inspired, and am trying to compile some packages for some NAS boxes in friends locations, and speculate whether you can tell me if there is any working SPK repository server code somewhere? I have been looking at sspks at github, but it is not working with the most current DSM builds (even though I have tried to patch the JSON returned to the DSM box). Will you be able to give me some input ? Send me an email if you can spend a bit of time helping…
I used Wireshark to sniff the HTTP GET request that the syno makes and used curl to reproduce that on the command line. Then you can see precisely how the official repo responds. With each DSM it gets slightly more complicated. Not near a PC right now.
As far as I can see, the package list comes out of a POST request – which returns some JSON data. Even though I managed to reconstruct the JSON data structure, it apparently isn’t enough…
It now seems to work – almost… Except for the displayed icon for my package in package manager, under “Community” .. I have a thumbnails section in the json output, and also package_icon variable in the INFO file… Any inpu on why the right icon not is displayed? It seems like the NAS never requests the image from the web server…
I’ve just been upgraded to 4.3.2, which broke my client access. Upon investigating it seems that they’ve added the ip interface (0.0.0.0) to the info that needs to go into .ui_info.
More problematically, it looks like the GUID is now being changed periodically. On my initial testing, no GUID managed to survive more than one restart of the CrashPlan package before being changed :(
It looks like wordpress stripped out the part of my message where I used angle brackets. The content of .ui_info is now “port,guid,0.0.0.0”.
Changing the default IP 0.0.0.0 to the IP of my NAS, the client is able to connect to the server again.
I concur… changing the default IP 0.0.0.0 to the IP of my NAS works!
And, to respond to an earlier post from Patters, yes, the Crashplan Windows client is installed for use by everyone. Hope this helps.
Hi, I can’t see the crashplan packages after adding your repository. I do see minecraft and servio, so it looks like the repo is set correctly. I have a DS109, which uses the marvell 88F6281.
Any ideas?
Due to increasing complexity and edge case handling getting out of hand I baselined CrashPlan on DSM 5.0 as a requirement. Unfortunately your NAS is too old to run it. The cut-off is 2010 models or newer I’m afraid.
Hi. I followed the instructions above to install crashplan client 64 bit on Windows 8.1, but I couldn’t find .ui_info on the specified location. So I created the file in the specified location, but the client didn’t connect to synology NAS.
Did a clean re-install of the Mac client. NAS part running well, but I really would like to be able to connect. Made all of the changes for 4.3 noted above, but still can’t get it to get past the splash screen for Crashplan. Any ideas?
There’s been another update – to 4.3.3.. However, even after following the method at http://chrisnelson.ca/2015/07/02/fixing-crashplan-4-3-0-on-synology/ there appears to be an issue using the local client to connect to headless machines.
I’ve change the .ui_info files to match tokens and changed the ui.properties file in the client to match the server IP number… It still just gives me the info for my local machine.
Same problem here, whenever I change my connection string in .ui_info file. After restarting crashplan service, the file is overwritten with a new random one
Hello,
I have a brand new RS815+ running DSM 5.2-5592-Update4. It has Atom C2538 CPU. I see the list of Crashplan packages for not the server pro e package. Is it compatible it perhaps it’s just not in the compatibility list yet?
Thanks
For some unknown reason, CrashPlan app refuses to connect to the Synology, and Sinology stopped uploading files, about 9 hours ago… I had no issues in the past 30 days. No system changes, only automatic updates on Synology.
Any ideas?
I checked all config files and all looks the same as I set it up about a month ago…
Slight update. It looks like CrashPlan pushed an update ver. 1430802000433 this morning (EST) and the CrashPlan package on Synology was automatically turned off (at least for me). Changing “Action” to run did the trick. Synology is once again uploading but he app on my computer is not connecting. I’m not sure if I messed up some config files or there must be something else changed… At this point, I’m happy the Synology is uploading again and will wait for responses how to fix he CrashPlan app… I hope this helped somebody ;)
Finally, I got it resolved. It turns out that (most likely) the update changed the GUID. Basically get the new GUID (which is followed by ,0.0.0.0 – which is not necessary) same way as previously (via SSH).
If this doesn’t work, do the fresh install of the app…
Hi again, I guess I had a process hanged or something like that. After rebooting my local computer I’ve been able to connect
Hello,
New problem after crash plan updated self to 4.3.3. guid on both client and disk-station changed to a random number. I changed the client via the crash plan guid command but don’t know the script to enter and change via tunnel ssh.
Hi – same problem here – had to re-enter guid on client side manually after update to 4.3.3 a few days ago.
Me too. For the benefit of others reading this, copy the .ui_info from /var/lib/crashplan/ on the NAS to C:\Users\\AppData\Local\CrashPlan\.ui_info which contain the GUID. Also update serviceHost and serverPort in ui.properties of course.
Looks like 4.3.3 came out recently. Just telling the package manager to run it a few times seems to have gotten the upgrade working, for now. It’d be nice if that could be more automatic though.
After the update to 1430802000433 i had to run the fix described at:
http://chrisnelson.ca/2015/07/02/fixing-crashplan-4-3-0-on-synology/
Including the update to .ui_info
everything fine now.
DS213+, DSM 5.2-5592 Update 4
Hal
Been having massive problems lately trying to get crashplan installed after I had problems with a previous version – was constantly getting “Failed to Run Package Service” messages after running.
I switched back from Java 8 to Java 7 and was getting very weird behaviour that the installer seemed to be failing to actually set up all the due files for crashplan (e.g. run.conf was simply missing as were a bunch of other files in the CrashPlan folder)
I recalled that I do have optware/ipkg installed and noted that the installer.sh script does source /etc/profile – in this file I have modified the PATH to also include /opt/bin and /opt/sbin
Removing these temporarily now seems to have gotten the app to install again and tentatively running…
Maybe solely coincidental or is there some binary that is being overridden by an optware binary and causing problems in the installer?
In case it helps anyone with the latest update from Crashplan, I found it necessary to uninstall and reinstall the Synology package. After the package has been reinstalled, stop it then start it again and then I was able to connect with the Crashplan client app. I’ve successfully tested this across a number of Diskstations that I manage (DS213+, DS713+, DS1513+ running Java 7).
Jay, thanks this worked perfected. Uninstalled, and reinstalled the crashplan package and it worked right away.
I see some comments above that the new upgrade change the GUID. But that in itself shouldn’t stop the uploading of new files? I am rebuilding my client box so I just logged in directly to crashplan and it appears uploads stopped 4 days ago.
I see Jay recommend a uninstall and reinstall of the package. If i uninstall do I need to connect with the client and log back in to crashplan site and have this nas ‘take over’ the existing backup
No, but as patters documentation tells you, when CrashPlan publishes an update, and the NAS tries to apply it, the usual result is that the package stops (i.e. no backups) until you restart it again so that his script can clean up the update.
Hi guys,
I don’t get the client to work. The backup engine (4.3.0-0033) at my synology is working fine.
I tried all of the mentioned above and I got it after the last updates everytime working again, but now it just won’t work.
I modified the ui_properties here E:\Program Files\CrashPlan\conf
I created the .ui_info file and placed it in E:\Program Files\CrashPlan and E:\Program Files\CrashPlan\conf and filled in the value from /var/lib/crashplan/.ui_info
I tried it without the IP-Adress at the end, with the ,0.0.0.0 at the end and with the IP Adress from my SYN – all three options doesn’t work.
Any other ideas?
When i checked C:\Users\admin\AppData\Local\CrashPlan there was execpt of the log directory nothing in there so I also copied everything into it, but this doesn’t changed anything as well.
thanks for your reply
Michael
Hi again,
I just solved the problem.
I had to change the file in C:\ProgramData\CrashPlan, even when CrashPlan is installed on another drive (E:). I found this information in the logfile, because CrashPlan tried to load a file in this directory, which the application couldn’t find.
So everything is fine again :)
thanks
Michael