Crashplan v4.8 not updating/working

Status
Not open for further replies.
Joined
Oct 4, 2016
Messages
3
Hi dear loved community,

I'm casting a line out there to see if anyone was hit by the mandatory update from Crashplan v4.7 to v4.8 recently.

The new version requires a new version of the Java runtime now v1.8 (previously v1.7). The new JVM causes a lot of problem. I've attempted many different solutions (in place update, new Jail with v4.8, using OpenJDK8 instead of the built-in Sun JRE...) none of which are working.

I know this is early but know that Code42 is dropping support for v4.7 as of October 17th. See announcement here.

Hopefully we can discuss those update/install issues here in this thread.
 
Last edited:

picklefish

Explorer
Joined
Mar 13, 2016
Messages
62
I tried very hard to get crashplan to work but found a lot of threads basically saying it's dead and the only real solution is to mount a shared folder from windows and run your backup from a windows box. (Don't know if mac or linux work well). Crash plan do not want to support it.

I'm waiting for FreeNAS 10 so I can hopefully go to using something out of docker. Hopefully: https://github.com/JrCs/docker-crashplan something like that maybe.
 

droeders

Contributor
Joined
Mar 21, 2016
Messages
179
I tried very hard to get crashplan to work but found a lot of threads basically saying it's dead and the only real solution is to mount a shared folder from windows and run your backup from a windows box. (Don't know if mac or linux work well).

I am using the Linux client for Crashplan, as are many others on this forum. Mine runs in a dedicated VM on my Linux workstation, which mounts my NAS shares and backs them up to Crashplan.

It has been working across several Crashplan version upgrades without any modification or re-configuration. I can't speak to Mac compatibility.
 

picklefish

Explorer
Joined
Mar 13, 2016
Messages
62
Ah yeah that makes way more sense than trying to use the FreeNAS plugin like I was trying to do.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,466
Has anyone done that?
I have, and it worked fine for me. I'm now running that VM on a Proxmox host instead, which I think is a better solution, but VirtualBox is easy to get going and doesn't take its own machine. Be aware, though, that FreeNAS is going to be dropping support for VirtualBox in the fairly-near future.
 

picklefish

Explorer
Joined
Mar 13, 2016
Messages
62
FreeNAS 10 is going to have WAY better support for VMs if you want to go that route nico I'd wait for FreeNAS 10 bhyve
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,466

millst

Contributor
Joined
Feb 2, 2015
Messages
141
If you're savvy and willing to invest the effort, you don't need to go the VM route. I've upgraded my jail to 4.8 and it's working fine so far. I used the Oracle JRE: jre-8u102-linux-i586.tar.gz. Besides that, I didn't do anything besides the usual manual upgrade method.

-tm
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,466
If you're savvy and willing to invest the effort, you don't need to go the VM route.
Indeed, CrashPlan can be made to work on FreeNAS, and I hope none of us have given a contrary impression. It's just that some of us feel that the hassle of maintaining the VM is less than the hassle of keeping CrashPlan on FreeNAS up to date.
 

millst

Contributor
Joined
Feb 2, 2015
Messages
141
No, just wanted to let people know that 4.8 works fine. I've even recommended the VM approach in other threads here.

-tm
 

JoeB

Contributor
Joined
Oct 16, 2014
Messages
121
I'm also running CrashPlan on Debian in a virtual-box. Its a fairly easy setup to perform and maintenance is then via a VNC viewer (I use tightVNC which is a java app for windows or web-based) which gives you the GUI for crashplan. So much easier and updates are a breeze. I can share my notes for installing it if required?
 

Kulasir

Cadet
Joined
May 23, 2015
Messages
4
If you're savvy and willing to invest the effort, you don't need to go the VM route. I've upgraded my jail to 4.8 and it's working fine so far. I used the Oracle JRE: jre-8u102-linux-i586.tar.gz. Besides that, I didn't do anything besides the usual manual upgrade method.

-tm
I would like to work it this way. Can you please provide directions? Is it simply installing the JRE and updating the path?
 

millst

Contributor
Joined
Feb 2, 2015
Messages
141
I didn't take any notes. Don't think there was anything else required other than the JRE update. Looks like they upgraded again (1435813200480_316.jar). The battle continues.

-tm
 
Last edited:
Joined
Sep 29, 2016
Messages
2
After doing a manual upgrade, I had to add

