#Crashplan upgrade failed install
#Crashplan upgrade failed update

#Crashplan upgrade failed install

If you tried recently to install CrashPlan and it failed, or wouldn’t stay running for very long, it looks like the most recent installer has fixed whatever was broken. I’m open to suggestions if anyone knows a way to get it running and keep it that way, but I haven’t found one myself yet. Until further notice, I can’t really recommend running CrashPlan on the Raspberry Pi. My own CrashPi stopped working as well, and I haven’t had a chance to see if I can find a way around it. Some users have reported being able to get the engine running, but not the UI, and others have said that even the engine isn’t working anymore. They never meant CrashPlan to run on ARM devices, and that’s what the Raspberry Pi is.

#Crashplan upgrade failed update

It looks like some recent update has possibly broken CrashPlan on the Raspberry Pi to an extent we’ve not seen before.Ĭode42 wrote a great backup program, but the Pi isn’t an officially supported platform, and never has been, so you can understand why they don’t really have any incentive to come rushing to our rescue. I’ve gotten a number of comments about CrashPlan not working lately. This no longer fits with the “free if you do it yourself” theme of this blog series, so I am an throwing in the towel. It is no longer written in pure Java, some key libraries are only available for Linux running on x86 architectures, and Code42 has eliminated the free home-user product from their offerings meaning that you’ll have to pay for a subscription in order to keep using CrashPlan at all. I’m leaving this here for posterity, but the simple fact is that CrashPlan is no longer a viable option on the Pi. If you run into trouble, reboot and try again.

Initially my service wouldn’t start, but after a reboot it worked just fine. My most recent version was swt-gtk-3.8.2.jar, rather than the …3.8.0 from the original installation. There is a newer version of the standard widget toolkit (SWT) in the current installer, so after installing it, take a look in your /usr/lib/java folder to see what version you have. Updates: It is no longer necessary to replace the Java Runtime Engine since the newer installer doesn’t seem to include it anymore, so skip removing /usr/local/crashplan/jre, which doesn’t even exist, and don’t create the symbolic link. If you have a Pluralsight subscription, please consider watching it. Self-promotion: I’ve recorded this series as a screencast for Pluralsight: