Crashplan on freenas 9.3?

[Brock388]

Ive been looking for literally days for a guide to install crashplan on freenas 9.3 but I cant find anything.. Does anyone have anything that can help?

 

[danb35]

I installed it yesterday, so I'm far from an expert. My main resources were this article, this article, and this video (including the second part). Here are at least the rough steps I followed:

• Install the crashplan plugin through the web GUI
• In the left-hand frame of the FreeNAS web GUI, expand Plugins, then click on Crashplan. Scroll down to accept the Java EULA.
• Add storage to the crashplan jail for whatever on your server you want to back up to crashplan. Add each dataset separately under /mnt/ in the jail, and make sure the "read only" and "create directory" checkboxes are checked. For example, if you have a dataset called "documents" that you want to back up, the source would be /mnt/pool/documents, and the destination would be /mnt/documents.
• SSH to your FreeNAS server as root
• Run "jls" to list your jails. Note the JID (number) of the crashplan jail
• Run "jexec (JID of the crashplan jail) csh". For example, if the JID is 3, run "jexec 3 csh"
• Run "echo crashplan_enable=\"YES\" >> /etc/rc.conf"
• Run "service crashplan start" and see if it starts without errors
• Run "sockstat -l" and see that you have a lot of java processes listening on port 4243.
• Run "service crashplan stop"
• Run "ee /usr/pbi/crashplan-amd64/share/crashplan/conf/my.service.xml"
• Scroll down to find the line that says "<serviceHost>127.0.0.1</serviceHost>". Change 127.0.0.1 to 0.0.0.0
• Hit Esc to bring up the menu, a to leave the editor, and save the file.
• service crashplan start
• sockstat -l -- the java processes should now be listening on *:4243
• Install the crashplan client on your desktop machine
• Edit the ui.properties file (see here for location) to uncomment the serviceHost line, and to change the IP address to the address of your crashplan jail

Now, when you run the crashplan client, it will control the crashplan installation on your FreeNAS server. I have it running, backing up a dataset on my FreeNAS server to Crashplan central. Still not sure about how to set up backing up my desktop machine to my FreeNAS server.

 

[danb35]

Was that helpful, did it not work, ... ?

 

[jakeandchase]

if you're backing up your PCs to your NAS, just use the easier method and backup to a CIFs share. no plugin required on the NAS

 

[depasseg]

if you're backing up your PCs to your NAS, just use the easier method and backup to a CIFs share. no plugin required on the NAS

Crashplan doesn't support NAS backups (there are some kludgy workarounds).

 

[SweetAndLow]

Crashplan doesn't support NAS backups (there are some kludgy workarounds).

They don't support nas backups in relation to snyology or some of the other pre made units. There is a port of crash plan for freebsd which works great. My vote is to keep asking them to officially support freenas and maybe one day they will have a supported plugin for easy install. The current plugin is just maintained by the community.

 

[depasseg]

I meant CP doesn't support backing up to a CIFS share.

I understand that the OP is looking to install CP on FreeNAS. It's on my to-do list as well.

 

[danb35]

@depasseg, what are you looking to do that the existing plugin doesn't accomplish? I'm still very new to playing with crashplan, but (when it works) it seems to do the job of backing up what I want from the FreeNAS box. Of course, it's entirely possible I'm using it wrong.

 

[depasseg]

I meant, install the plugin. And then migrate all my other machines to backup to the FreeNAS instead of the ReadyNAS. I've heard some issues updating the plugin, which is why installing CP from scratch sounded interesting, but I'm not sure it's worth the trouble.

 

[xcom]

I meant, install the plugin. :) And then migrate all my other machines to backup to the FreeNAS instead of the ReadyNAS. I've heard some issues updating the plugin, which is why installing CP from scratch sounded interesting, but I'm not sure it's worth the trouble.

No issues here.
All works fine and as expected.
I have 6 systems backing up to it and works flawlessly.

 

[Rilo Ravestein]

• Run "echo crashplan_enable=\"YES\" >> /etc/rc.conf"
• Run "sockstat -l" and see that you have a lot of java processes listening on port 4243.
  
• Run "ee /usr/pbi/crashplan-amd64/share/crashplan/conf/my.service.xml"
• Scroll down to find the line that says "<serviceHost>127.0.0.1</serviceHost>". Change 127.0.0.1 to 0.0.0.0
• sockstat -l -- the java processes should now be listening on *:4243

Could you please explain why you did the above steps (bold)?
- Doesn't the plugin start the service automatically? If not, i think this should be reported as a bug i think.
- Why the changes on serviceHost?
Thanks!

 

[fracai]

The service host stuff is so crashplan is listening on all interfaces instead of just locally. Normally, you run the service and gui on the same machine. With freenas you're running a headless service and will run the gui on a different machine. You can either change the listening interface or set up an ssh tunnel before you start the gui. These instructions are for the interface change.

The first but is to enable the crashplan service when the jail starts up. I would have thought this is already done.

 

[danb35]

Could you please explain why you did the above steps (bold)?
- Doesn't the plugin start the service automatically? If not, i think this should be reported as a bug i think.

No, the plugin doesn't start the service automatically. Bug 7564 created.

- Why the changes on serviceHost?

Because by default, the crashplan service only listens on localhost, i.e., the crashplan jail itself, for the client to connect. Since it's running headless, the client will be running on another computer, and thus the service will need to listen on another interface. You could, instead, set it to the jail's IP address, but setting it to 0.0.0.0 has it listen on any interface available to the jail. I'm not sure if this is a bug too, though I'm inclined to think it is.

 

[Rilo Ravestein]

Thanks for the info!

I'm not sure if this is a bug too, though I'm inclined to think it is.

