[SOLVED] Crashplan fails to start on linux / java path issue

Copy of a post I just made on the Code42 support forum

I have run a Netgear ReadyNas Pro with Crashplan headless for months. The first time I installed Crashplan in a headless config, I followed the instructions on the Netgear forums (viewtopic.php?f=4&t=61152) which worked flawlessly on initial installation. Subsequently I had a failed Add-on installation, and Crashplan stopped working. I reinstalled Java through Frontview, but that did not did not fix the Crashplan starting problem. I ssh'd into the NAS and tried a uninstall/reinstall of Crashplan which also did not fix it (from terminal running: ps auxww | grep -i CrashPlanService confirmed the service was not working).

Code42 wouldn't help because this is an unsupported configuration - BUT maybe they'll read this and bake up some fixes to make Crashplan more robust on linux installations (this issue relates to the linux/debian installation - not the fact that it's in a headless config). Anyway, back to the fix -- I then looked at the Crashplan log files, but noticed there were only two log files under /usr/local/crashplan/log# which were: engine_error.log and engine_output.log.

engine_error.log had the clue, an obscure java error.
Error: dl failure on line 863
Error: failed /usr/local/crashplan/jre/lib/amd64/server/libjvm.so, because /lib64/libm.so.6: symbol __get_cpu_features, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
...this means nothing to me, but on close inspection after some time I notice that the path for the JRE was within the Crashplan installation folder - rather than the main java folder for the add-in (which the readyNAS installed under /usr/bin/java7). How do I fix the java path?

Thanks to this post I found some comments that had the answer - the java path was wrong, and there was a file with one variable to fix it (http://blog.andrewkoebbe.com/posts/2014 ... dynas-102/). If you use the default installation location, crashplan installs under /usr/local/crashplan. Within that directory is a file named install.vars; where there is a variable JAVACOMMON, with a path to tell Crashplan which Java to use. The default value was the JRE inside the Crashplan installation folder - that was not working for some reason. I changed the variable to /usr/bin/java7 - pointing to the JRE installed for the entire readyNAS.
Then, I simply ran /etc/init.d/crashplan start ...and crashplan fired up and is now running fine.

I have not tested survivability of a restart, but will do that after Crashplan syncs up and backs up my latest files.

Whew!