Crashplan for Dummies, aka Step by Step :)

I also ran into an issue with the target ReadyNas listed gray circle and a "Unable to backup - No Connection for x.x days" message. Here's the solution.

I increase the limit by running ulimit -n 8192 and then /etc/init.d/crashplan restart manually whenever I run into the gray circle issue. I've tried following the steps below to make it permanent, but haven't been successful.

I found out it was because the limit for open files was too small on the readynas. Here's the instructions from CrashPlan support:

Hello Greg. I have reviewed your logs and I have a few questions about the hardware that CrashPlan is running on. They appear to be NAS devices themselves, they are running a Netgear Linux Kernel for ReadyNAS. Running CrashPlan directly on a NAS device is an unsupported configuration and I would not be able to assist in troubleshooting anything caused by running CrashPlan in an unsupported way. However, I can tell you that the set of logs from the machine named "NAS-Home-2" indicate that there are too many open files. Every operating system imposes a limit on the number of "files" a process may have open at any one time. More accurately, the OS imposes a limit on the number of file descriptors a process may have open at any one time, but for our purposes the difference isn't significant. CrashPlan will occasionally bump up against these limits; it's not common by any means but we do see it sometimes for very large archives (i.e. archives with lots of files). Linux defines both a system-wide and a per-process limit on the number of open files a process can open. It's best to always begin with the per-process limit for two reasons: Changing this value instead of the system-wide value minimizes the impact on the rest of the system It's likely to be the lesser value anyway You can use the "ulimit" command (actually a shell builtin on most platforms now) to get the limit for this process on the number of open files: ulimit -n This value can be set using a variation on the above command: ulimit -n 4096 On rare occasions you may find yourself increasing this limit to a value that exceeds the system-wide limits. When this occurs the only option available is to modify the system-wide values. This should be a fairly rare occurence but if it does come up the following commands should prove helpful. You can view the current system-wide limit using the proc file system: cat /proc/sys/fs/file-max This value can be set for the current system by writing to the same file: echo "4096" > /proc/sys/fs/file-max Note that modifying the proc file system will not cause the change to be preserved across restarts. In order to make this change permanent you'll need to modify /etc/sysctl.conf. Open /etc/sysctl.conf (you'll need to be root) Edit (or add if not present) the "fs.file-max" parameter Save the file and exit Note that editing this file will not bring about a change in the running system. To do this you'll need to re-apply all the settings defined in /etc/systctl.conf (including the changes you just made). The following command will do it: sysctl -p /etc/sysctl.conf The above instructions are for a normal Linux distro and not a custom built one like the Netgear Linux distro but it should work for you. Thanks. Kevin