I would think so too.

Would these manual changes survive a plugin update?

 

[danb35]

Turns out the missing crashplan_enable is operator error--if you enable the plugin from the plugins -> installed page, that line will be added to /etc/rc.conf. I hadn't been aware that newly-installed plugins aren't enabled by default. PEBCAK.

 

[Tom_]

The instructions provided by @danb35 worked for me. Might be worth adding, starting from a fresh jail on FreeNAS 9.3 I had couldn't start the crashplan service until I edited /usr/pbi/crashplan-amd64/share/crashplan/bin/run.conf file using the instructions here.

 

[ClayM]

Is anybody else getting this error?

root@crashplan_1:/var/log/crashplan # cat engine_error.log
/etc/host.conf: line 2: bad command `hosts'
/etc/host.conf: line 3: bad command `dns'

I got it on a new install, and after making the rc.conf changes on a working install that was broken after an update.

 

[JaimieV]

/Edit: I missed this thread which I'm now going to work through...

/Edit2: So I had to do the run.conf edit three or four times, and that was the trick. Hey ho! I'll note that down for next time.

Original post:

I did have a CrashPlan plugin working fine for several months after doing the edit to the Java opts detailed as per Tom_'s post above.

About two months ago it stopped working, and I've just now had time to look into it. I'm currently thinking that Crashplan have updated it again, and there needs to be a new tweak in addition to the one already made. So if you have Crashplan running okay right now, *don't* connect to it with your client app or you'll get updated to one that doesn't work! Probably.

So after a bit of fiddling and getting nowhere I did a delete and reinstall of the plugin, then the run.conf edit, and it fired up - but on connecting to it with the tweaked local CrashPlan app the first thing it did was update to v3.7.0 - and now it doesn't launch at all. "Crashplan data did not validate, configure it first." is the error at the top of the Plugins page when I try to turn it on.

In the jail, I get this a few moments after starting the service:

root@crashplan_1:/var/log/crashplan # cat engine_output.log
Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location - find_vma failed
[02.27.15 15:58:09.977 INFO main root ] Locale changed to English
[02.27.15 15:58:09.979 INFO main root ] *************************************************************
[02.27.15 15:58:09.979 INFO main root ] *************************************************************
[02.27.15 15:58:09.979 INFO main root ] STARTED CrashPlanService
[02.27.15 15:58:09.982 INFO main root ] CPVERSION = 3.7.0 - 1388728800370 (2014-01-03T06:00:00:370+0000)
[02.27.15 15:58:09.982 INFO main root ] LOCALE = English
[02.27.15 15:58:09.984 INFO main root ] ARGS = [ ]
[02.27.15 15:58:09.984 INFO main root ] *************************************************************
[02.27.15 15:58:10.228 INFO main root ] Adding shutdown hook.
[02.27.15 15:58:10.242 INFO main root ] BEGIN Loading Configuration
[02.27.15 15:58:10.334 INFO main root ] BEGIN Copy Custom
[02.27.15 15:58:10.334 INFO main root ] Directories: [.Custom, custom, /usr/pbi/crashplan-amd64/share/crashplan/conf/.Custom, /usr/pbi/crashplan-amd64/share/crashplan/conf/custom]
[02.27.15 15:58:10.335 INFO main root ] NOT waiting for custom skin to appear
[02.27.15 15:58:10.335 INFO main root ] NO customizations found.
[02.27.15 15:58:10.335 INFO main root ] END Copy Custom
[02.27.15 15:58:10.344 INFO main root ] Loading from default: /usr/pbi/crashplan-amd64/share/crashplan/conf/default.service.xml
[02.27.15 15:58:10.538 INFO main root ] Loading from my xml file=conf/my.service.xml
[02.27.15 15:58:10.652 INFO main root ] Loading ServiceConfig, newInstall=false, version=6, configDateMs=null, installVersion=1388556100363
[02.27.15 15:58:10.653 INFO main root ] OS = Linux
[02.27.15 15:58:11.071 INFO main root ] AuthorityLocation@32730961[ location=central.crashplan.com:443, hideAddress=false ]
[02.27.15 15:58:11.073 INFO main root ] Checking Java memory heap max.
[02.27.15 15:58:11.077 INFO main root ] Previous Java memory max heap size was 1024
[02.27.15 15:58:11.082 INFO main root ] END Loading Configuration
[02.27.15 15:58:11.171 INFO Thread-0 root ] Stopping service...
[02.27.15 15:58:11.185 INFO Thread-0 root ] SystemWatcher stopped.
[02.27.15 15:58:11.186 INFO Thread-0 root ] Service stopped
jtux Loaded.
Exiting!!! java.lang.RuntimeException: Unexpected IO Exception constructing selector engine - e=java.io.IOException: Function not implemented
[02.27.15 15:58:12.580 INFO main root ] ***** STOPPING *****

and then the log wipes itself down to
root@crashplan_1:/var/log/crashplan # cat engine_output.log
Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location - find_vma failed

Doesn't look useful, really. Anyone who's a better Java diagnoser than I am able to create a workaround?

 

[SweetAndLow]

Crash plan has always worked perfectly for me I just had to update the java startup flags 2x so far. This fix was made in freshports but there hasn't been a new plugin made.

 

[sremick]

Crash plan has always worked perfectly for me I just had to update the java startup flags 2x so far. This fix was made in freshports but there hasn't been a new plugin made.

Might there be benefit then to installing Crashplan manually in a jail versus using the plugin? That's the same route I took with Plex but wasn't necessarily going to with Crashplan. Maybe I should, but wasn't sure if anyone else was doing it this way.

And would it be safe to install it into the same jail as my Plex server, or should I keep them separate?