Crashplan Headless

You need to make an edit in crashplan/conf/ui.properties

Line 3 needs to be changed from

#servicePort=4243

to

servicePort=4200

changing the port number AND removing the initial #

Also - when you select your backup folders, you need to select the shares shown under "C", and ignore the top level list (which are actually links).

That has been updated.

#Fri Dec 09 09:50:22 CST 2005
#serviceHost=127.0.0.1
servicePort=4200
#pollerPeriod=1000  
# 1 second
#connectRetryDelay=10000
# 10 seconds
#connectRetryAttempts=3
#showWelcome=true

#font.small=
#font.default=
#font.title=
#font.message.header=
#font.message.body=
#font.tab=

In PuTTY, I am creating the tunnel using local port 4200 and mapping to localhost:4243
Still connects to the local windows install.

Jason

Odd. That is what I've done (following CrashPlan's instructions here: http://support.crashplan.com/doku.php/h ... ess_client) and it works fine. Under Destinations/computers I see the NAS first (labeled "this one") and my local machine second. I launch Putty first and login, then I launch the Crashplan desktop client. Did you try rebooting the PC?

Found a weird quirk. Luckily, I had made a backup copy of ui.properties before making any changes. I was using notepad to edit the file initially. I then went back to the backup file I created and opened it with wordpad, made the changes, and resaved as ui.properties.

Now, when trying to connect the desktop engine, I am getting a message that says, "unable to connect to the backup engine, retry?" - this is positive movement. Now, it is either the firewall blocking it, or an issue with the readynas install of Crashplan.

As my linux is not very good. Is there a quick check I can do to make sure the engine is running correctly on the ReadyNAS?

if you enter "ps -x" in the NAS command line you should see "/usr/bin/java -Dfile.encoding-UTF-8 -Dapp=CrashPlanSe" as one of the processes.

If putty is connected to the NAS, and local port 4200 is still forwarded to localhost:4243, and you are logged in as root, then you should be able to reach the backup engine.

The port forwarding is not persistent - it is convenient to save the session settings in putty, so you don't have to re-enter it.

I am still connected, I typed in ps -x and in the printout, "/usr/bin/java -Dfile.encoding=UTF-8 -Dapp=CrashPlanSerive...." is listed.
I still have an active PuTTY session with the port forwarding.

Still unable to connect.

Also, per http://support.crashplan.com/doku.php/recipe/stop_and_start_engine, specifically the following -

How It Works - Linux The start / stop script is stored in the crashplan/bin directory (default for a root install is: /usr/local/crashplan/bin). Usage: CrashPlanEngine stop|start

I am able to change to /usr/local/crashplan/bin but when I try to stop or start the service, I get "CrashPlanEngine: command not found" I tried this with "CrashPlanService also.

if ps -x shows it, then it is running. So there is no need to start or stop it. You could re-boot the NAS of course (though you would have to re-open the putty connection).

I guess it is possible that your windows firewall or security software is interfering with the port forwarding??? Though it seems strange, since they are not interfering with the command line window. Did you try disabling them?

I'll try rebooting everything tonight. Users are accessing info on the NAS all the time, so I don't want to take that down right now. Thanks for the help so far. Hopefully a reboot does it. If not, I will try disabling the firewall...after hours.

I have rebooted everything. Turned off the windows firewall. No firewall on NAS.
I am able to establish the ssh connection to the NAS with tunnel 4200 -> 4243
With this established, I am unable to telnet <nas IP> 4200 -> I get a "could not open connection to the host" message
Telnet <nas IP> just sits at a flashing cursor

I ran netstat --listen on the NAS and 4243 does not show up.
*:4242 shows up (I believe this is the server service port)

netstat -an | grep LISTEN | grep 42 shows ->
tcp 0 0 0.0.0.0:4242 0.0.0.0:* LISTEN
tcp 0 0 <nas ip>:4243 0.0.0.0:* LISTEN

Any other ideas? Still can't get desktop service to connect to the ReadyNAS

telnet to the NAS doesn't work for me either, but I connect ok to Crashplan without it. I am not sure if something is off in the Crashplan instructions, or if it is something on the NAS.

netstat -an | grep LISTEN | grep 42 on my setup is close to yours but not identical:
tcp 0 0 0.0.0.0:4242 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:4243 0.0.0.0:* LISTEN

You can open a CrashPlan support case (though their support is a bit overwhelmed at the moment, so don't expect an immediate reply).

You could also look in /usr/local/crashplan/log, and try to sort what is happening from the log files.

BTW, Crashplan recently updated their product to 3.2. My initial install was the older 3.0.3 - it appears to have auto-updated (both on the NAS and Windows), though I am wondering if your issue is unique to new headless installs on 3.2. If you raise a support case with them, you might note that possibility.