Crashplan 4.4.1 and Freenas 9.3

[Chris Dill]

I have scoured and scoured and tried different posts, different methods, etc, and none of them have worked.

I followed this guide to the letter: https://forums.freenas.org/index.php?threads/crashplan-on-freenas-9-3.26487/

Then after I tried to do it without SSH port forwarding and a tunnel, instead connecting right to my jail IP. Neither of these guides work because the new plugin and FreeNAS are different- for instance those java options are already fixed in the latest version.

Then I followed this guide: https://forums.freenas.org/index.ph...ashplan-4-4-1-on-older-freenas-9-2-1-7.38681/

And again, no dice (I followed both the OP and the comment at the end).

If anyone is bored with all the family in town this weekend, would you mind putting together a step by step for getting Crashplan headless on FreeNas 9.3 with the latest plugin version, and connecting to it from Windows using the latest Crashplan desktop version 4.4.1? I would be GREATLY in your debt!

I cannot post any logs for troubleshooting purposes, because I was never able to actually get it to connect... it actually connected, but under file locations the only thing there was my local PC C: and D:. Also. .ui_info doesnt exist on my PC with the new desktop version, though I do have some comparable files in two directories: C:\ProgramData\CrashPlan and C:\Program Files (x86)\CrashPlan.

 

[jadz]

My crashplan on freenas has recently upgraded to 4.5 which seems to have broken things again - I wonder if that is related to your troubles?

Code:

cat /usr/pbi/crashplan-amd64/share/crashplan/log/history.log.0 | grep start
I 11/22/15 05:49PM CrashPlan started, version 4.4.1, GUID 622846634348197249
I 11/23/15 03:14PM CrashPlan started, version 4.5.0, GUID 622846634348197249

 

[mchias]

My box updated to 4.5 as well a few days ago so you aren't the only one.

One thing I noticed although it may have existed earlier is that 127.0.0.1 is injected into the .ui_info file in lieu of the 0.0.0.0. It used to be port,key,0.0.0.0. I stopped the service on the NAS, edited it to say 0.0.0.0 in vi, and restarted the service. However, the file flipped back to 127.0.0.1.

I wish they would make a client for us already. Hopefully the wizards of smart can figure out a way around in the meantime.

My crashplan on freenas has recently upgraded to 4.5 which seems to have broken things again - I wonder if that is related to your troubles?

Code:

cat /usr/pbi/crashplan-amd64/share/crashplan/log/history.log.0 | grep start
I 11/22/15 05:49PM CrashPlan started, version 4.4.1, GUID 622846634348197249
I 11/23/15 03:14PM CrashPlan started, version 4.5.0, GUID 622846634348197249

 

[Janne]

Hi,

My Crashplan also did the update to 4.5.0. The fun part is that there is no 4.5.0 version of desktop app available, so I guess that the connection problems are related to the outdated desktop version. As far as I know, the versions of FreeNAS and Desktop Crashplan clients need to match in order to be able to connect. Everything worked fine with 4.4.1 and now I can't connect anymore. Fun, fun, fun.

 

[jadz]

My 4.5 instance isn't even starting and I don't see anything in the CrashPlan logs. Can you confirm that your 4.5 is actually running?

 

[mchias]

I can start the service in the jail via the "service crashplan start" command but when I run the "service crashplan status" command it says it is not running. But if I go to start it again I get a message saying it is already running.

I am going to go through the logs to see if there is anything.

The log file shows the 4.5 service started and nothing more.

 

[jadz]

