- May 3, 2017 at 21:50 #1020
Thanks for your feedback. I ended up updating myself so that I could confirm the procedure and write a KB article for others to find.
Considering I’ve been experiencing some server timeouts while CrashPlan is running, when accessing my DS412+, I chose to use the dedicated install instead, to see if that makes a difference. It worked and upgraded fairly easily to 4.8.2 and it is now synchronising (without any adoption).
May 3, 2017 at 22:03 #1024
- Using terminal, copy cpio:
sudo cp /volume1/@appstore/CrashPlan/bin/cpio /bin/cpio
- Place the Java SE Runtime file in your public share (you need a Oracle login to get it from here, the latest version of patters’ package requires not the latest Java package, but version 8u121: jre-8u121-linux-x64.tar.gz)
- Uninstall CrashPlan using DSM Package Manager
- Install CrashPlan using DSM Package Manager
- Wait a moment and try to run it (in my case it wouldn’t run) so I uninstalled/reinstalled one more time
- You can read the real time log with terminal open:
tail -f /var/packages/CrashPlan/target/log/service.log.0
- You should see the install script starting the upgrade and finishing with “Service stopped normally”.
- Wait a moment and try to run the package again; if it fails, wait some more time and run again. The tail log should now show lots of output, which means it’s running.
- After this, don’t forget:
- Change the .ui_info file contents, using this guide. Note that this first time the headless .ui_info may be ending in 0.0.0.0 – this means that the next time you restart CrashPlan it will change, and then showing the correct headless server IP.
- Check if the GUI is properly connecting and login
- Change your Java Max Heap size if necessary, using this guide (Solution 2 for persistence) and restart
- Verify your .ui_info connection info again – it may have been broken after the restart
- You may now block the auto-upgrade process, using this guide
- Check if the GUI is properly connecting.
Ok, I’ve placed both instructions on a new KB article, that may help others as well:AdvertisementMay 3, 2017 at 22:18 #1025
Again, DSM has an update I need to apply which most likely will restart Synology and I may be back at square 0, oh the fun.
I’ve upgraded DSM after upgrading CrashPlan and it survived the process just fine!May 3, 2017 at 23:45 #1026
I had the issue which was solved using the article however I had to make 2 changes:
- Used the DSM Java8 install
- Changed the “/var/packages/CrashPlan/target/install.vars” file “JAVACOMMON=/<<volume2>>/@appstore/Java8/j2sdk-image/jre/bin/java”
Also deleted all the CrasPlan folders after the uninstall (for a clean install):
Working like a dream….May 3, 2017 at 23:47 #1027May 4, 2017 at 20:13 #1036
Thanks An for putting this together. Its working for me for last 24 hrs. Followed your instructions.
- Using terminal, copy cpio:
- You must be logged in to reply to this topic.