NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Crashplan JRE update needed
Crashplan released an update on 21 September 2015 (4.4.0) which fails to install on my pro-6 (running 4.2.28).
The issue is that the new service requires jre 1.7 or jre 1.8, and my system was r...
Here's for those who boldly go ...
https://rnxtras.com/add-ons/update/glibc6-2-13-readynas-os-4-x86-only-60494
Have fun!
-Stefan
The installer I used put java 1.8 in /usr/local/bin/java Java 1.6 is in /usr/bin/java.
So I also needed to change JAVACOMMON in install.vars. Crashplan has now upgraded to version 4.4.0. I still need to upgrade the client app on the PC, but so far it looks like the update issue is solved.
(Crashplan hasn't yet provided a 4.4.0 download, which is why the client can't be updated).
Just found your thread after a long time and a very large number of tabs trying to work out what happened to my NAS all of a sudden. I have exactly the same problem. 3.4GB in /usr/local/crashplan/upgrade from many directories of the form "1435726800440.1442908683198", all containing a copy of crashplan jars.
Thanks for your help, I'll hopefully put it to good use.
For anyone who thinks they may have the same problem, here's how I got this far:
Initial symptoms: NAS boots up and is visible through RAIDAR and FrontView. But all the shares can't be mounted from my Windows boxes, and trying to disable/re-enable CIFS is failing. After a while, SSH access stops working. Crashplan is complaining the backup hasn't run for a few days.
Step 1 - Enabling tech support mode
http://kb.netgear.com/app/answers/detail/a_id/21100
Step 2 - Logging in via telnet, search the web for the password, not sure if I should post it here or not.
Step 3 - Mounting os partition
# start_raid.sh
# mount /dev/md0 /sysroot
Step 4 - Check OS partition disk usage
# df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 10240 0 10240 0% /dev
/dev/md0 4184756 4184628 0 100% /sysrootStep 5 - Identify usage under /sysroot
search for disk usage by directory, filter for entries in the Gigabytes (or anything with G in it - I'm not a linux ninja)
# du -ch | grep G
...
3.0G ./usr/local/crashplan/upgrade
3.4G ./usr/local/crashplan
3.4G ./usr/local# cd usr/local/crashplan/upgrade
# ls
1430802000433.1441892511941 1435726800440.1442892937381 1435726800440.1442938901933 1435726800440.1442984305410
1430802000433.jar 1435726800440.1442894986800 1435726800440.1442940789145 1435726800440.1442986202689
...Step 6 - Delete most of these folders
From here on my plan is to follow Stephen's advice.
Deleting all the 1*.* files and folders in usr/local/crashplan/upgrade is safe, you don't need to leave any of them in place.
At the moment there is no windows 4.4.x download available, so you do need to look at the logs to tell the status.
As stated by others you must upgrade to jre 1.7 or better for the crashplan 4.4 upgrade to complete. Once you upgrade java don't forget to set the default version. Commands look something like this:
java -version
......
apt-get install openjdk-7-jre
......
$ sudo update-alternatives --config java
(and select the jdk you want to use.)
but after the upgrade completes I am finding that I can no longer connect to the engine remotely. Has anyone solved this issue yet?
I am hoping that when the window's client gets upgraded to 4.4 that the remote client connect issue will be fixed......ugh
This is such an excellent thread with perfect and succinct instructions that made it almost fun to fix this problem on my Ultra 2. Thanks StephenB!
(Well, I don't know yet whether it's really fixed (I will know when crashplan attempts another update), but I have no reason to believe that it didn't work.
One litle additional info, in case anyone is wondering: usr/local/bin/java is a symlink to /etc/frontview/addons/bin/EJRE/ejdkl.8.0_51/linux_i586/jre/bin/
Hm, the only thing I don't understand is why the java installation in that path is dated from 2015-06-25. Maybe the installation failed? Apparently not, since the /etc/frontview/addons/bin/EJRE/ejdk1.8.0_51/linux_i586/jre/release gives me JAVA_VERSION="1.8.0_51".
Anyway. I'll see what happens in a day or two.
Mine has the same date, I don't think its a real problem. I suspect the directory is extracted from the tar.gz, and that the extraction preserved the date.
The old java is still there, so you do need to update JAVACOMMON as posted above.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
