SOLVED Crashplan NOT updating?

[Andrew076]

I have a basic question, is it the consensus that crashplan will no longer update from 3.6.3 on the FreeNAS server side? I ask because I had to delete and reinstall the plugin a few days ago (it ended up being something else entirely so that was a mistake!) Anyway before deleting, the FreeNAS side had updated to 4.5.2 and my windows GUI was at 4.5.

I have reinstalled everything and everything is working, i.e. crashplan is backing up to the Code42 servers, and my windows GUI connects to FreeNAS.

However, when I did this before, after installing bash and connecting the FreeNAS server and the Windows GUI, they both started updating. This is not happening and both the FreeNAS side and windows side is at version 3.6.3 which will be fine so long as Code42 continues to support older versions of Crashplan. It does make me nervous though as I generally want to keep everything up to date.

I am using Crashplan in a FreeNAS jail.

 

[RoboKaren]

In the past, the CrashPlan server in a FreeNAS jail would automatically update itself (which was problematic in its own right). However, when they released 4.5.x of the CrashPlan server code, Code42 put in some linux kernel version checks in the upgrade code that FreeBSD/FreeNAS doesn't pass, so there's no longer auto-updating from 3.63 to 4.x.

You have to do it manually using the instructions given earlier in this thread by mastax. So if you want the most recent version:

1. Install CrashPlan 3.6.3 using the jail template
2. Using mastax's instructions in post #5 of this thread, update to 4.x
3. After you're at server version 4.x, configure your CrashPlan server using the matching version of the client on your PC/MAC.

I don't know if the CP-server will continue to upgrade itself once it's at 4.x, so you might want to just make sure that it's at the same version number as your client (the GUI app on your PC).

 

[Andrew076]

In the past, it would update. However, when they released 4.5.x, Code42 put in some linux kernel version checks that FreeBSD/FreeNAS doesn't pass, so there's no longer auto-updating from 3.6.3 to 4.x. You have to do it manually using the instructions given earlier in this thread by mastax.

But those instructions were for Linux right? I thought FreeNAS was different from Linux. Will those instructions still work for FreeBSD?

 

[RoboKaren]

But those instructions were for Linux right? I thought FreeNAS was different from Linux. Will those instructions still work for FreeBSD?

To be clear, I mean his instructions on post #5 of this thread (your post was post #23). Yes, those are the FreeNAS (FreeBSD) instructions and should work for you. I tried it out and it seemed to work although I'm going to keep on using VirtualBox as I prefer having the GUI on the same machine.

 

[Andrew076]

To be clear, I mean his instructions on post #5 of this thread (your post was post #23). Yes, those are the FreeNAS (FreeBSD) instructions and should work for you. I tried it out and it seemed to work although I'm going to keep on using VirtualBox as I prefer having the GUI on the same machine.

Worked perfectly! Thank you I wasn't sure if that would mess things up or not!

 

[RoboKaren]

@mastax - I think you should make your post #5 a separate post - and ask for a sticky from a mod.

 

[BankZ]

I followed these directions but I get the version printed twice when I do this:

root@crashplan_1:/ # cat /var/log/crashplan/engine_* | grep CPVER
[02.02.16 06:59:33.936 INFO main com.backup42.service.CPService] CPVERSION = 4.5.0 - 1435726800450 (2015-07-01T05:00:00:450+0000) - Build: 270
[02.02.16 06:59:36.004 INFO main com.backup42.service.CPService] CPVERSION = 4.5.0 - 1435726800450 (2015-07-01T05:00:00:450+0000) - Build: 270


This is different than older versions. Is this to be expected?

 

[nidur]

Yeah so it was time for my annual CrashPlan update battle.

Thanks to @mastax instruction to upgrade, the process was very easy. Plugin updated to CPVERSION = 4.5.0

The "/usr/pbi/crashplan-amd64/share/crashplan/bin/run.conf" did not change (SRV_JAVA_OPTS & GUI_JAVA_OPTS)

My "/usr/pbi/crashplan-amd64/share/crashplan/conf/my.service.xml" did not change

The only thing i needed to do was to restart the jail and get the authentication token again from
"\var\lib\crashplan\.ui_info"

And my client is running 4.5.2 and connecting normally.

 

[Andrew076]

So I have a general question, for those of you who have the Plugin updated to CPVERSION = 4.5.0, and
the Client running 4.5.2 when you click on the History in the GUI, is it updating? Mine has not updated since January 26 when I did the upgrade. It is working just isn't providing the information historical information.

 

