Crashplan 4.8.2

[Andrew076]

For those of you who are hesitant to do your crashplan update when everything is working until someone else does it (like me...) I am happy to report that the update to 4.8.2. went off with out a hitch.

The steps I took from within the Crashplan Jail were:

$ cd /usr/pbi/crashplan-amd64/share/crashplan
$ wget --no-check-certificate https://download2.code42.com/installs/linux/install/CrashPlan/CrashPlan_4.8.2_Linux.tgz
$ tar -xf CrashPlan_4.8.2_Linux.tgz
$ cd crashplan-install
$ cpio -idv < CrashPlan_4.8.2.cpi
$ service crashplan stop
$ cd ..
$ rm -r lib*
$ cp -r crashplan-install/lib* .
$ service crashplan start
$ exit

 

[nickt]

Legend!!

I was just starting the trawl through the FreeNAS forum after noticing that my crashplan install was failing to upgrade from 4.8.0 to 4.8.2 every hour. Grimacing at the prospect of yet another painful crashplan update, I saw your post, and - as promised - it went without a hitch!

Oddly, the autoupdate was failing for two - seemingly - stupid reasons. First was that it determined that my java version was wrong (it isn't) and second due to a certificate error in the wget step in trying to download a "new" java version from code42. Can't really understand why the autoupdate would be quite so dumb...?

Code:

[root@crashplan_1 /usr/pbi/crashplan-amd64/share/crashplan/log]# cat upgrade.1436674800482_4.1493378078595.log
TARGETDIR=/usr/pbi/crashplan-amd64/share/crashplan
BINSDIR=/usr/pbi/crashplan-amd64/share/crashplan/bin
JAVACOMMON=/usr/pbi/crashplan-amd64/jre-linux-i586-1.8.0_72/jre/bin/java

<snip>

Sourcing ../../install.vars...
Current CrashPlan Backup Engine:
Stopping using ../../bin/CrashPlanEngine...
Stopping CrashPlan Engine ... OK
Ensuring the UpgradeUI is not running.
UpgradeUI is shut down.
JAVACOMMON is set: /usr/pbi/crashplan-amd64/jre-linux-i586-1.8.0_72/jre/bin/java
Current Java Version:
The Current java is not supported. Embedding a supported version.
The Current java is not compatible. Embedding a compatible version.
Download JVM from http://download.code42.com/installs/proserver/jre/jre-linux-i586-1.8.0_72.tgz
downloading the JRE using /usr/local/bin/wget
--2017-04-28 21:14:50--  http://download.code42.com/installs/proserver/jre/jre-linux-i586-1.8.0_72.tgz
Resolving download.code42.com (download.code42.com)... 216.17.8.19
Connecting to download.code42.com (download.code42.com)|216.17.8.19|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://download.code42.com/installs/proserver/jre/jre-linux-i586-1.8.0_72.tgz [following]
--2017-04-28 21:14:51--  https://download.code42.com/installs/proserver/jre/jre-linux-i586-1.8.0_72.tgz
Connecting to download.code42.com (download.code42.com)|216.17.8.19|:443... connected.
ERROR: cannot verify download.code42.com's certificate, issued by 'CN=thawte SSL CA - G2,O=thawte\\, Inc.,C=US':
  Unable to locally verify the issuer's authority.
To connect to download.code42.com insecurely, use `--no-check-certificate'.
Unable to download JRE from http://download.code42.com/installs/proserver/jre/jre-linux-i586-1.8.0_72.tgz; please check network connection
Starting using ../../bin/CrashPlanEngine...
Starting CrashPlan Engine ... Using standard startup
OK

But never mind - your process worked perfectly - so thanks!!

Nick

 

[Andrew076]

Legend!!

I was just starting the trawl through the FreeNAS forum after noticing that my crashplan install was failing to upgrade from 4.8.0 to 4.8.2 every hour. Grimacing at the prospect of yet another painful crashplan update, I saw your post, and - as promised - it went without a hitch!

Oddly, the autoupdate was failing for two - seemingly - stupid reasons. First was that it determined that my java version was wrong (it isn't) and second due to a certificate error in the wget step in trying to download a "new" java version from code42. Can't really understand why the autoupdate would be quite so dumb...?

Code:

[root@crashplan_1 /usr/pbi/crashplan-amd64/share/crashplan/log]# cat upgrade.1436674800482_4.1493378078595.log
TARGETDIR=/usr/pbi/crashplan-amd64/share/crashplan
BINSDIR=/usr/pbi/crashplan-amd64/share/crashplan/bin
JAVACOMMON=/usr/pbi/crashplan-amd64/jre-linux-i586-1.8.0_72/jre/bin/java

<snip>

Sourcing ../../install.vars...
Current CrashPlan Backup Engine:
Stopping using ../../bin/CrashPlanEngine...
Stopping CrashPlan Engine ... OK
Ensuring the UpgradeUI is not running.
UpgradeUI is shut down.
JAVACOMMON is set: /usr/pbi/crashplan-amd64/jre-linux-i586-1.8.0_72/jre/bin/java
Current Java Version:
The Current java is not supported. Embedding a supported version.
The Current java is not compatible. Embedding a compatible version.
Download JVM from http://download.code42.com/installs/proserver/jre/jre-linux-i586-1.8.0_72.tgz
downloading the JRE using /usr/local/bin/wget
--2017-04-28 21:14:50--  http://download.code42.com/installs/proserver/jre/jre-linux-i586-1.8.0_72.tgz
Resolving download.code42.com (download.code42.com)... 216.17.8.19
Connecting to download.code42.com (download.code42.com)|216.17.8.19|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://download.code42.com/installs/proserver/jre/jre-linux-i586-1.8.0_72.tgz [following]
--2017-04-28 21:14:51--  https://download.code42.com/installs/proserver/jre/jre-linux-i586-1.8.0_72.tgz
Connecting to download.code42.com (download.code42.com)|216.17.8.19|:443... connected.
ERROR: cannot verify download.code42.com's certificate, issued by 'CN=thawte SSL CA - G2,O=thawte\\, Inc.,C=US':
  Unable to locally verify the issuer's authority.
To connect to download.code42.com insecurely, use `--no-check-certificate'.
Unable to download JRE from http://download.code42.com/installs/proserver/jre/jre-linux-i586-1.8.0_72.tgz; please check network connection
Starting using ../../bin/CrashPlanEngine...
Starting CrashPlan Engine ... Using standard startup
OK

But never mind - your process worked perfectly - so thanks!!

Nick

Glad it worked for you.

 

[millst]

I wouldn't call certificate validation stupid. The certificate store is probably out-of-date or misconfigured. Using the --no-check-certificate disables validation. Without it, you risk downloading a tampered version of the software.

-tm

 

[Eric Blau]

Thanks for the steps for upgrading to 4.8.2. I wrote down similar steps for previous upgrades. I needed to add a step to get things working. After your step:

$ cp -r crashplan-install/lib* .

I had to add:

$ cp -r crashplan-install/lang .

otherwise CrashPlan would not start. It exited with the following exception:
[04.29.17 13:01:59.667 ERROR main com.backup42.service.CPService] Error starting up, java.util.MissingResourceException: Can't find bundle for base name txt, locale en
STACKTRACE:: java.util.MissingResourceException: Can't find bundle for base name txt, locale en
at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1564)
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1387)
at java.util.ResourceBundle.getBundle(ResourceBundle.java:773)
at com.backup42.service.history.HistoryLogger.reinitBundle(HistoryLogger.java:54)
at com.backup42.service.history.HistoryLogger.init(HistoryLogger.java:42)
at com.backup42.service.CPService.start(CPService.java:616)
at com.backup42.service.CPService.main(CPService.java:2563)

After copying the lang directory from crashplan-install, it started fine.

 

[Kulasir]

Thanks for this wonderful thread! My crashplan has been failing for a while and I was able to fix it with info here.

Here are a couple of tips that might be useful to others.
I upgraded to crashplan home. The method describes here still works just replace CrashPlan_4.8.2_Linux.tgz with the pro version. I manually downloaded it from crashplan site.

If you are bugged by crashplan status not returned correctly, you can fix it by following these steps.

1. fix _find_pid in CrashPlanEngine (location: /usr/pbi/crashplan-amd64/share/crashplan/bin )

Code:

_findpid() {
		/bin/ps -awwo 'pid,command'| grep 'app=CrashPlanService' | grep -v grep | awk '{ print $1 }'
}

2. Add status command to /usr/local/etc/rc.d/crashplan

Code:

status_cmd="${command} status"

Insert it after:

Code:

stop_cmd="${command} stop"

Now,

Code:

service crashplan status

will return correct status.