CRASHPLAN UPGRADE FAILED INSTALL
CRASHPLAN UPGRADE FAILED UPDATE

ufw allow from to any port 4242 is the command I used to open a port back to my office for backups to go back and forth between servers. The new version also required me to open some ports in the Ubuntu Firewall. I only noticed this problem when our backups stopped working and the subsequent failure when we had a production server go down. Prior upgrades were seamless and required no intervention. I’ve lost a huge time commitment fixing these issues brought about by Crashplan’s upgrade processed from 3.x to 4.x. During the installation process java-common was updated with compliant java files as Crashplan does not work with the Oracle version apparently.

CRASHPLAN UPGRADE FAILED INSTALL

I went through the install process again. Once removed, I installed java using the guide here and the useful first comment for default install. I resolved by uninstalling and finding all crashplan install files and locations. Code42, you need a reasonability check here! This continued long enough to spool up to our entire drive size. Crashplan was creating a new folder every 30 minutes and then finding that v1.6 of the ubuntu java-common package was installed and then failing out of the process.

CRASHPLAN UPGRADE FAILED UPDATE

We find that in our /usr/local/crashplan/upgrade directory there are effectively an unlimited number of time stamped update folders. We look and find there is zero space left on the drive. Download of upgrade complete version 1425276000420. So, before you go down the road of manual jre installations, look into this first.īackups started working again after the manual jre upgrade, some hassle, a lot of searching, finding logs, etc. The log for the failing CrashPlan package would look something like this: CrashPlan started, version 3.7.0, GUID 559750658046558476 Upgrades available at :443 Downloading a new version of CrashPlan. Their newer software versions, at least after 4.4.1, seem to upgrade the native jre package properly and require little intervention. I think Code42 (Crashplan’s creator) was inundated with failures as they released some software which essentially broke their linux based backbone. I will say that I didn’t install the java package on two other linux servers and they subsequently just worked themselves out. Importantly, to do this you must change /usr/local/crashplan/install.varsįrom JAVACOMMON=/usr/local/crashplan/jre/bin/java I ended up installing the 12.04LTS java-common package a few months ago which is still v1.6. The documentation for a headless client is poor if you run into any issues. My headless linux boxes stopped backing up to Crashplan earlier this year.

Crashplan upgrade failed