Sep 29: Another update pushed and app stopped working
- September 30, 2016 at 07:12 #771
I’ve just noticed (as I’m trying to get CrashPlan to work because of another issue) that the package stopped working. There was an update pushed on the 29th of September and now the package won’t run.
Does anyone know if the old instructions (manually extract the jars) still work for this new version?
Attachments:You must be logged in to view attached files.October 1, 2016 at 13:03 #773
It seems that the upgrade script downloads a new version of java (1.8) and then messes up the install.
I’d post the log, but I get error 403 forbidden, so the site must be really unhappy about some characters in the log file.
Anyways, it cannot find the backup engine. I tried uninstalling CrashPlan and Java7, then installing Java8, and then installing CrashPlan and telling it to use Java8 from Synology.
It still went ahead and downloaded the upgrade and it’s own version of java and messed up the service.
I’m on holidays for a week, so I hope someone figures out a way to fix this. It’s beyond me why CrashPlan don’t have their own package for Synology.AdvertisementOctober 1, 2016 at 15:21 #775
I do confirm java 8 requirement.
However there are other issues on non x86 or x64 architectures. I can’t get it to work again on ARM (raspberry pi) after the upgrade.October 1, 2016 at 16:19 #776
I’m on DS412+ which is Intel Atom D2700, so x64. It doesn’t help.
Also, the jar file is deleted during the upgrade, so I can’t even manually do it.
The whole /volume1/@appstore/CrashPlan/lib/ directory is missing!October 1, 2016 at 16:27 #777
Is there any way to block the upgrade? Reinstalling the package seems to bring a working version, but then when you stop and start the package it gets the upgrade which destroys the installation.October 1, 2016 at 18:14 #780
I’m not checking my DS right now, but there are some solutions popping. Apparently if you’re using Java 1.7 it will break, and using Java 1.8 will make it run.
Check out what I’ve gathered so far on the page below and share your experiences with it.October 1, 2016 at 19:29 #782
I can confirm the fix #1 worked for me. I didn’t have syno_package.vars anymore, so I created a new file with just the USR_MAX_HEAP setting. I don’t remember if there was anything else in this file.
It seems to be scanning and synchronising, so I guess it’s ok. The upgrade happened in the middle of compacting the backup, and I didn’t have a working crashplan for 12 days, so we’ll see. Fingers crossed 🙂
Thanks for your help!October 3, 2016 at 13:20 #787
I’ve updated the article with basically what was the easiest solution (#3) to implement when this happened with 4.7.0. Read it over there for clarity:October 4, 2016 at 10:44 #791
However there are other issues on non x86 or x64 architectures. I can’t get it to work again on ARM (raspberry pi) after the upgrade.
Yes Marc, I think that there is an architecture issue. On an ARM device, I think that we need a replacement for the new file “libc42archive.so”. With that name probably is a a file created by code42.
There is a note in the release notes for some operating systems “Removes support for Windows XP, Windows Vista, OS X v10.7.5, and OS X v10.8. Devices on these operating systems will not upgrade to CrashPlan app version 4.8.”. We can reinstall the older version, but I don’t know how to make the crashplan client to not update automatically.October 4, 2016 at 10:49 #794
Patters has pushed a new package version today, have you tried it?
“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”October 4, 2016 at 11:29 #797
I suspect we can disable updates by symlinking usr/local/upgrade folder to /dev/null
But I doubt it will work for very long ..October 5, 2016 at 14:49 #803
I can’t say if you can or not, but patters seems to think it’s not possible:
Unfortunately no way to block. At some point (if not already) Code42 will migrate your backup archive on their servers forcing you to version 4.8.0.October 11, 2016 at 18:22 #809
Um guys, I’m starting to worry at this point about the safety of my data.
I got CrashPlan working finally, and thanks for all your help. But now it’s stuck at synchronising and it shows 1 file and 0MB of data. I had 1TB of documents and photos that are irreplaceable.
Is it possible that CrashPlan is deleting all my data now?
I logged into crashplan and it shows my system as 100% backed up with 0MB and 1 file!October 12, 2016 at 02:40 #810
Um guys, I’m starting to worry at this point about the safety of my data. I got CrashPlan working finally, and thanks for all your help. But now it’s stuck at synchronising and it shows 1 file and 0MB of data. I had 1TB of documents and photos that are irreplaceable. Is it possible that CrashPlan is deleting all my data now? I logged into crashplan and it shows my system as 100% backed up with 0MB and 1 file!
If it says “Synchronizing”, my opinion is to let it to its thing. I remember it took more than a day, maybe even a couple, for anything useful to come up eventually. You can also check your backup via web browser on the CrashPlan site, at least you’ll find it there.October 12, 2016 at 09:15 #811
If it says “Synchronizing”, my opinion is to let it to its thing. I remember it took more than a day, maybe even a couple, for anything useful to come up eventually. You can also check your backup via web browser on the CrashPlan site, at least you’ll find it there.
That’s the problem, on CrashPlan site it shows my NAS as 0MB and 100% complete. So it looks like CrashPlan deleted all my files on the site, and I’m afraid it might do the same on the NAS.
I’ve stopped the package for now as I’m not sure what it’s doing. I could just remove the backup and let it upload 1TB of data, but seeing this has shaken my faith in CrashPlan as a product. Also I would lose all version history (it’s probably gone already).
- You must be logged in to reply to this topic.