Crashplan for Dummies, aka Step by Step :)

Not sure what the problem was, but I uninstalled everything and started again and this time it works.  I must have missed something last night.

I was having very similar problems. Just copying the .ui_info file from the remote (ReadyNas) to my local machine (Windows 10) didn't quite work. You still have to change the port number from 4243 to 4200. 

It's step 2.2.4 from:

https://support.code42.com/CrashPlan/4/Configuring/Using_CrashPlan_On_A_Headless_Computer#Alternative_Port_Forwarding_Options

That was the step I missed...

Hi,

This is one of those things that you set up once and then you forget about! But I kind of remember that changing the configuration file was still a required step in setting up the client, am I mistaken?

---

tony359 wrote:

Hi,

 

This is one of those things that you set up once and then you forget about! But I kind of remember that changing the configuration file was still a required step in setting up the client, am I mistaken?

---

If you are talking about ui_info, then yes.

But as derejy42 says, copying the file from the NAS to the client PC won't work if the port number is being tunneled.  

Ok

Change of port number is mentioned in the guide though, just before the ui.info step.

I'm just wondering if there is anything missing from the list.

Hi Tony. I only recently saw your update on how to install 4.3.0 on page 23 of this thread. Wish I would have seen the post before banging my head against this for a few hours last night! I wonder if it would be worth having the info in a new thread because google search leads to the first message in this very long thread, and it's not easy to find the updated info on page 23.

Anyhow, you had some green questions on your post. This is what I found while working through the steps (for Crashplan 4.4.1):

I had to install java separately following the instructions on minimserver.com. If I let crashplan install java on its own, crashplan wouldn't start. I had Java-related errors in /usr/local/crashplan/log/engine_error.log

This is the Java version I ended up installing last night.

java version "1.8.0_65"
Java(TM) SE Embedded Runtime Environment (build 1.8.0_65-b17, headless)
Java HotSpot(TM) Embedded Client VM (build 25.65-b01, mixed mode)

During crashplan installation:
option 4, I pointed to some folder in the main drive e.g. /c/crash-backup (because filling up the OS partition causes problems)

After installation, I changed the Java path in /usr/local/crashplan/installs.vars from JAVACOMMON=/usr/local/crashplan/jre/bin/java to JAVACOMMON=/usr/local/bin/java

Hope that helps.

Hi Derek,

I agree that "page 24" is not the best place where to find a detailed guide. StephenB, your advice please?

Java: I had the same issue when I installed version 4.2. I ended up installing my own Java but then it was pointed out that it was not needed. I reckon it's just a matter of telling Linux/CrashPlan where to find the Java installed by the installer, so we don't have to install a separate one. Can someone advise on this too? Now my system is fully up and running and I'm a little hesitant to play with it.

Thanks for the other feedbacks, I'll have a look and update the guide accordingly! :)

(time for editing expired)

Ok, weird thing happened today. My CP GUI wouldn't connect anymore. After a while I found the ui.info had somehow reset. And on Windows 10 (I guess Windows 8 is the same) Filezilla will refuse to save under ProgramData and very little warning is given - I'll put a note (ops, which I can't do anymore! StephenB, any chance you could allow me to manage that post with no time limitations please?)

Anyway the new Java link works, thanks.

Maybe you can start a new thread, and I can block replies?

On Java I think the history might make a difference.  If Java was installed manually initially, then Crashplan makes it your responsibility.  If you do a clean install on the current version, Crashplan installs Java. 

---

tony359 wrote:

StephenB, any chance you could allow me to manage that post with no time limitations please?)

 

---

Regrettably I can't.  Can you copy/paste it to a new thread?

I see, that may explain.

Can I just start a new thread anytime? Will I be able to edit that post over time?

THanks for your help.

---

On Java I think the history might make a difference.  If Java was installed manually initially, then Crashplan makes it your responsibility.  If you do a clean install on the current version, Crashplan installs Java. 

---

Ah, that would make sense. I had java 6 installed before installing Crashplan. So maybe the notes should mention this caveat. Thanks!

I've got a problem!

It seems Crashplan updated to 4.5 and now it's not doing anything. I've got a notification from Crashplan saying the server hasn't been in touch for 15 days.

I've reconnected and I can connect, it's up and running, but it's "waiting for backup".

History only shows the service starting every day and nothing more.

Running the usual commands shows the service is running and ports are ok. But it's not doing anything.

Ideas?

Edit: ARGHHHH!!!!!

http://support.code42.com/CrashPlan/4/Troubleshooting/Linux_CrashPlan_App_Version_4.5_Cannot_Back_Up

