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

Question to all of strugglers here:
Have you considered buying some ready-to-go Windows/Linux server (e.g. Beebox available from $150, taking 7W/hour), map your synology folders as a network drives, and use regular CP windows client? Sure, its another box in the network, but considering its dead silent, pretty small, costs $1 dollar to run / month, its not much more nuisance than having a notebook recharger laying around.
I may resort to that — I have some little arm dev kits(raspberry pi,etc) lying around that I could re-task for this.
I have done a similar thing here. I have two Synology boxes – RS815 (ARM processor), and DS413 (PPC processor – used as backup target for the RS815 + numerous windows machines), so it looked like I would not have much success upgrading to DSM 6.0.
Rather than using a dedicated box to run a Linux server, I created an Ubuntu virtual machine on my Hyper-V host server, installed the “standard” Linux Crashplan client and then figured out how to permanently mount my Synology shares on this machine (I’m a complete Linux Noob!).
After upgrading my Synology boxes to DSM 6.0, and a couple of hours playing around in Ubuntu, I have everything backing up perfectly using this solution.
It’s a pity that Code42 seem unable or unwilling to support Synology boxes, and kudos to Patters for his time and effort in providing us with a fantastic solution for so long, but after jumping through hoops with every successive upgrade for so long now, I really needed a “set and forget” backup again.
Sounds good. I imagine it would be possible to use rented virtual server from Amazon or Microsoft the same way.
I am definitely considering it – have my main PC client set up now so it can back up network attached drives. In fact I added one the other day just to test it out. Right now – I am getting Error: Could not find or load main class com.backup42.service.CPService error – the log shows no error on the update – which is what broke it:
Last msg in the log displayed in the DSM package panel shows the message “Synology extracting upgrade…” – and when I look there is no jar file in the upgrade directory. Not sure what else to do except delete and reinstall the package…
Can anyone with an Atom Diskstation confirm whether or not Crashplan works on DSM 6? I’m curious as to whether the only people with problems are those with Arm processor based diskstations or if it is something inherent in DSM 6.
I am running Crashplan 4.6.0 on DSM 6 with an Intel Atom processor without problems.
DS1815+ with DSM 6.0-7321 and Crashplan 4.6.0 is running just fine.
Thanks for the confirmation Troy and ajwillmer. So the mystery now is what has changed in DSM 6 on ARM to make CP stop working where it was working fine before.. I wonder if Synology have any information on that front.
Have you loaded the GUI and ensured you’re really backing up data?
I’m having trouble with DSM 6.0-7321 on a Diskstation with an INTEL Atom D2700. Before updating, I confirmed that CrashPlan was working. Now it won’t run when I try to start the service.
great instructions but I just can’t find the /Library/Application Support/CrashPlan/.ui_info there is no such file?
To add to the CP comments, even on their business platform, they have stopped sending ~recovery drives~. They used to for a fee, like most online backup services. Afterall, lets’ say you needed to restore a 800GB-1TB set of data. Sad to say, while they cap upload, they even cap download rates with a max of 5 megs. Try doing that when you need a ~real restore~
I decided to move from CP to another backup service because the continuous issues… I found iDrive as a possible alternative if you do not want backup more than 1TB. They have Synology package, but…
https://www.idrive.com/synology-backup
Unfortunately they have issues with new update also (http://forum.idrive.com/topic.php?id=458&page=3&replies=25) so may this also not the best choice….
Anyway the older version (2.03.17) working smoothly on the latest DSM 5.2 version.
have a look here http://www.m2networks.ca/crashplan-crashing-on-synology-dsm-6/
I am currently stuck with java.lang.NoClassDefFoundError: Could not initialize class com.code42.jna.inotify.InotifyManager, reported more in this thread.
I tried a fairly radical fix and copy the lib-jna versions from my Raspberry pi ( version 3.2.7 ) over to my NAS. Still the same error. It seems it has nothing to do with libjna itself but the class that uses lib-jna?
Anyone else has any suggestions?
I am using dsm 6 on ds213 and have crashplan working.
My fix was install java 8(7 should work)
thanks to fplanjer: I change the java package to by going into ‘/var/packages/CrashPlan/target/install.vars’ and changing line:
JAVACOMMON=/volume1/@appstore/CrashPlan/jre/bin/java
into
JAVACOMMON=/volume1/@appstore/java8/ejdk1.8.0_77/linux_arm_sflt/jre/bin/java
and since i unisntall crashplan a few time I followed patters instruction and all worked.
Hi Mark, can you confirm that CrashPlan is able to scan your files?
Last night when I went to sleep it was up to 21%. Today, the crashplan website status is up to 91%. When i get home I will verify it finished or not.
did yours not start at all or failed in the middle of the scan?
I have Crashplan started using these instructions … waiting to see if it will scan files and run backup.
One immediate – I don’t seem to be able to connect my crashplan desktop client on my PC to the service running on my NAS.
ui.properties has been updated to point at server IP
I’ve installed the 4.6 client on my PC… but it just times out trying to connect?
Any suggestions?
Last message in history.log is
I 03/31/16 04:04PM CrashPlan started, version 4.6.0, GUID 680804743381516290
I solved this following the additional instructions for adding port details to various properties files.
Or maybe I didn’t – with the client connected … it looks like my existing backup has disappeared from the client .. no details of any files I can restore appear – although they do show if I use the web client.
If I say ‘backup now’ – I’m not sure anything is actually happening… log files shows ..
I 03/31/16 04:48PM [Default] Backup to CrashPlan Central will take priority until complete (up to 24 hours)
But no file scanning is happening.
Here’s engine_error.log … looks like something else is having the same Java version problem…
Any suggestions please?
Exception in thread “W31998036_ScanWrkr” java.lang.NoClassDefFoundError: Could not initialize class com.code42.jna.inotify.InotifyManager
Perhaps setting the max notify? I noticed on DSM 6 it was again set to Linux default of 8192.
You can do this by adding “fs.inotify.max_user_watches=1048576” to /etc/sysctl.conf and rebooting.
That was worth a try but no luck – how do I check the setting? I did make the change to the file and rebooted but same problem.
sysctl -a | grep fs.*notify
With your change, i always get :
Exception in thread “W11872285_ScanWrkr” java.lang.NoClassDefFoundError: Could not initialize class com.code42.jna.inotify.InotifyManager
at com.code42.jna.inotify.JNAInotifyFileWatcherDriver.(JNAInotifyFileWatcherDriver.java:22)
at com.code42.backup.path.BackupSetsManager.initFileWatcherDriver(BackupSetsManager.java:417)
at com.code42.backup.path.BackupSetsManager.startScheduledFileQueue(BackupSetsManager.java:355)
at com.code42.backup.path.BackupSetsManager.access$1600(BackupSetsManager.java:72)
at com.code42.backup.path.BackupSetsManager$ScanWorker.delay(BackupSetsManager.java:1148)
at com.code42.utils.AWorker.run(AWorker.java:157)
at java.lang.Thread.run(Thread.java:745)
I will try java 8
Last night when I went to sleep it was up to 21%. Today, the crashplan website status is up to 91%. When i get home I will verify it finished or not.
did yours not start at all or failed in the middle of the scan?
Crash plan was running (pointing the jre to the synology one) but it was not scanning files (the error that everybody has been having lately). I tried to use your solution but then realize that you ds213 might not run the same processor as my ds413 (so I probably need another jre). I have a freescale QorIQ P1022 CPU, can does it say in the info center for yours?
So tried the ppc version 8u6 for the ds413, CrashPlan starts but same behavior. Java does not seem to be supported on that platform after 8u6, so unfortunately no chance to install 8u77
I did pretty much the same. Crashplan runs but didn’t scan my files…
I find this : https://randomwindowstips.wordpress.com/2013/02/25/crashplan-pro-for-linux-stuck-at-waiting-for-backup-or-connecting-to-backup-destination/
The java error is here…
I tried several times with several path… Nothing to do.
Same error, different problem
That’s an interesting post because it seems to be an issue with file system permissions on the tmp directory and a big change in DSM6 seems to have been in the user permissions model…
I workarounded the problem using RaspberryPI 2.
I created a folder named “volume1” and mounted my shared backupped folders in volume1/subfolder1, volume2/subfolder2, ecc.
I adopted the backup that was done by the Synology so I did not have to reupload my 100 Gbytes.
So far, so good.
Now I am waiting for an update coming from Patters.
If someone wants to do the same, I can explain how to do it.
Bye
.luca
Please share – seems this is the only way to get this to work. It’s a little odd too as Raspberry Pi has ARM CPU so we can count that out. Must be a system level change in DSM 6
First of all, install Crashplan according to: https://melgrubb.wordpress.com/2014/08/01/raspberry-pi-home-server-part-10-crashplan/
After installation, I configured my .ui_info file on Windows PC to connect to Raspberry Pi crashplan installation.
I had 3 folders backupped on the Nas:
1 – MyDocs
2 – MyApps
3 – MyJob
On crashplan site, I can see my backupped folders:
1 – volume1\MyDocs
2 – volume1\MyApps
3 – volume1\MyJob
I shared the 3 folders using NFS: https://www.synology.com/en-global/knowledgebase/DSM/tutorial/File_Sharing/How_to_access_files_on_Synology_NAS_within_the_local_network_NFS
I created 3 folders on my Raspberry Pi:
1 – volume1\MyDocs
2 – volume1\MyApps
3 – volume1\MyJob
Then I created 2 scripts on my Raspberry:
startmount.sh
#!/bin/bash
#Start rpcbind and mount drives
sudo service rpcbind start
sudo mount -t nfs 192.168.20.60:/volume1/MyDocs /volume1/MyDocs
sudo mount -t nfs 192.168.20.60:/volume1/MyApps /volume1/MyApps
sudo mount -t nfs 192.168.20.60:/volume1/MyJobs /volume1/MyJovs
stopmount.sh
#!/bin/bash
#Unmount drives
sudo umount -f /volume1/MyDocs
sudo umount -f /volume1/MyApps
sudo umount -f /volume1/MyJobs
I launched startmount.sh and I mounted the folders in the same path of my NAS installation.
Starting Crashplan from my Windows PC, I chose “adopt” and selected my NAS backup.
Everything has been synced in about 10 minutes.
Now that it is all ready, using crontab, I launch startmount.sh at 1.30 am and I launch stopmount.sh at 3.30 am.
That’s it.
HTH
.luca
Please post detailed instructions.
please explain…. Are you talking about doing a windows crashplan install on the rasberry pi 2?
I explained everything in the post above… awaiting moderation (I think because there are some links).
If you are in hurry:
h**p s : – – www . lucamerega . it – cp . txt
Remove spaces, substitute “*” with “t” and substitute “-” with “/”.
Hi I have just upgraded my Synology to DSM 6.0-7321 crashplan stopped working so I reinstalled it but now it will not start I get the following error in the engine log any ideas ?
Exception in thread “Thread-1” com.code42.exception.DebugRuntimeException: Unable to persist ServiceModel, Invalid signature file digest for Manifest main attributes, conf/service.model
at com.backup42.service.model.ServiceModel.save(ServiceModel.java:339)
at com.backup42.service.CPService.cleanup(CPService.java:2025)
at com.backup42.service.CPService$1.run(CPService.java:424)
Caused by: java.lang.SecurityException: Invalid signature file digest for Manifest main attributes
at sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:284)
at sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:238)
at java.util.jar.JarVerifier.processEntry(JarVerifier.java:316)
at java.util.jar.JarVerifier.update(JarVerifier.java:228)
at java.util.jar.JarFile.initializeVerifier(JarFile.java:383)
at java.util.jar.JarFile.getInputStream(JarFile.java:450)
at sun.misc.URLClassPath$JarLoader$2.getInputStream(URLClassPath.java:940)
at sun.misc.Resource.cachedInputStream(Resource.java:77)
at sun.misc.Resource.getByteBuffer(Resource.java:160)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:454)
at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:411)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at com.code42.crypto.Blowfish128CryptoUtility$BlowfishCache.getInstance(Blowfish128CryptoUtility.java:146)
at com.code42.crypto.Blowfish128CryptoUtility.encrypt(Blowfish128CryptoUtility.java:88)
at com.code42.crypto.Blowfish128CryptoUtility.encryptObject(Blowfish128CryptoUtility.java:53)
at com.backup42.service.model.ServiceModel.save(ServiceModel.java:326)
… 2 more
I get an “Invalid location” message when I try to add “http://packages.pcloadletter.co.uk” as a package location.
i was able to also get my crashplan running on my DSM6 DS414 (ARM). However, like others my desktop crashplan client shows a message “waiting for backup” and “initial backup not complete”. And the nas log shows “Exception in thread “W13139250_ScanWrkr” java”
To at least get crashplan running on my nas i did the following steps
1. Removed synology java 7 and java 8 installations
2. Installed patters java 7
i was able to also get my crashplan running on my DSM6 DS414 (ARM). However, like others my desktop crashplan client shows a message “waiting for backup” and “initial backup not complete”. And the nas log shows “Exception in thread “W13139250_ScanWrkr” java”
To at least get crashplan running on my nas i did the following steps
1. Removed synology java 7 and java 8 installations
2. Installed patters java 7
3. went into ‘/var/packages/CrashPlan/target/install.vars’ and changed line:
JAVACOMMON=/volume1/@appstore/CrashPlan/jre/bin/java
into
JAVACOMMON=/volume1/@appstore/java7/jre/bin/java
Should we be patient or try to find a another solution?
What do you think?
Im not able to let it work in my DS212J Java 8, Crashplan 4.60, DSM 6
Hi!!
I have put the steps together to get it work:
1. Install Crashplan (It will stop working after the update).
2. Install java8 and download the latest version.
3. Open ssh with putty or other ssh client and connect to your synology.
4. Extract the update manually:
sudo 7z e /var/packages/CrashPlan/target/upgrade/1435813200460_382.jar “*.jar” -o/var/packages/CrashPlan/target/lib/
sudo 7z e /var/packages/CrashPlan/target/upgrade/1435813200460_382.jar “lang/*” -o/var/packages/CrashPlan/target/
5. Get your temporary upgrade folder:
cd /var/packages/CrashPlan/target/upgrade
dir
Look for the folder 1435813200460_382.yourfoldername
6. Rename the upgrade.sh file:
sudo mv /var/packages/CrashPlan/target/upgrade/1435813200460_382.yourfolder/upgrade.sh /var/packages/CrashPlan/target/upgrade/1435813200460_382.yourfolder/upgrade.sh.old
7. Rename or remove the java JRE folder included with Crashplan:
sudo mv /var/packages/CrashPlan/target/jre /var/packages/CrashPlan/target/jre.old
8. Find your java folder, it looks like /volume1/@appstore/Java8/j2sdk-image/jre
cd /volume1/@appstore/Java8
dir
cd j2sdk-image
dir
See if you find a JRE folder.
9. Make a mountpoint in your Crashplan Folder to the java jre folder:
cd /volume1/@appstore/CrashPlan
ln -s /volume1/@appstore/Java8/j2sdk-image/jre ./jre
10. Install CrashPlan client on your pc and disable the crashplan service
11. Get your CrashPlan connection info:
cat /var/lib/crashplan/.ui_info ; echo
12. Edit the C:\ProgramData\CrashPlan\.ui_info or on a mac /Library/Application Support/CrashPlan/.ui_info file with the output from the previous command:
4243,13d436c0-230a-4242-b258-574e60e62a9f,yournasip
I Hope that this will help the people struggling with the update.
Good Luck!!
Best Regards,
Reijer
I for my part are trying to investigate other options. Currently Hyperbackup + Amazon S3 – not sure, but seems to be stable as well – no idea about the costs, but I cannot afford an unsupported / unreliable backup solution.
Interesting you should say that. I have a local USB Hyper backup with versioning – I use offsite backup as a single copy file once each day (may change this to once a week). I looked in to Amazon both Glacier and S3 – had some success with Glacier but I could never get S3 backups to work at all. It’s another case of trying and seeing if it works for you. Amazon is tricky with pricing – what I like about Crashplan is you have unlimited storage for a monthly fee and can download anything you like when you want. You also get versioning.
Be careful with anything else if it’s for home use – S3 is more expensive to store – Glacier is cheap to store but if you need anything be prepared to wait to get it – plus additional retrieval charges.
I tinkered with Amazon for a few days and not that impressed so far – I’m not putting this down to Amazon but I think the Synology apps have issues with some files or not resilient to network interruptions.
That said you have to think that Crashplan will not tollerate a single headless client with unlimited storage on their servers forever (could be wrong)
This comment @chrisnelson.ca fixed it for me (DS214+ @DSM6.0):
h**p: — chrisnelson . ca/2015/07/02/fixing-crashplan-4-3-0-on-synology/#comment-19061
I have a DS214, and I haven’t upgraded to DSM 6. I was able to get Crashplan running again.
I have a Java 8 package installed (java8/ejdk1.8.0_51/linux_arm_sflt), and I haven’t observed any Java issues.
I used the manual installation instructions from Peter in this thread and from http://chrisnelson.ca/2015/07/02/fixing-crashplan-4-3-0-on-synology/ (has updates for 4.6 Crashplan). Thanks to both Peter and Chris (and patters!)
Like Peter, I needed to install the 359 update first, then the 382 update.
You need to delete extra directories in /var/packages/CrashPlan/target/upgrade, so that there is just one for 359 and one for 382, and rename the script in each directory, which disables the script.
After I successfully updated using the 359 package, my upgrade to 382 failed. Turned out more directories for 382 appeared after the 359 update. Once I deleted the new 382 directories, I was able to update to 4.6.0, and Crashplan ran on the Synology and did backups.
My old 4.5.2 client is still working, with the GUID from previous installs. I’ll upgrade the client later
http://chrisnelson.ca/2015/07/02/fixing-crashplan-4-3-0-on-synology/
Synology DSM v6
I don’t recommend upgrading to v6 at this time (March 2016) if you do not have an Intel based CPU in your Synology NAS as there have been issues reported with the java packages in the comments here as well as on Patter’s page. If you do have an Intel based CPU you will need to use 7z commands on DSM6 instead of zip commands. Examples for CrashPlan 4.6.0:
sudo 7z e -y -o/var/packages/CrashPlan/target/lib /var/packages/CrashPlan/target/upgrade/1435813200460_382.jar “*.jar”
sudo 7z e -y -o/var/packages/CrashPlan/target/lang /var/packages/CrashPlan/target/upgrade/1435813200460_382.jar “lang/*”
I’ve got the 4.6 client working now. Some notes:
– Code 42 recommends updating the cache before uninstall/reinstall of the client, but that’s a waste of time. It refreshes the cache again anyway.
– My authentication token didn’t change, but I needed to edit the IP for my NAS in a client side file.
– After editing the IP address, the new 4.6 client didn’t behave normally – there was an error about an incorrect version.
– After I rebooted my Windows client system, I had to log in a couple of times and “adopt” the NAS.
– After adopting, the client was able to communicate with the server, and my old settings were in place, no full backup needed. And the next backup of new files uploaded pretty quickly, 2 GB in 15 minutes, around 20 Mbps.
And I’m definitely not updating to DSM 6 until Synology fixes the issues on ARM systems.
After spending way too much time during the last three years fixing and patching up Crashplan I used the last few days to check out other options. Should be simple and reliable and with as little maintenance as possible. And free if possible as my budget is limited. And –surprise – Synology Cloud Station does the job very well, with some adjustments and partly with the use of CCC. Even for my sort of complicated situation: daily backup of a handful of Macs and several external HDDs, all Macs in different places on two continents, and two DSs, both remote as well.
As much as I liked this forum and the outstanding willingness to help (thanks again everyone who invested so much time and effort!), I’m so happy to say: Good-bye, Crashplan. I’m done with you.
I still see some comments about Crashplan and Java errors – there was a fix provided on here where you download a jna*.jar file and copy over to Crashplan directory. There have been some successes with upgrades if following a certain route, i.e. patch in a certain order – I wonder if installing the 4.6 version fresh causes problems? Although I did try 4.5.2 and 4.6 on DSM 6 and both had the same Java iNotify problem. Only until I copied over the newer jna*.jar file did Crashplan start working again.
I am though having some issues with 4.6 and DSM 6 running incredibly slowly with backups taking days where in the past hours. Pruning is now in to the 2nd day. Backup upload speeds through client GUI has a huge range from 120kpbs to 2.5mps – would be interested to hear other people’s experience of 4.6 on DSM 6
My experience on DS214se (ARM), sortof working! I use NAS as target for client backups
I upgraded to CP 4.6 in the usual manual way before DSM 6 arrived and CP was working as normal.
Not being aware that I could have prevented the DSM 6 upgrade, it arrived in due course, and CP started behaving badly, with client messages “Connecting to backup destination ..” and server report “destination not available”.
I have been reviewing comments from contributors here (thank you!) but have not taken any action yet (other than mutliple restarts of clients and server and setting up CP on one of my clients to backup to a shared drive on the NAS, as a precaution). Having monitored CP over the past week, I have found that CP on NAS works, sortof! For a reason I have not yet discovered, the backup starts working from both my clients about midday each day and continues to work until CP shutdown late in the evening to allow NAS to hibernate disks. This behaviour has been consistent for a week now.
Thanks David – I had got so close to this fix but with one important detail wrong.
For those who haven’t seen it there is a comment on this page with the fix for ARM processors:
http://chrisnelson.ca/2015/07/02/fixing-crashplan-4-3-0-on-synology/comment-page-1/#comment-19061
In short, if you have fixed the issue with it not even starting due to the incorrect path, you need the following to get it to scan files again:
1. Stop Crashplan service through diskstation package manager
2. Download: https://maven.java.net/content/repositories/releases/net/java/dev/jna/jna/4.2.2/jna-4.2.2.jar
3. go to /var/packages/CrashPlan/target/bin and make a backup from jna.jar ( mv jna.jar jna.backup )
4. rename the downloaded jna-4.2.2.jar to jna.jar
5. copy the jna.jar you downloaded to the /var/packages/CrashPlan/target/bin directory
6. start Crashplan
The mistake I made when searching for a fix was to replace the jar in the lib directory, not the one in the bin directory.
If you are starting from scratch (you’ve just upgraded to DSM 6 and crashplan is in state ‘Stopped’), follow the full instructions here: http://chrisnelson.ca/2015/07/02/fixing-crashplan-4-3-0-on-synology/comment-page-1/#comment-19061
What a relief! My crashplan is functioning properly again!
With BIG thanks to @Martin Keinman (in the comments section at http://chrisnelson.ca/2015/07/02/fixing-crashplan-4-3-0-on-synology/) this fixed my issue “Exception in thread “W30145090_ScanWrkr” java.lang.NoClassDefFoundError: Could not initialize class com.code42.jna.inotify.InotifyManager” / GUI showing “Waiting for Backup”
I’m running CrashPlan 4.6.0 on a DS213j with DSM6.0 and Java 1.7.0_75-0034
(stop crashplan)
10. Download: https://maven.java.net/content/repositories/releases/net/java/dev/jna/jna/4.2.2/jna-4.2.2.jar
11. go to /var/packages/CrashPlan/target/bin and make a backup from jna.jar ( mv jna.jar jna.backup )
12. rename the downloaded jna-4.2.2.jar to jna.jar
13 copy the jna.jar you downloaded to the /var/packages/CrashPlan/target/bin directory
(start crashplan)
Please beware that the “jna.jar” exists in both “bin” and “lib” folder. The fix is to do the rename/replace in the “bin” folder and leave the “lib” folder untouched.
there is a solution at the following link by martin kleinman.
http://chrisnelson.ca/2015/07/02/fixing-crashplan-4-3-0-on-synology/
These last few steps did it for me on my ARM box DSM6.0.
10. Download: https://maven.java.net/content/repositories/releases/net/java/dev/jna/jna/4.2.2/jna-4.2.2.jar
11. go to /var/packages/CrashPlan/target/bin and make a backup from jna.jar ( mv jna.jar jna.backup )
12. rename the downloaded jna-4.2.2.jar to jna.jar
13 copy the jna.jar you downloaded to the /var/packages/CrashPlan/target/bin directory
14 start Crashplan
15. check /var/packages/crashplan/.ui_info for a new guid when you can’t connect.
patters,
We haven’t heard from you on this issue. I hope that you are all right and just on vacation.
The new DSM 6.0 has a new fonction : HyperBackup with differential backup that can be used with Hubic. Do you know Hubic ? it’s a OVH’s brand that offers 10to for 50€/year (so quite similar to Crashplan : https://hubic.com/en/offers/ ).
As Hubic is natively integrated in DSM, you should never have problems with updates or so on… I really loved to used Crashplan, but trying to fix the updates every month is giving me some headaches.
patters please help! DSM 6 with current version just starts and then stops (not even getting to the point of trying to get the client to work).
Are others moving to A3 or Glacier where support is integraed into DSM?
I fixed crashplan 4.6 on DSM 6
See My step by step Guide here:
http://www.mydreamlist.nl/view/34/name/crashplan/
I posted It multiple timer on this forum but It’s NOT showing up.
Good luck!
Reijer
Crashplan is working again on my disk station, except for the logging information (?).
This worked for me (DS413j, DSM6.0, Java8):
http://www.mydreamlist.nl/view/34/name/crashplan/
My Crashplan is working again, except for the log function. I followed instructions in
http://www.mydreamlist.nl/view/34/name/crashplan/ (DS413j, DSM 6, Java8, CP4.6 (eventually)).
This has completely stopped working for me with DSM 6. Has anyone figured out what the issue is? Is a fix coming?
Funny thing… my Crashplan on the NAS has been running just fine… but little did I know, it really wasn’t backing up. It had reverted to the computer that was attached. I just logged in to Crashplan and my 1.3tb is gone. I am thankful for patters keeping this going, but clearly Code42 is not the company for me. I would have been happy to pay more for support…pay more for a NAS solution with them, but they don’t want my business and that is fine with me. Fortunately, I had sent an older Synology across the country to my family and can use it for offsite backup. Absent a cloud solution that makes sense, looks like that will be the path for me from this point onward.
The complete overhauls and changes to the headless system from Code42 honestly has me believing that it is intentional. They don’t seem to publish anything that would explain how these changes are improving the system for users at all, so it leaves me with the assumption that it intentional disruption. I could be wrong… but then again my 1.3tb vanished. Along with it will be the money I spend with them.
Thanks again Patters… best of luck to you all. Hope Synology finds a true partner that makes sense, because this really doesn’t any longer.
As stated above, there are plentiful supported ways to use CrashPlan for Synology backup.
Hi Patters, does your Synology Crashplan package still require external JRE? I ask because it seems that it is getting its own JRE (making the /upgrade and /jre subfolders within /var/packages/CrashPlan/target). More generally, is this a good place to ask questions or report bugs, or do you prefer another contact method? Thanks!
Hey there,
Looks like there is yet another update for Crashplan – going to 4.6 now. Our headless app has been down for 16 days now. Any idea when a new package will be available?
Thanks for all your help Patters!
discontinued?
Hi all, Just to let everyone know my experiences with Crash Plan. I have a DS214 play running DSM 6.0-7321. I have Crash plan version 4.6.0 (although the Crash Plan package is still showing version 4.5.2-0037, I know 4.6.0 is installed by viewing the log) installed on the 214. I have the Crash Plan version 4.6.0 client installed on my PC. I have 2.9tb of data backed up and everything is working as it should. Every few days the client on the PC wouldn’t see the DSM 214, I noticed that the .ui.info (in programmeData/CrashPlan) kept changing. I then remembered that I had forgotten to make this file read only after running the SSH session command echo `cat /var/lib/crashplan/.ui_info` (as per Patters instructions above in the main guide). Hope this helps.
Thank you for postings this! I have this problem and didn’t what it was. Could you tell me exactly how to fix it. I am not that great with Linux.
Hi patters and friends,
I really hope patters can release his latest version of CrashPlan that can work with DSM 6. My backup hasn’t been working since I upgraded my DSM. Yes, a big mistake I know. It really feels like the end of the world to me. :) Please release the newest version soon! Cheers!
Steve
Can we expect an update, anybody knows?
It’s just if an update is coming, I don’t want to spend time trying to fix things – I’ll just wait then :)
Followed this guide, switch made it work again for me – AWESOME! :)
https://idmedia.no/general/crashplan-4-5-0-released/
Worked for me as well – great find!
Worked great for me as well (DSM 6.0). Thanks for posting! My mac/pc 4.6 clients are happy again.
perfect!
Guys, let me recap the whole situation.
DSM 6 and Crashplan 4.60 have issues.
This is a fact.
It does not affect Intel based NAS.
This is a fact.
If you upgrade to DSM 6, you have to use 7zip.
This is a fact.
It looks like the problem is due to java incompatible versions.
There are several solutions.
For me, the one that worked was the one posted by Heiko:
“I fixed this error, and CrashPlan is now fully working on my DS214se (DSM 6). I found that the jna.jra that ships with CrashPlan needs to be updated.”
I own a DS215J+
I think that the correct solution (for ARM based NAS) is:
1 – Install Synology Java
2 – Upgrade Crashplan as usual using 7z
3 – change the JRE position with a symbolik link to the Java installed on point 1
4 – Change the “jna.jra”
I do not understand why nobody (Patters) came out with a new version.
I do not have good feelings about the future…
Let’s wait for the events.
My 2 cents.
Hmmmm… why someone´s hobby project doesnt have 0-day support?
Lazy bastard.
There is a “non written law” among SW developers writing for free: if you are not sure you can support the project… make source code public.
Should be quite easy :-)
I’m conflicted about that unwritten law. I love the practice of course – in fact when I got a Docker-based solution together to replace this package on my system, I pretty quickly open sourced the repo and even linked to it here (https://github.com/ajkerrigan/crashplan-docker-synology). It’s been cleaned up a bit since then and used by other people in my situation. I encourage people to do whatever they want with the code or concept (even if that just means pointing out flaws).
However, patters has hosted this package, made it freely available and provided free support for years. It bugs me a lot to think that the end result of all that is an obligation to either provide perpetual free support or release his source. It’d be a nice gesture, but as an unwritten rule it seems pretty audacious.
He never promised us anything, and he really doesn’t owe us anything.
@Luca: Yes, this was my solution as well. Partly though. First, yes, it seemed to work. The new java soft link seemed to resolve the issue with the upgrade of the crashplan client. And at last my synology folders were listed in the crashplan app. But, unfortunately the crashplan client is not able to scan my files for incremental changes. In other words: nothing happens during my scheduled backup time slot. No files are being backed up at all. I am able to successfully start my PC client and see the folders, but no backup is done.
I agree with you: I do not feel too comfortable with this. I will probably look for another solution within short.
I totally agree. This solved the problem for me as well (ds215j). The last thing with “initial backup not complete” was resolved by replacing the jre.jar file (Using WinDcp commander for the file transfer).
@Luca Actually the source code is in the post at the top, so go ahead…
Thanks Luca, appreciate the observation to upgrade as usual using 7z. For those unfamiliar with unzip and 7z command lines, a beneficial add to your post would be to share what the 7z command line would be. I guessed and got it wrong, my CrashPlan upgrade target folder is now FUBAR.
Could you please post the corresponding 7z commands which need to be used instead of unzip?
Found out myself. In /var/packages/CrashPlan/target/upgrade use
7z e 1435813200460_403.jar “*.jar” -o/var/packages/CrashPlan/target/lib/
7z e 1435813200460_403.jar “lang/*” -o/var/packages/CrashPlan/target/
Thanks! Two points however: 1) The quotation marks are corrupted into “smartquotes” by this blog comment system. So they need to be changed to standard “non-smart” quotes. 2) I’d recommend adding the switch “-aoa” to the end of each line, which triggers 7zip to automatically overwrite any existing files with the same name.
My Crashplan (DS413j, DSM6, Java8, CP4.6) works again, thanks to these instructions: http://www.mydreamlist.nl/view/34/name/crashplan/
On top of that I change the access right of the log files (to enable logging again)
I’ve been using Patter’s package for quite a while now, and haven’t had any issues since now. I’ve had the upgrading issue for the past few releases, but Chris Nelson and Patters instructions have always got me by. I have an RS212, and just can’t get this to work. I’ve tried all the Has anyone else with a 212 model or similar got this to work on DSM 6?
Output from engine_output.log shows:
jtux Loaded.
# A fatal error has been detected by the Java Runtime Environment:
# SIGILL (0x4) at pc=0x54c42988, pid=5865, tid=1082590320
# JRE version: Java(TM) SE Embedded Runtime Environment (7.0_75-b13) (build 1.7.0_75-b13)
# Java VM: Java HotSpot(TM) Embedded Client VM (24.75-b04 mixed mode linux-arm )
# Problematic frame:
# C [jna4038927632299834532.tmp+0x12988] ffi_prep_cif_machdep+0x184
# Core dump written. Default location: /volume1/@appstore/CrashPlan/core or core.5865
# An error report file with more information is saved as:
# /volume1/@appstore/CrashPlan/hs_err_pid5865.log
Any help appreciated! Posting as it may be something quite simple that another user has come across and found a solution for… (I hope!)
Cheers, Andrew
Have you tried replacing jna.jar with the latest from the maven repository? ( Version 4.2.2. ).
I had to do these steps:
1. Remove Crashplan
2. Install Crashplan but stop it as soon as you can ( do not let it update! )
3. Login as root
4. make a backup from install.vars ( to e.g. install.old
5. Start Crashplan and let it update ( will fail anyhow )
6. Stop Crashplan again ( if it is started )
7. expand the update ( jar file )
7z e -y -o/var/packages/CrashPlan/target/lib /var/packages/CrashPlan/target/upgrade/1435813200460_382.jar “*.jar”
7z e -y -o/var/packages/CrashPlan/target/lang /var/packages/CrashPlan/target/upgrade/1435813200460_382.jar “lang/*”
8. remove the jre directory! ( rm -rf jre )
9. remove install.vars and copy the install.old to install.vars ( has to do with the used java home )
10. Download: https://maven.java.net/content/repositories/releases/net/java/dev/jna/jna/4.2.2/jna-4.2.2.jar
11. go to /var/packages/CrashPlan/target/bin and make a backup from jna.jar ( mv jna.jar jna.backup )
12. rename the downloaded jna-4.2.2.jar to jna.jar
13 copy the jna.jar you downloaded to the /var/packages/CrashPlan/target/bin directory
14 start Crashplan
15. check /var/packages/crashplan/.ui_info for a new guid when you can’t connect.
HTH
Hi Andrew,
I have the exact same error on my ds413j. Tried everything (reinstalling the package, reinstalling java8) but every result leads to core being dumped. I wonder if it has anything to do with memory issues. My ds413j only has 512Mb of RAM.
Have you found a solution yet?
Cheers,
Tom
Hi Andrew,
Did you manage to find a solution. I have the exact same problem on a DS413j.
Thanks,
Tom
Just an update for what worked for me (I posted some updates above)
DS413 (so PPC Cpu)
DSM 6.0
Install Patter’s Java 8
Uninstall and reinstall Patter’s Crashplan
Sym link the Crashplan JRE (might be more elegant ways of doing that but it works)
At this point I got the iNotify errors, but the existing backup was “adopted” within a day.
I observed that the Crashplan engine would repeatedly restart when trying to back up new files, with the UI disconnecting each time.
This has happened before so I already have my backups in smaller timed filesets but I’ve increased the Java heap from 512m to 768m and, for my filesets, updated files are now being backed up and the Crashplan engine is now stable. So it’s possible that 4.6.0 is a bit more of a memory hog the 4.5.x
So if you are at a point where Crashplan starts and adopts but doesn’t seem to back up new files then try increasing the heap size if you can. Remember to do it in Patter’s package config, not the the Crashplan config.
what is “Sym link the Crashplan JRE”? Thank you!
See my previous post for detailed notes, or use the JAVACOMMON method by Fred below which is more elegant.
Essentially it looks like, at least for some of us, Crashplan tries to use it’s own Intel x86 java, which will always fail on on non Intel x86 CPUs.
FINALLY WORKING!!! DS715 (with Annapurna Alpine chip)
Make sure Patters’ Java7 package is installed:
Edit ‘/var/packages/CrashPlan/target/install.vars’:
change
JAVACOMMON=/volume1/@appstore/CrashPlan/jre/bin/java
into
JAVACOMMON=/volume1/@appstore/java7/jre/bin/java
Restart CrashPlan.
What an ordeal! Thanks Fred (& Luca). This worked for me to get CP back up and running. What to do going forward though is not such an easy one…Thanks again all.
This worked for me too! :D At least, the app is running and at first it seems to work fine.
However, backup to CrashPlan Central is stuck on “Connecting to backup destination”. Although the CrashPlan Central destination is lid “green”, indicating it is connected, it is not able to initiate the backup (same problem with all incoming backups).
CrashPlan troubleshoot guide says this is obviously a sign of a firewall or an antivirus program blocking crashplan’s connections.
Have tried all possible DSM 6.0 firewall exceptions (including disabling it altoghter), but still no luck.
Is anybody else having these issues?
Thanks it was quite simple to get to work using DS212j (with ARM5)
I did a fresh install, as I have a newly installed DSM 6 DiskStation
Installed java7
Rebooted Diskstation
Installed CrashPlan using Patters 4.52 package
Rebooted Diskstation
Logged in via SSH (from my desktop)
ssh -p admin@ip-adress
cd /var/packages/CrashPlan/target
sudo vi install.vars
changed
JAVACOMMON=/volume1/@appstore/CrashPlan/jre/bin/java
into
JAVACOMMON=/volume1/@appstore/java7/jre/bin/java
How to use the vi editor
Type “i” to go to edit/insert mode
Then I made the changes
Press ESC
Then type
“:wq”
To write and quit
Restarted DiskStation
Did connect using my disktop installation of CrashPlan (4.6.0) after I did the settings Patters recommand about token value:
4243,9ac9b642-ba26-4578-b705-124c6efc920b,0.0.0.0….
Thanks works like a charm! Note use: JAVACOMMON=/volume1/@appstore/java8/ejdk1.8.0_77/linux_arm_sflt/jre/bin/java if you want to use Java 8. All up and running again here.
Yeah finally it’s working again!
Note if you are on Java 8 use: JAVACOMMON=/volume1/@appstore/java8/ejdk1.8.0_77/linux_arm_sflt/jre/bin/java
You can also just stop/start the service instead of rebooting it seems.
Thanks frold – worked for me.
getting good throughput?
thanks
Confirmed – working for me on DS231+
This worked for me.
I used JAVA 8 and used and changed the line to:
JAVACOMMON=$JAVA_HOME/bin/java
the Variable $JAVA_HOME translate into /volume1/@appstore/java8/jre
It worked on DS115j and DS213j
Does anyone know Patters and can tell us if:
1) Is he all right?
2) Does he still wants to support this?
I’ve always appreciated this installation for Crashplan on DSM. However, if this is being abandoned I’d like to know so I can plan accordingly.
Thanks.
Hal
Patters, can you please chime in here. I am not asking for you to fix anything, just a shout out if this project is still supported or not. (Hopefully all is well with you.)
I have found the solution for arm on ds414, but “Your comment is awaiting moderation.” since a long time…
You must change the jna component to make crashplan working…
It seem that patters is not here for the moment.
Hello bagupremier
Please try to submit your solution in small pieces, it might go through without the moderation. Remember to number the pieces so we can see if any piece is missing :-)
are you getting good throughput?
i’m having difficulties on a ds414, could you please share your findings? I tried some of the above mentioned solutions but none did really work.
Those of you who has a problem with “initial backup not complete”: Check out the post from Martin Kleinmans about downloading a new java package and replacing the old jre.jar file in the given library. Seems to work. My cloud files are currently being synchronized again.
http://chrisnelson.ca/2015/07/02/fixing-crashplan-4-3-0-on-synology/
/Mikael
DS213j + CP 4.6
pointing it to the proper java works. i have java 8 from other sources on my ds212j. i updated my JAVACOMMON=/volume1/@appstore/java8/ejdk1.8.0_77/linux_arm_sflt/jre/bin/java
so far crashplan is working again.
Following these instructions, I managed to get Crashplan running again (DS413j, DSM6, Java8, CP 4.6): http://www.mydreamlist.nl/view/34/name/crashplan/
On top of that I needed to change the access rights of the log-files to get the log-facility working again.
I cant get mine to work. Anyone know of an alternative to this that doesnt cost too much
CrashPlan stopped running on my NAS. In the engine_error.log I read:
Exception in thread “Thread-1” com.code42.exception.DebugRuntimeException: Unable to persist ServiceModel, Invalid signature file digest for Manifest main attributes, conf/service.model
Does anyone have a clue what I can do about this?
Found the solution for ARM here : https://www.reddit.com/r/synology/comments/4butct/repair_crashplan_upgrade_on_dsm_6/
Remove Crashplan
Install Crashplan but stop it as soon as you can ( do not let it update! )
Login as root
make a backup from install.vars ( to e.g. install.old
Start Crashplan and let it update ( will fail anyhow )
Stop Crashplan again ( if it is started )
expand the update ( jar file )
7z e -y -o/var/packages/CrashPlan/target/lib /var/packages/CrashPlan/target/upgrade/1435813200460_382.jar “.jar” 7z e -y -o/var/packages/CrashPlan/target/lang /var/packages/CrashPlan/target/upgrade/1435813200460_382.jar “lang/”
remove the jre directory! ( rm -rf jre )
remove install.vars and copy the install.old to install.vars ( has to do with the used java home )
Download: https://maven.java.net/content/repositories/releases/net/java/dev/jna/jna/4.2.2/jna-4.2.2.jar
go to /var/packages/CrashPlan/target/bin and make a backup from jna.jar ( mv jna.jar jna.backup )
rename the downloaded jna-4.2.2.jar to jna.jar 13 copy the jna.jar you downloaded to the /var/packages/CrashPlan/target/bin directory 14 start Crashplan
check /var/packages/crashplan/.ui_info for a new guid when you can’t connect.
This work fine for me on DSM 6.0 + DS414
Just checking recently and notice the backup speed drop tremedously and it does not take up much cpu and memory unlike the past where it eat up everything. Anyone know what happen?