[Reece Johnson]

So I have a general question, for those of you who have the Plugin updated to CPVERSION = 4.5.0, and
the Client running 4.5.2 when you click on the History in the GUI, is it updating? Mine has not updated since January 26 when I did the upgrade. It is working just isn't providing the information historical information.

Copy the following files from the Crashplan 4.5.0 conf/ directory to
/usr/pbi/crashplan-amd64/share/crashplan/conf/

default.service.xml
service.log.xml
ui.log.xml
upgradeui.log.xml

Then restart the Crashplan service.

 

[Andrew076]

Copy the following files from the Crashplan 4.5.0 conf/ directory to
/usr/pbi/crashplan-amd64/share/crashplan/conf/

default.service.xml
service.log.xml
ui.log.xml
upgradeui.log.xml

Then restart the Crashplan service.

So I am fairly new to Freenas how exactly do you copy files from one directory to an other?

 

[RoboKaren]

@mastax - any chance you could write a new post with updated instructions (Linux CP is now at 4.5.2) and put it somewhere we can make it a sticky?

 

[inpowers]

Hi Guys

When I stop crashplan I get a message
/usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Can someone please tell me what it means especialy the NO SHEBANG LINE IN part.

Thanks

 

[Todd Hayward]

and for clarification (for noobs like me), the "CrashPlan 4.5.2 conf" folder is actually:
/usr/pbi/crashplan-amd64/share/crashplan/crashplan-install/conf (the conf folder of the update package that was unpacked by the tar command).

so to copy the files, use this command from the /usr/pbi/crashplan-amd64/share/crashplan/conf folder:

service crashplan stop
cp -f ../crashplan-install/conf/* . #(the space is intentional, the # is a comment, so do not type what comes after it)
service crashplan start

 

[t3hG04T]

As I've run (as many others here) into a "cannot connect to my CP anymore" problem recently, being able to download only version 4.7.0 of the GUI, I compiled my own quick "not-to-fotget" set of instructions for setting it up.

It's heavily based on the fantastic mastax's writeup, kudos to you friend!

Apparently I was able to force CrashPlan on FreeNAS to update to 4.7.0 and connect to it via GUI client 4.7.0. I revised my settings and everything is merrily backing up away ^^. No more ,"your PC is not backed up!" emails from CP!

It's all here on GitHub to allow for easy editing/forking/etc if anyone is interested: https://github.com/t3hG04T/freenas-crashplan_update

[Fantastic mastax's post.]

 

[Slovak]

And just in time to spur more upgrade issues, Crashplan 4.8 is released: https://support.code42.com/Release_Notes/CrashPlan_For_Home/4.8

 

[willn]

Yes, I am trying to fix my Crashplan now. 4.8 has broken my setup.

 

[nicofranceusa]

I am really at lost. I've spent the last two days trying to figure this out. I've attempted a fresh install of v4.8 which btw requires a new JVM v1.8 which seems to be the biggest problem. I've tried using the packaged linux Sun JRE v1.8 as well as OpenJDK v1.8 no of which are working yet. I'm getting a lot of shared library issues.

Now my local Desktop Crashplan has now been updated to v4.8 as well so I can't even connect to a clean install of Crashplan server v4.7...

I hope some smart folks out there are going to be able to figure out some work around.

Crashplan v4.7 will no longer be supported as of October 17th: https://support.code42.com/Terms_An...ome_And_CrashPlan_PRO_Software_Version_Policy

 

[RoboKaren]

I ended up giving up on Crashplan-in-a-jail and instead upgraded to 9.10 and put Crashplan into an Ubuntu VM using byhyve. Was fairly easy: Create a byhyve VM, install Ubuntu, create a VNC connection to get to the GUI, then install Crashplan; share the folders from FreeNas to Ubuntu with a CIFS share (since byhyve doesn't support shared folders); and voila.

 

[Andrew076]

I ended up giving up on Crashplan-in-a-jail and instead upgraded to 9.10 and put Crashplan into an Ubuntu VM using byhyve. Was fairly easy: Create a byhyve VM, install Ubuntu, create a VNC connection to get to the GUI, then install Crashplan; share the folders from FreeNas to Ubuntu with a CIFS share (since byhyve doesn't support shared folders); and voila.

How do you do this exactly? Is the VM run on the freenas server? Where is this byhyve program?