export LD_LIBRARY_PATH=/usr/pbi/crashplan-amd64/share/crashplan/jre/lib/i386/jli

and change:

/bin/ps -eo 'pid,cmd' ...

to

/bin/ps -o 'pid,command' ...

in the CrashPlanEngine script to get everything working again.
 

j42k

Cadet
Joined
Oct 16, 2016
Messages
1
I didn't take any notes. Don't think there was anything else required other than the JRE update. Looks like they upgraded again (1435813200480_316.jar). The battle continues.

-tm
Millst -- do you install the JRE update in the jail? If so, what is the Command Line that is used to do this?

I'm willing to try to get Crashplan 4.8.0 working (currently on 4.7), but need pointers on how to update the JRE. Thanks!
 

millst

Contributor
Joined
Feb 2, 2015
Messages
141
You can extract with something like this:

tar xzf jre-8u102-linux-i586.tar.gz

TBH, if you're not already familiar with basic UNIX commands, you're just asking for a world of hurt trying to run Crashplan in an unsupported environment.

-tm
 

0xD0NK3Y

Cadet
Joined
Feb 18, 2014
Messages
5
Hello, I needed to build a fresh Crashplan jail to version 3.8 so I made a note of what worked for me. I am connecting to the headless crashplan via a windows client (https://forums.freenas.org/index.php?threads/crashplan-easier-way-to-connect-headless.23544/) and I do not want the overhead of Virtualbox. All of the following is inside the Crashplan jail.

Install crashplan plugin
Go to Plugins -> Crashplan on the left hand menu in the WebUI and accept agreement
Go to Plugins and turn crashplan on
Is it running?:
ps aux | grep java
Is it listening?:
sockstat -4
Stop crashplan plugin.

Upgrade to 4.6.0
cd /usr/pbi/crashplan-amd64/share/crashplan
wget --no-check-certificate https://download.code42.com/installs/linux/install/CrashPlan/CrashPlan_4.6.0_Linux.tgz
tar -xf CrashPlan_4.6.0_Linux.tgz
cd crashplan-install
cpio -idv < CrashPlan_4.6.0.cpi
cd ..
rm -r lib*
cp -r crashplan-install/lib* .

Modify /usr/pbi/crashplan-amd64/share/crashplan/conf/my.service.xml - change:
<serviceUIConfig>
<serviceHost>127.0.0.1</serviceHost>
<servicePort>4243</servicePort>

to:
<serviceUIConfig>
<serviceHost>0.0.0.0</serviceHost>
<servicePort>4243</servicePort>

Fix up init & java (as per https://forums.freenas.org/index.php?threads/crashplan-will-not-start.44764/#post-301280)
Add after shebang in /usr/pbi/crashplan-amd64/share/crashplan/CrashPlanEngine:
export LD_LIBRARY_PATH=/usr/pbi/crashplan-amd64/share/crashplan/jre/lib/i386/jli
and change:
/bin/ps -eo 'pid,cmd' ...
to:
/bin/ps -o 'pid,comm' ...
Start Crashplan:
service crashplan start
Is it running?:
ps aux | grep java
Is it listening?:
sockstat -4
Stop crashplan plugin.
Lock .ui_info:
chmod go-w /var/lib/crashplan/.ui_info
copy /var/lib/crashplan/.ui_info to your windows system.

Upgrade to 4.7.0 (Not necessarily essential, see note below)
cd /usr/pbi/crashplan-amd64/share/crashplan
Clean up old files:
rm CrashPlan_4.6.0_Linux.tgz
rm -r crashplan-install/

Get next version:
wget --no-check-certificate https://download.code42.com/installs/linux/install/CrashPlan/CrashPlan_4.7.0_Linux.tgz
Unpack:
tar -xf CrashPlan_4.7.0_Linux.tgz
Fix java(as per https://forums.freenas.org/index.php?threads/crashplan-update-failing-due-to-old-java-version.42300/)
Get java download link:
cat crashplan-install/install.defaults
Download:
wget --no-check-certificate http://download.code42.com/installs/proserver/jre/jre-7-linux-i586.tgz
Extract:
tar -xf jre-7-linux-i586.tgz
Install new version:
cd crashplan-install
cpio -idv < CrashPlan_4.7.0.cpi
cd ..
rm -r lib*
cp -r crashplan-install/lib* .

Check init script is still fixed and start crashplan:
nano /usr/pbi/crashplan-amd64/share/crashplan/bin/CrashPlanEngine
Start crashplan:
service crashplan start
Is it running?:
ps aux | grep java
Is it listening?:
sockstat -4
Stop crashplan plugin.

Upgrade to 4.8.0
Clean up old files:
rm CrashPlan_4.7.0_Linux.tgz
rm -r crashplan-install/

Get next version:
wget --no-check-certificate https://download.code42.com/installs/linux/install/CrashPlan/CrashPlan_4.8.0_Linux.tgz
Unpack:
tar -xf CrashPlan_4.8.0_Linux.tgz
Fix java(as per https://forums.freenas.org/index.php?threads/crashplan-update-failing-due-to-old-java-version.42300/)
Get java download link:
cat crashplan-install/install.defaults
Download:
wget --no-check-certificate http://download.code42.com/installs/proserver/jre/jre-linux-i586-1.8.0_72.tgz
Extract:
tar -xf jre-linux-i586-1.8.0_72.tgz
Install new version:
cd crashplan-install
cpio -idv < CrashPlan_4.8.0.cpi
cd ..
rm -r lib*
cp -r crashplan-install/lib* .

Check init script is still fixed:
nano /usr/pbi/crashplan-amd64/share/crashplan/bin/CrashPlanEngine


Finally:
Change JAVACOMMON in /usr/pbi/crashplan-amd64/share/crashplan/install.vars:
JAVACOMMON=/usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java
to:
JAVACOMMON=/usr/pbi/crashplan-amd64/share/crashplan/jre/bin/java
Start crashplan:
service crashplan start
Is it running?:
ps aux | grep java
Is it listening?:
sockstat -4

All done, try to connect with Windows client.

Note JAVACOMMON:
If you are getting version mismatch in usr/pbi/crashplan-amd64/share/crashplan/log/app.log then changing JAVACOMMON to the location of the updated JRE should fix your problem(assuming you have the correct JRE)
Note 4.7.0:
You may be able to skip 4.7.0 and jump straight to 4.8. I don't have any more time to experiment but I suspect it was JAVACOMMON that prevented me from doing so.

Thank you to all of the members of the Freenas forums, I hope pulling this stuff together helps someone. Apologies for the formatting.


Relevant:
https://forums.freenas.org/index.php?threads/crashplan-plugin.15366/
https://forums.freenas.org/index.php?threads/crashplan-not-updating.40374/#post-254182
https://forums.freenas.org/index.ph...home-computers-to-crashplan-on-freenas.39265/
https://forums.freenas.org/index.php?threads/crashplan-not-updating.40374/#post-254182
https://forums.freenas.org/index.php?threads/crashplan-not-updating.40374/page-2
https://forums.freenas.org/index.php?threads/crashplan-running-on-ubuntu-in-bhyve.45192/
https://forums.freenas.org/index.php?threads/crashplan-v4-8-not-updating-working.46548/#post-321272
 

Paul W.

Cadet
Joined
Dec 1, 2015
Messages
9
Hey Donkey, thanks for the post! I followed as best I could and struggled just a little bit. I'll add this to your process:

A trailing "/" is needed when redefining the JAVACOMMON path

I needed to edit the .ui_info files. on the server, set the IP to 0.0.0.0, and on the client set the IP to the jail IP.

Otherwise, this was an extraordinarily helpful resource.

I noted that even though I set the .ui_info file to read-only, upon restarting the plugin via the GUI, that file got replaced anyway.
 

Andrew076

Patron
Joined
Apr 5, 2015
Messages
206
Hello, I needed to build a fresh Crashplan jail to version 3.8 so I made a note of what worked for me. I am connecting to the headless crashplan via a windows client (https://forums.freenas.org/index.php?threads/crashplan-easier-way-to-connect-headless.23544/) and I do not want the overhead of Virtualbox. All of the following is inside the Crashplan jail.

I have a few questions:
You mention checking if it is runing
Is it running?:
ps aux | grep java

How do you know if it is running?

I get
root 33972 0.0 0.0 18832 2508 0 S+J 8:42PM 0:00.00 grep java

Then you ask Is it listening?:
sockstat -4

I get
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
root python2.7 5086 3 tcp4 192.168.1.2:12352 *:*
root syslogd 4769 7 udp4 *:514 *:*

I think there must be something missing. I decided to "start from scratch" and deleted the plugin and then started from scratch but I seem to recall that you need to connect with an old version of the Desktop Software first. Is this not correct?
 
Status
Not open for further replies.
Top