Crashplan tunnel not working

Status
Not open for further replies.

alexthefourth

Dabbler
Joined
Sep 3, 2013
Messages
28
After several hours of tinkering with the crashplan plugin I finally got it to stay on. Now my problem seems to be that the tunnel between my pc and the crashplan jail is not being made. I would like to know how i can verify that?

I can ssh into the jail, i have changed the ui file to change the port on my pc to 4200.

One problem i have is that i cannot check the top of sockstat -4 to see this line:
[root@freenas] ~# jexec crashplan_1 sockstat -4
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
crashplan sshd 4149 5 tcp4 192.168.1.103:22 192.168.1.83:53226
root sshd 4147 5 tcp4 192.168.1.103:22 192.168.1.83:53226
root java 3952 56 tcp4 127.0.0.1:4243 *:*
root java 3952 57 tcp4 *:4242 *:*
root java 3951 56 tcp4 127.0.0.1:4243 *:*
...

when i run sockstat -4 it runs and goes to the bottom so i cannot see the first line. is there a way to view the top line of sockstat -4?
 

fracai

Guru
Joined
Aug 22, 2012
Messages
1,212
You can pipe the result through "less".
As in:
Code:
jexec crashplan_1 sockstat -4 | less

Use the arrow keys to scroll up or down and press 'q' when you're done.
 

alexthefourth

Dabbler
Joined
Sep 3, 2013
Messages
28
thank you

so when i run that I do not see this line
crashplan sshd 4149 5 tcp4 192.168.1.103:22 192.168.1.83:53226

but if i run cpuset -l 0 /usr/local/share/crashplan/bin/CrashPlanEngine status it shows that it is running.

im not sure how to troubleshoot this or how to start sshd under the crashplan user.
 

qwerion

Dabbler
Joined
Jan 30, 2014
Messages
19
Use a different port than 4200. That one no longer works for some reason. Using 42000 personally.

If you care to check, the ui.log of the crashplan client has the error message:
Code:
invalid core port specified! - 4200 defaulting to 4243 
 
Last edited:
Status
Not open for further replies.
Top