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 running 1.6. The upgrade not only repeatedly failed, it also filled the OS partition with repeated downloads. So if you are running crashplan on OS 4.2.x, then take a look right away.
You can install jre 1.8 on the NAS - I used the procedure here: http://minimserver.com/ejre-installer.html
Crashplan has not tried up upgrade since I installed the jre - I'll update the thread after that happens.
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
85 Replies
Replies have been turned off for this discussion
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.
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.
I tried 4.3.3 after installing java 7 and what i get is:
engine_output.log:
Exiting!!! java.lang.NumberFormatException: For input string: ""
[10.09.15 12:22:17.117 INFO main root ] ***** STOPPING *****i tired to reinstall crashplan and i get lots of errors with cpio. I got around this somehow - yet still it is not starting:
engine_error.log:
Exception in thread "Thread-1" java.lang.NullPointerException
at com.backup42.service.backup.BackupController.stop(BackupController.java:1114)
at com.code42.backup.BackupManager.tearDown(BackupManager.java:279)
at com.backup42.service.backup.BackupController.tearDown(BackupController.java:596)
at com.backup42.service.CPService.cleanup(CPService.java:1906)
at com.backup42.service.CPService$1.run(CPService.java:355)i have no clue what to do :(
I see you are trying to install 4.3.3 they have a newer version 4.4.1 (I beleive it is 4.4.1 - 1435726800441 (2015-07-01T05:00:00:441+0000) - Build: 30) try that version. as far as I can tell this version does not install a seperate JRE as did 4.3.)
I had to unstall 4.3 and reboot and then install 4.4.1 to get mine to work.
My /usr/local/crashplan/install.vars has now changed to:
TARGETDIR=/usr/local/crashplan BINSDIR=/usr/local/bin MANIFESTDIR=/usr/local/var/crashplan INITDIR=/etc/init.d RUNLVLDIR=/etc/rc2.d INSTALLDATE=20151006 APP_BASENAME=CrashPlan DIR_BASENAME=crashplan JRE_X64_DOWNLOAD_URL=http://download.code42.com/installs/proserver/jre/jre-7-linux-x64.tgz JRE_I586_DOWNLOAD_URL=http://download.code42.com/installs/proserver/jre/jre-7-linux-i586.tgz JAVACOMMON=/usr/local/bin/java
My symlink in /usr/local/bin/java now points to /etc/frontview/addons/bin/EJRE/ejre1.7.0_75/bin/java instead of pointing to the JRE that was installed local to Crashplan in 4.3..
They have a newer version 4.4.1.
I had to uninstall 4.3. and reboot and install 4.4.1 to get it to work.
My JAVACOMMON in install.vars now points to "JAVACOMMON=/usr/local/bin/java"
my /usr/local/bin/java now points to my global install instead of the EJRE that was installed locally in Crashplan 4.4/etc/frontview/addons/bin/EJRE/ejre1.7.0_75/bin/java.
My global install is the ejre installed via this link http://minimserver.com/ejre-installer.html.
4.4.1 came out shortly after 4.4.0. After I got java 8 installed, it upgraded first to 4.4.0, and then successfully upgraded to 4.4.1.
Why did you upgrade to java 7 when the current version is 8? Perhaps that is related to the issue.
You can also submit a support request to crashplan. Though their policy is that they don't support headless, they still have provided help to me. I have gotten good support on the tickets I've entered.
I had the same problem. I'm running OS 6.5.3 on a ReadyNAS Ultra 2, so I couldn't use the java installer addon from http://minimserver.com/ejre-installer.html.
However I can confirm that Crashplan will upgrade from 4.3 to 4.4.1 with Java 1.7 installed using apt-get.
In order to get the windows GUI to connect again, I had to totally delete all the .ui_info files from the pc, reinstall crashplan and update .ui_info with the secuirty token; as described in using crashplan headless instructions. It's seems the format of .ui_info is slightly different in crashplan 4.4.1. Also it seems you don't need to edit the port in ..\conf\.ui_<username> anymore as you did in 4.3.
- Anybody else using plex who also installed this addon? It looks it may have broken audio transcoding. I have tested a few movies that have 5.1 audio and the transcoder now appears to mux the track improperly. Just curious if anyone else sees this or its a plex issues. Plex is like a house of cards so it could very well be on their side but timing is coincidental.
Do you see any error messages in either the syslog or logs provided by Plex? While there is a chance that the glibc broke the transcoding this would be a quite rare thing to happen. Unfortunately I currently don't have Plex installed so I can't test it.
-Stefan
Had a look through the logs and didn't see any issues. Tried another Plex client that also requires transcoding and it played fine. So this looks to be a android fire plex client issue. Not a shock really as plex on the fire tv platform is riddled with issues.
Thanks for putting this addon together! Everything seems to be looking good!
Stefan's glibc addon seems to have fixed it for me! Thanks!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