Wait: my kernel is 2.6.37.6.RNx86_64.2.4, it should work?

Now what? OS6?

You need to update glibc.  https://community.netgear.com/t5/Backing-up-to-your-ReadyNAS/Crashplan-JRE-update-needed/m-p/1013370#M11396 points to a free add on to do that on 6.2.x ReadyNAS

Hi everybody

I had to reinstall CrashPlan on my NAS and honestly I cannot connect to it anymore. A few things have changed since the original step by step guide - I believe putty tunnel is not needed anymore - and I am a little stuck.

I have uninstalled and reinstalled CP.

Copied the token on my ui.info file

What's next? What needs and does not need to do with version 4.6?  Thanks!

Tony

Have you tried the putty tunnel?  It is stil working for me.

It is helpful to make C:\ProgramData\CrashPlan\.ui_info read-only - otherwise the PC Crashplan UI tends to re-write the token when it starts up.

Hi Stephen,

Yes, I managed to have it working again via putty but it was working without before. And I can't remember what I did to have that working.

It would be a good time to create the new step by step guide :)

I think the basic trick you are looking for is described here: https://www.liquidstate.net/how-to-manage-your-crashplan-server-remotely/

Adding serviceHost=nasipaddress in ui.properties on the pc, and changing the servicehost from 127.0.0.1 to 0.0.0.0 on the NAS

---

tony359 wrote:

 

 

It would be a good time to create the new step by step guide :)

---

I agree but if I took it on I'd needed to do a fresh install to check it - not something I'm prepared to do :-)

No worries, I've just freshly reinstalled mine! :)

Thanks

Somehow it did not work for me. The fact that the token was changed every time did not help and after wasting tons of time over the past few days I'm giving up now! It works with putty, happy days.

Why not making it simpler!!

I'm ok with using putty myself.  The first thing I do is tail the backup_file and history log, and I don't even launch the gui unless something looks off there..

What you probably did was edit <install dir>/conf/my.service.xml and change the serviceHost line to

<serviceHost>0.0.0.0</serviceHost>

so that it listens for the UI on all ports. You still need to edit the .ui_info on the PC file to point to it as per the headless instructions and use the actual ip of the ReadyNAS instead of the localhost.

4243,00000000-0000-0000-0000-000000000000,192.168.1.x
<port>,<          Token          >,<IP of ReadyNAS>

Adding serviceHost=nasipaddress as suggested isn't going to work (not on 4.6 anyway) as somewhere down the line there was a change in the format for the config file that handles this.

Has everyone here used WhoCares_'s (Stephan's) glibc addon to get this working? Has anyone run into a bunch of apt-get dependency problems from it? I tried his addon twice and it essentially prevents apt-get from being used because of dependency issues. As of now, I got CrashPlan running with the EJRE installer and a patch for the inotify_init1 error. This lets me stay on the older glibc and keep my apt-get working. As well as allow me to install and compile various things I needed running on the NAS.

inotify_init1() was added in Linux 2.6.27; library support was added to glibc in version 2.9. WhoCares_'s addon installs version 2.13. I wonder if installing an older version with support for inotify_init1 would keep things working. I may give this a shot after a much needed break from dealing with this and after making a backup of the OS partition.

---

JeremyP1 wrote:

Has everyone here used WhoCares_'s (Stephan's) glibc addon to get this working?

I installed it some time ago, and had no problems with NAS operation or crashplan since.  But I normally don't use apt-get so I wouldn't run into the dependancy issues. Perhaps WhoCares_ will comment.

CrashPlan upgrades now install Java - I was running 1.8 from ejre, but it decided to install 1.7 as well..

Has anyone had issues with Crashplan auto-upgrading and completely botching their installation on the Readnas? This has happened to me twice now. I go through the setup and workarounds to get CP up and running and it works really well up until the point that CP pushes an automatic update. It's getting old really fast, and I don't think there's a way to disable auto-updates. Seems CP updates don't like what was done as far as manually changing libjna files and also using the native JRE 1.7 that I installed with apt... what ends up happening is that the update "half-completes" and leaves CP in a broken state where the /usr/local/crashplan/lib directory is completely wiped out... anyone else notice this and have a workaround?

Hi

I haven't touched mine for a long while now. I receive notifications from CP every week so it's working.

Maybe it's better if you leave the installer using its own Java. I cannot remember whether the guide is mentioning that but when I first started looking into that it seemed that Java had to be manually installed - but the setup is copying its own version instead.

Have a look if you can remove the global Java - unless you need it - and maybe that would work when it updates. Also, can you find any logs that tell you what happened?