Do you have java processes running after running the "service crashplan start" (I don't)?

Code:

root@crashplan_2:~ # ps aux

Anything listening on relevant ports (I don't)?

Code:

root@crashplan_2:~ # sockstat -4

Do you have something recent in the service.log.0 (nothing recent in mine)?

Code:

root@crashplan_2:~ #  tail /usr/pbi/crashplan-amd64/share/crashplan/log/service.log.0

 

[mchias]

Do you have java processes running after running the "service crashplan start" (I don't)?

Code:

root@crashplan_2:~ # ps aux

I have a handful of processes running.

Code:

[root@crashplan_1 /]# ps aux | more
USER   PID %CPU %MEM     VSZ   RSS TT  STAT STARTED    TIME COMMAND
root 29706 26.4  0.9 1716812 72952  0  SNJ   9:13PM 0:03.53 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java
root 29721 13.1  0.9 1716812 72952  0  SNJ   9:13PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java
root 29722 13.1  0.9 1716812 72952  0  SNJ   9:13PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java
root 29720 11.9  0.9 1716812 72952  0  SNJ   9:13PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java
root 29719 11.8  0.9 1716812 72952  0  SNJ   9:13PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java
root 29718 11.7  0.9 1716812 72952  0  SNJ   9:13PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java
root 29707  7.1  0.9 1716812 72952  0  SNJ   9:13PM 0:00.84 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java
root 29714  6.8  0.9 1716812 72952  0  SNJ   9:13PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java
root 29711  1.6  0.9 1716812 72952  0  SNJ   9:13PM 0:00.22 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java
root 29709  0.7  0.9 1716812 72952  0  SNJ   9:13PM 0:00.11 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java
root 29708  0.4  0.9 1716812 72952  0  SNJ   9:13PM 0:00.07 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java
root 29710  0.1  0.9 1716812 72952  0  SNJ   9:13PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java
root 29712  0.1  0.9 1716812 72952  0  SNJ   9:13PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java

Anything listening on relevant ports (I don't)?

Code:

root@crashplan_2:~ # sockstat -4

Again, it looks like it is listening.

Do you have something recent in the service.log.0 (nothing recent in mine)?

Code:

root@crashplan_2:~ #  tail /usr/pbi/crashplan-amd64/share/crashplan/log/service.log.0

Yep, something here as well.

Code:

[root@crashplan_1 /]# tail /usr/pbi/crash*/share/cras*/log/service.log.0 | more
[11.30.15 21:13:08.028 INFO  main           com.backup42.service.CPService] *************************************************************
[11.30.15 21:14:07.212 INFO  ystemWatcher p42.service.peer.CPCConnectCheck] Connect to CPC after 0ms
[11.30.15 21:14:07.316 INFO  ystemWatcher up42.service.peer.PeerController] Attempting to connect to CPC. delay=60000
[11.30.15 21:14:08.580 INFO  MQ-Peer-0    saging.security.SecurityProvider] SP:: Session secured in 382 ms. Session[id=718387046552424933, closed=false, isAcceptor=false, remoteIdentity=ENDPOINT, completedAuth=false, lat=2015-11-30T21:14:08:580, lrt=2015-11-30T21:14:08:580, lwt=2015-11-30T21:14:08:313, #pending=0, enqueued=true, local=192.168.1.4:54910, remote=216.17.8.3:443, usingProtoHeaders=true, usingEncryptedHeaders=true, WAN]
[11.30.15 21:14:08.862 INFO  MQ-Peer-1    .code42.messaging.peer.PeerLayer] PeerLayer: session authenticated RemotePeer-[guid=42, server=true, state=CONNECTED, mode=PRIVATE, location=central.crashplan.com:443, public=na, transportPbK=null, transportPbKRequestable=true, connecting=2015-11-30T21:14:07:271, connected=2015-11-30T21:14:08:862, attempts=0, connectActivity=2015-11-30T21:14:08:862, keepAliveSent=0, minRetry=0, retryDelay=0, reflector=reflector.crashplan.com:443, #nat=0, session=Session[id=718387046552424933, closed=false, isAcceptor=false, remoteIdentity=ENDPOINT, completedAuth=true, lat=2015-11-30T21:14:08:861, lrt=2015-11-30T21:14:08:861, lwt=2015-11-30T21:14:08:585, #pending=0, enqueued=true, local=192.168.1.4:54910, remote=216.17.8.3:443, usingProtoHeaders=true, usingEncryptedHeaders=true, WAN]]
[11.30.15 21:14:08.953 INFO  MQ-Peer-2    ervice.peer.PeerVersionValidator] WE have an old version, localVersion=1435726800450 (2015-07-01T05:00:00:450+0000), remoteVersion=1440997200510 (2015-08-31T05:00:00:510+0000), remoteGuid=42
[11.30.15 21:14:09.040 INFO  ystemWatcher up42.service.peer.PeerController]   Connected to CPC after 1sec
[11.30.15 21:15:09.041 INFO  ystemWatcher ervice.peer.CPCAutoRegisterRetry] Remove AutoRegister retry system check, no longer needed.
[11.30.15 21:16:09.042 INFO  ystemWatcher p42.service.peer.CPCConnectCheck] Disconnect from CPC after 1min 0sec
[11.30.15 21:16:09.042 INFO  ystemWatcher up42.service.peer.PeerController] DISCONNECT and REMOVE CPC

 

[Janne]

Code:

root      35840  0.0  1.2 1216816 98880  1- INJ  Sun10PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35841  0.0  1.2 1216816 98880  1- INJ  Sun10PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35842  0.0  1.2 1216816 98880  1- INJ  Sun10PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35843  0.0  1.2 1216816 98880  1- INJ  Sun10PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35844  0.0  1.2 1216816 98880  1- INJ  Sun10PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35845  0.0  1.2 1216816 98880  1- SNJ  Sun10PM 0:01.36 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35846  0.0  1.2 1216816 98880  1- INJ  Sun10PM 0:00.11 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35847  0.0  1.2 1216816 98880  1- INJ  Sun10PM 3:17.85 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35848  0.0  1.2 1216816 98880  1- INJ  Sun10PM 0:00.05 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35849  0.0  1.2 1216816 98880  1- INJ  Sun10PM 0:00.01 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35850  0.0  1.2 1216816 98880  1- INJ  Sun10PM 0:00.03 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35851  0.0  1.2 1216816 98880  1- INJ  Sun10PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35852  0.0  1.2 1216816 98880  1- INJ  Sun10PM 0:00.01 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35853  0.0  1.2 1216816 98880  1- INJ  Sun10PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35854  0.0  1.2 1216816 98880  1- SNJ  Sun10PM 0:02.20 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35855  0.0  1.2 1216816 98880  1- INJ  Sun10PM 0:00.03 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35856  0.0  1.2 1216816 98880  1- INJ  Sun10PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35858  0.0  1.2 1216816 98880  1- INJ  Sun10PM 0:00.00 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco
root      35859  0.0  1.2 1216816 98880  1- INJ  Sun10PM 0:00.01 /usr/pbi/crashplan-amd64/linux-sun-jre1.7.0/bin/java -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.enco

I have processes up'n'running as well, listening to ports and stuff. I'm just not able to connect to Freenas Crashplan from the desktop. Weird stuff.

Code:

debug1: Connection to port 4200 forwarding to 127.0.0.1 port 4243 requested.
debug2: fd 7 setting TCP_NODELAY
debug1: channel 2: new [direct-tcpip]
channel 2: open failed: connect failed: Connection refused
debug2: channel 2: zombie
debug2: channel 2: garbage collecting
debug1: channel 2: free: direct-tcpip: listening port 4200 for 127.0.0.1 port 4243, connect from 127.0.0.1 port 64299, nchannels 3
debug1: Connection to port 4200 forwarding to 127.0.0.1 port 4243 requested.
debug2: fd 7 setting TCP_NODELAY
debug1: channel 2: new [direct-tcpip]
channel 2: open failed: connect failed: Connection refused
debug2: channel 2: zombie
debug2: channel 2: garbage collecting
debug1: channel 2: free: direct-tcpip: listening port 4200 for 127.0.0.1 port 4243, connect from 127.0.0.1 port 64300, nchannels 3

 

[predv2]

I was in the process of re-building my Freenas box so I had not got around to this until now. I received the below email from Code42 and thought nothing of it until I noticed I was not able to get ChrashPlan to start. I am thinking this is the issue.


---------------------------------------------------

Hello,

We're contacting you to let you know about some changes made to the newest version of CrashPlan that may affect the CrashPlan app on one of your devices. Starting with the release ofCrashPlan version 4.5.0, the System Requirements with regards to Linux have changed. Here are the system requirements that have changed:

Linux kernel version:

• CrashPlan app version 4.5.x or later: 2.6.27 or newer and glibc 2.9+
• CrashPlan app version 4.4.1 or earlier: 2.6.13 or newer and glibc 2.4+

If you have a Linux device running kernel 2.6.26 or older and are still on CrashPlan version 4.4.1, CrashPlan on this device will not upgrade to version 4.5.0. If your device is on kernel 2.6.26 or older and has already upgraded to CrashPlan version 4.5.0, CrashPlan has likely stopped working.

To continue using up-to-date versions of CrashPlan, we recommend upgrading your operating system to a supported version of the Linux kernel. For instructions on upgrading your Linux device, refer to the documentation for your device or your Linux distribution.

An alternate solution to resolve this is to Uninstall CrashPlan 4.5.0, and install CrashPlan version 4.4.1, which can be found in this direct link:

• https://download.crashplan.com/installs/linux/install/CrashPlan/CrashPlan_4.4.1_Linux.tgz

Please Note: Computer-to-computer backups require both devices be on the same version of the CrashPlan app.

We've created a Support Article that explains more about this change, here:

• https://support.code42.com/CrashPla...inux_CrashPlan_App_Version_4.5_Cannot_Back_Up

Please let us know if you have any further questions.

Thank you,
Code42 Customer Champion Team