As I am currently evaluating both Crashplan and SpiderOak, here are the procedures for getting both of them updated in the source lists. In the interest of full disclosure, I have not yet downloaded and tested the SpiderOak packages, and I am NOT an experienced Linux user. Just thought everyone might find this procedure useful for getting to the point where downloading both packages is simple:
1. Log in via SSH client. (I use PuTTY)
2. Edit /etc/apt/sources.list with either vi or nano "vi /etc/apt/sources.list" or "nano /etc/apt/sources.list"
6. At the end of the update, you'll get the following error message (although the public key might be different): W: GPG error: http://apt.spideroak.com stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5D654504F1A41D5E W: You may want to run apt-get update to correct these problems
7. To correct this issue, you'll need to get the public key and install it. To do so, enter the following: "gpg --keyserver http://apt.spideroak.com/spideroak-apt-pubkey.asc --recv-keys 5D654504F1A41D5E" (where the public key must match the one received above)
8. If successful, you will see the following: gpg: requesting key F1A41D5E from http server apt.spideroak.com gpg: /root/.gnupg/trustdb.gpg: trustdb created gpg: key F1A41D5E: public key "SpiderOak Apt Repository <apt@spideroak.com>" imported gpg: Total number processed: 1 gpg: imported: 1
9. Finally, add it by entering the following: "gpg -a --export 5D654504F1A41D5E | sudo apt-key add -"
10. If successful, you will see the following: "OK"
11. Now, you can update again: "apt-get update"
12. A successful update will look like this (assuming you entered both Crashplan and Spideroak into your source.lists file):
Need some help. I have a ReadyNAS Ultra 4 Plus running the latest Radiator at 4.2.21. I followed the directions to a T except I am running CrashPlan 3.2.1 for linux on my ReadyNAS. The point where I am failing is that I am unable to telnet to localhost on port 4200 from the readynas. I have properly setup my ui.properties file with servicePort=4200. When I try to launch the Desktop Client I get the failure message and if I would like to try the backup. The only problem that I can tell is that when I run the netstat command on my Readynas, I don't see it trying to listen on 4242. It does however listen on 4343. I am on a windows box and made sure I have tunneling setup on my putty settings. I also rebooted both the desktop and readynas. But still it won't listen on 4242. I do however see that it listen on 4243.
*EDIT* So it turns out that even though I get a connection refused when trying to telnet to localhost on port 4200, the Desktop Client works fine and I can see my Readynas. Has anyone seen this situation? Anyways, it appears to be working and I am going to attempt a backup and see if it works.
*Edit Again* So it appears all is working well and fine even though the readynas is not listening on port 4242 and the telnet localhost 4200 fails to connect. My last problem seems to be using the desktop client without SSHing first. According to the dummy guide, it says I should be able to close everything out and change my ui.properties back to default and I should be able to use the desktop client without puttying first. while it does connect, it no longer sees my readynas, but now it sees my desktop. Any suggestions? I guess for now I can always just putty first. A little annoying but not a big deal.
Need some help. I have a ReadyNAS Ultra 4 Plus running the latest Radiator at 4.2.21. I followed the directions to a T except I am running CrashPlan 3.2.1 for linux on my ReadyNAS... The only problem that I can tell is that when I run the netstat command on my Readynas, I don't see it trying to listen on 4242. It does however listen on 4343. I am on a windows box and made sure I have tunneling setup on my putty settings. I also rebooted both the desktop and readynas. But still it won't listen on 4242. I do however see that it listen on 4243..
I am also running 3.2.1 (both the PC and the ReadyNAS autoupdated when 3.2.1 was released). I am seeing the results in the guide:
Did you use the same command options that are in the guide? The -na is important.
skim32 wrote:
So it turns out that even though I get a connection refused when trying to telnet to localhost on port 4200, the Desktop Client works fine and I can see my Readynas. Has anyone seen this situation? Anyways, it appears to be working and I am going to attempt a backup and see if it works.
Yes, this is normal. BTW, make sure you select the shares under the "C" volume for backup, the top level folders you will see are symbolic links (shortcuts) - if you pick them, crashplan will backup the shortcut file, but not the data.
skim32 wrote:
According to the dummy guide, it says I should be able to close everything out and change my ui.properties back to default and I should be able to use the desktop client without puttying first. while it does connect, it no longer sees my readynas, but now it sees my desktop.
If you change ui.properties back, you can run the desktop client to manage the crashplan server that is locally installed on your PC. This would be important to people who have a multi-PC license. So this behavior is expected.
Did you use the same command options that are in the guide? The -na is important.
I am now seeing my ReadyNAS listening on port 4242. I dunno why it wasn't before. I ran the same netstat command and only saw it listening on 4243. After I ran the Desktop Client for the first time, I think it started to listen on 4242. A little strange and unexpected but at least it's working.
StephenB wrote:
Yes, this is normal. BTW, make sure you select the shares under the "C" volume for backup, the top level folders you will see are symbolic links (shortcuts) - if you pick them, crashplan will backup the shortcut file, but not the data.
I am familiar with linux symlinking, but thanks for the tip. Backup is working great and I've already tested a restore. A little strange that the default restore location is the conf folder. But I am able to change that on the fly so it's not a big deal. Anyone know of way to make it default to original location so I don't have to change it everytime?
StephenB wrote:
If you change ui.properties back, you can run the desktop client to manage the crashplan server that is locally installed on your PC. This would be important to people who have a multi-PC license. So this behavior is expected.
I guess I misunderstood the guide. I was actually using the following link for my guide (http://www.shasam.net/blog/2012/3/21/cr ... s-x86.html). I was under the impression that even after I changed my ui.properties back to the default I should still be able to manage my ReadyNAS without puttying first. I guess I have to putty in everytime. Not a big deal. Besides that, the only other two things that were unexpected from the guide was that my readynas didn't start listening to port 4242 until after I connected with my Desktop Client and i always got a connection refused when telneting to localhost on port 4200. But everything works regardless of those two differences.
I'm on Verizon Fios 25/25 plan and am seeing speeds at around 9Mbps. Anyone know if that's a limitation of Crashplan? Or I wonder if my Fios service isn't living up to it's advertised plan. My speedtest results show around 20Mbps, so I am curious as to what other people are seeing.
...I'm on Verizon Fios 25/25 plan and am seeing speeds at around 9Mbps. Anyone know if that's a limitation of Crashplan? Or I wonder if my Fios service isn't living up to it's advertised plan. My speedtest results show around 20Mbps, so I am curious as to what other people are seeing.
I have Verizon Fios 35/35. Speeds vary quite a bit - it depends in part on what is going on with Crashplan Central, and partly on the NAS (and your ISP of course). I've seen it vary from 1.5 Mbps to 18 or so. 9 Mbps is fairly is typical.
I've set the WAN sending buffer size to 2560 KB, and the receiving message buffer size to 512 KB in backup settings. I also have data de-duplication set to "minimal" and compression set to "off" in advanced backup settings. This seems to give pretty good performance.
I've also made a few adjustments to my.service.xml on the NAS which seems to speed up some file types. They certainly helped in the beginning, but I haven't confirmed how much they help with 3.2.1. PM me if you want details on that.
I don't recall the exact performance of my initial backups, but I know I was uploading an average of ~70 GB per day, perhaps more. There is a short performance thread here: viewtopic.php?f=4&t=61412 you might want to add to it.
I followed the guide in the OP and have had CP 3.0.3 running for a while now without issues. Will it auto update the Linux version on our NAS?
A few days ago in my backup status email I noticed that my backup was not complete any more and the next report showed that it was even more behind. When I checked on the history from the CP client it was showing that the CP service was starting and stopping multiple times a min. I am not Linux man so I figured I would try to uninstall CP from the NAS (I did not do the full uninstall where you clear out the config files) and then install 3.2.1. That went without hitch. I rebooted the NAS after that and then connected with the client. It took about 5 hours for the NAS to verify all of the data with what was already backed up to the CP cloud. I have 3 backup sets and it completed 2 of them and then the client dropped. I reconnected and checked the history and this is what I see:
So it looks like it is having a hard time keeping the CP service running on the NAS. I am on RAIDiator 4.2.21, Memory: 4096 MB [4-5-5-18 DDR2], Volume C: Online, X-RAID2, 6 disks, 77% of 7404 GB used. The services I have installed are CP, Nas Monitor 3.3, PHP+Mysql Support 1.4, ReadyNAS Remote, v1.0.9.78, uTorrent 2.2.02 (not running).
I shutdown the readynas and cold booted it. From what it looks like when ever there is a backup job running the CP service keeps restarting. I have 2 backup sets that only run at night and one that is all the time. As soon as the all the time set finished the CP service ran fine until my at night sets started and then the service started restarting again. The CP client gets disconnected when that happens but my Putty connection to the NAS is fine. So this seems to be only affecting CP.
You might want to engage CrashPlan support (and post on their forum), They won't do much with the headless configuration, but I think your issue is not related to the fact you are headless. I see some cases where the service disconnects in my log, but I am not seeing the continuous "Crashplan Started" entries that you are seeing.
In the meantime, you can look at the logs in /usr/local/crashplan/log. Note there are also some logs in /usr/local/crashplan/bin. Also, if you click on the house in the upper right corner of the client, you will get a list of commands (which you can enter at the top of the window). There is a way to adjust the logging level, but regrettably the usage hint is not informative.
You could also be running out of virtual memory. If you look at /usr/local/crashplan/bin/run.conf you will see an -Xmx512m option. You can try doubling that to -Xmx1024m and see if that helps.
/usr/local/crashplan/bin Was full of restart logs that all look pretty much the same:
Fri Aug 24 11:33:08 CDT 2012 : /usr/local/crashplan/bin/restart.sh Fri Aug 24 11:33:08 CDT 2012 : APP_BASENAME=CrashPlan Fri Aug 24 11:33:08 CDT 2012 : DIR_BASENAME=crashplan Fri Aug 24 11:33:08 CDT 2012 : Stopping using ./CrashPlanEngine... Stopping CrashPlan Engine ... Still running, killing PID=16820 ... OK Fri Aug 24 11:33:08 CDT 2012 : Sleeping 10 seconds... Fri Aug 24 11:33:18 CDT 2012 : Starting using ./CrashPlanEngine... Starting CrashPlan Engine ... Using standard startup OK Fri Aug 24 11:33:18 CDT 2012 : New Service Process below: Fri Aug 24 11:33:18 CDT 2012 : Exiting restart script
Nothing jumped out to me (non linux guy) in the /usr/local/crashplan/log files. I decided to try your Virtual memory change in /usr/local/crashplan/bin/run.conf DEFAULT File:
... A few days ago in my backup status email I noticed that my backup was not complete any more and the next report showed that it was even more behind. When I checked on the history from the CP client it was showing that the CP service was starting and stopping multiple times a min. ... I reconnected and checked the history and this is what I see:
So it looks like it is having a hard time keeping the CP service running on the NAS.
I recently ran into this also (and needed to apply my own solution :slap: ). I suspect I hit some threshold related to directory depth which caused CP to run out of memory.
You don't get any meaningful error report from CrashPlan if this happens, so you do need to monitor what it is doing by logging in with the client from time to time.
I am trying to setup CrashPlan on my ReadyNAS Pro that I have sitting in my office. I would like to use it as an offsite backup location for my home computers. I have read everything I can find for installing it on the ReadyNAS and seem to be stuck.
My problem seems to be the same one f41yaz posted here: http://www.readynas.com/forum/viewtopic.php?f=4&t=61152&hilit=crashplan&start=30#p363309
I am stuck trying to connect my desktop GUI with the headless install per the "How It Works - Using PuTTY" section of this guide: http://support.crashplan.com/doku.php/how_to/configure_a_headless_client#how_it_works_-_using_putty
tcp 0 xxx.xxx.xxx.xxx:4242 yyy.yyy.yyy.yyy:zzzzz ESTABLISHED
part.
Any ideas for a noob? I have clicked and read every link I can find about this and have seen a couple people with the same issue. However, It seems they somehow figure it out and disappear without posting a solution.
My desktop PC is Win7 x64, NAS is ReadyNAS Pro4
My ui.properties file shows:
#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
If you look at the putty connection setting (Connection->SSH->Tunnels) you should see "L4200 Localhost:4243" in the forwarded ports list. Do you see that?
It asks me for a to setup an account or use an existing username and password. After that it looks like it connects to the NAS this time. Before I originally posted it was just connecting to the local engine, NAS was not showing up at all. Now it says Nas (this one). I guess it wasn't broken even though It still throws:
I am having an issue getting this working. I have installed CrashPlan on the NAS and followed the instructions.
The only way I can get the machines to backup to the NAS however is to issue the command on the NAS: ulimit -n 8192 and then /etc/init.d/crashplan restart
I have tried setting this as a default in the /etc/sysctl.conf I have also tried setting the noffile limts in the /etc/security/limits.conf
Whenever I restart the NAS however the only way I can get the backup to start running is to run /etc/init.d/crashplan restart
