CrashPlan Pro for Linux: Stuck at “Waiting for Backup” or “Connecting to Backup Destination”

First off, I want to give a shout-out to a very helpful post. Thank you to Bryan for posting these tremendously helpful posts on how to get CrashPlan up-and-running on headless Linux server (aka: pretty much any Linux Web Server).

Installing CrashPlan on a Headless Linux Server
Using the Windows CrashPlan Client to manage a headless Linux server 

Also there is more on CrashPlan’s own site about this here.

Anyways, so the rest of this article assumes that you have successfully gotten CrashPlan installed on your Linux server, and that you are able to manage it via a remote client and select folders for backup.

So, what happened to me was, I got everything configured correctly, but still could not get the backup going. These are the symptoms I faced:

1. The folders were successfully selected; I could see them on CrashPlan’s web interface as selected
2. CrashPlan PRO Online (CrashPlan Central) was selected as the destination
3. No matter  what I tried, it would just sit there saying “Waiting for Backup” or “Connecting to Backup Desitnation” and would say 0 files completed.

These are the troubleshooting steps I performed:

1. I verified that ports 443, 4242 and 4243 were allowed for outbound connections
2. I tried restarting the CrashPlan Engine multiple times
3. I even uninstalled and re-installed CrashPlan completely
4. There were various posts online about versions of Java and changing things with the Java install. I didn’t think this was the problem for me…so I would suggest you skip those steps if you see them.

I eventually started looking at the logs, and found this Java error in one of the log files:

Exception in thread "W30145090_ScanWrkr" java.lang.NoClassDefFoundError: Could not initialize class com.code42.jna.inotify.InotifyManager
at com.code42.jna.inotify.JNAInotifyFileWatcherDriver.<init>(
at com.code42.backup.path.BackupSetsManager.initFileWatcherDriver(
at com.code42.backup.path.BackupSetsManager.startScheduledFileQueue(
at com.code42.backup.path.BackupSetsManager.access$1600(
at com.code42.backup.path.BackupSetsManager$ScanWorker.delay(

Now, as far as I understand it, inotify is only needed if you want to do scanning for real-time file changes. I actually didn’t even want to do this, so I disabled that, but it still didn’t find my problem.

I finally came across this post on CrashPlan’s own site that has a viable answer! Unfortunately the title of the post doesn’t say anything about “Waiting for Backup” so it is hard to connect it as the solution for this particular issue. Thank you to Renee S from CrashPlan for posting a viable solution that works on that forum!

Basically, the short of it is, CrashPlan doesn’t have the right parameter on the /tmp/ folder it needs to perform the backups.

Here are the instructions to get it to work again. 

1. You will need to create a new tmp folder for CrashPlan on your Linux server. Here are the specifications for that folder
– They recommend putting the directory in a user’s home directory (not root’s)
– The user CrashPlan was installed under must have write permissions on the directory you create
– IMPORTANT: The directory must be without the noexec restriction.
– So, for example, your directory might be: /home/myname/crashplan-temp

2. Once you have your temp folder created, you need to edit the run.conf file which is located here: /usr/local/crashplan/bin/run.conf

3. Open up this file, and look for this line:

SRV_JAVA_OPTS="-Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m -Xmx512m -Dnetworkaddress.cache.ttl=300 -Dnetworkaddress.cache.negative.ttl=0"

4. We need to add an additional paramater specifying the new temp directory. This is done using this form:<path>

where <path> is a pointer to the directory you created in step 1. This can be added to the BEGINNING of the line, right after the quotes, so using the theoretical directory listed in step 1, it might look something like this

SRV_JAVA_OPTS=" -Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m -Xmx512m -Dnetworkaddress.cache.ttl=300 -Dnetworkaddress.cache.negative.ttl=0"

5. Once you have that saved, restart CrashPlan on the Linux server for good measure, then it should work!

A couple tips if it still isn’t working:

– Make sure you have appropriate permissions on the directory you specified
– a few people had success changing the ownership to nobody:nobody  (chown nobody:nobody). I didn’t have to do this, but it might work for you

I hope this fix works for you!