Crashplan JRE update needed

[StephenB]

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.

[WhoCares_ · Accepted solution]

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

[StephenB]

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).

[satiated]

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

https://community.netgear.com/t5/Using-your-ReadyNAS/Readynas-NV-V1-Mounting-OS-partition-in-support...

# 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% /sysroot

Step 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.

[StephenB]

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.

[rugene]

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

[StephenB]

---

@rugene wrote:

... 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

---

The current version on my linux system is 4.4.1 (there was a second update pushed).  

The windows client isn't available yet (per crashplan support), and should solve the connection issue.  You will need to reset the application token on the PC (as the software upgrade changes the token on the linux system).

[StephenB]

The 4.4.1 windows client is available now at https://www.code42.com/crashplan/thankyou/

It did a complete reinstall on my PC, so I needed to re-enter my crashplan account info and then needed to re-configure .ui_info

[jamestx10]

I am still having an issue getting the update to install.

java -version
java version "1.8.0_51"
Java(TM) SE Embedded Runtime Environment (build 1.8.0_51-b07, headless)
Java HotSpot(TM) Embedded Server VM (build 25.51-b07, mixed mode

Looks like Java 1.8 is installed fine but

update-alternatives --config java

There is only 1 program which provides java
(/usr/lib/jvm/java-6-sun/jre/bin/java). Nothing to configure.

[StephenB]

What is JAVACOMMON in /usr/local/crashplan/install.vars set to?

Type "which java" and make sure that JAVACOMMON is set to the same path.  Then restart crashplan.

[jamestx10]

That fixed it. THANKS

[chaug]

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.

[StephenB]

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.

[newuser11]

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 😞

[sdouek]

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..

[sdouek]

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.

[StephenB]

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.   

[newuser11]

Hello,

i did the upgrade to java 7 as this is the latest version for Debian Wheezy (Readynas 516).

I tried with 8 manually - but had the same result...

I installed 4.4.1 (had no 4.4.0) and reinstalled it as well - same problem, null pointer exceptions are thrown in my face.

I do have a ticket open - no answer yet for 1+ days.

What i have done now is, i went back to http://www.shasam.net/blog/2012/3/21/crashplan-on-the-netgear-readynas-x86.html and the download link for that ultra old version is still working. So i installed that - and so farit  running. Lets wait what happens on the next auto update... 😞

[newuser11]

Here we go - as soon as i try to connect with the client (using 4.4.1 as i could not find an older version) the client says 'upgrading' and the engine output shows me the updates.

Upgrading to 3.5.3 3.6.3 3.6.4 3.6.5 3.7.0. 4.2.0 -> all went fine.

Coming to 4.3.0 i get the following error and the service stops running:

[10.09.15 14:08:19.318 INFO main root ] *************************************************************
[10.09.15 14:08:19.319 INFO main root ] *************************************************************
[10.09.15 14:08:19.319 INFO main root ] STARTED CrashPlanService
[10.09.15 14:08:19.320 INFO main root ] CPVERSION = 4.3.0 - 1427864410430 (2015-04-01T05:00:10:430+0000) - Build: 31
[10.09.15 14:08:19.320 INFO main root ] LOCALE = English
[10.09.15 14:08:19.320 INFO main root ] ARGS = [ ]
[10.09.15 14:08:19.320 INFO main root ] *************************************************************
[10.09.15 14:08:19.401 INFO main root ] Adding shutdown hook.
[10.09.15 14:08:19.405 INFO main root ] BEGIN Loading Configuration
[10.09.15 14:08:19.445 INFO main root ] BEGIN Copy Custom
[10.09.15 14:08:19.445 INFO main root ] Directories: [.Custom, custom, /repository/.Custom, /repository/custom]
[10.09.15 14:08:19.446 INFO main root ] NOT waiting for custom skin to appear
[10.09.15 14:08:19.446 INFO main root ] NO customizations found.
[10.09.15 14:08:19.446 INFO main root ] END Copy Custom
[10.09.15 14:08:19.448 INFO main root ] Loading from default: /usr/local/crashplan/conf/default.service.xml
[10.09.15 14:08:19.733 INFO main root ] Loading from my xml file=conf/my.service.xml
[10.09.15 14:08:19.796 INFO main com.backup42.common.config.ServiceConfig] ServiceConfig deferred upgrade.
[10.09.15 14:08:19.797 INFO main root ] Loading ServiceConfig, newInstall=false, version=6, configDateMs=null, installVersion=1331787601320
[10.09.15 14:08:19.798 INFO main root ] OS = Linux
[10.09.15 14:08:19.959 INFO main root ] AuthorityLocation@893284971[ location=central.crashplan.com:443, hideAddress=false, isLocked=false ]
[10.09.15 14:08:19.960 INFO main root ] Checking Java memory heap max.
[10.09.15 14:08:19.961 INFO main root ] Previous Java memory max heap size was 1024
[10.09.15 14:08:19.962 INFO main root ] END Loading Configuration
[10.09.15 14:08:19.966 INFO main com.code42.net.ConnectivityTester ] Connectivity testing localhost, port=4242, connectionTimeout(ms)=100, retryDuration(ms)=100
[10.09.15 14:08:20.072 INFO main com.code42.net.ConnectivityTester ] Failed to connect after duration=105, retryDuration=100, address=localhost, connectTimeout=100, e=Connection refused
[10.09.15 14:08:20.072 INFO main com.code42.net.ConnectivityTester ] Connectivity testing localhost, port=4243, connectionTimeout(ms)=100, retryDuration(ms)=100
[10.09.15 14:08:20.173 INFO main com.code42.net.ConnectivityTester ] Failed to connect after duration=100, retryDuration=100, address=localhost, connectTimeout=100, e=Connection refused
[10.09.15 14:08:20.175 WARN main com.backup42.service.CPService ] 1, java.lang.ArrayIndexOutOfBoundsException: 1
java.lang.ArrayIndexOutOfBoundsException: 1
at com.backup42.service.ui.UIInfoUtility.getUIConnectionDetails(UIInfoUtility.java:53)
at com.backup42.service.ui.UIInfoUtility.hasUIConnectionDetails(UIInfoUtility.java:122)
at com.backup42.service.CPService.initServicePorts(CPService.java:1077)
at com.backup42.service.CPService.start(CPService.java:341)
at com.backup42.service.CPService.main(CPService.java:1922)

Exiting!!! java.lang.ArrayIndexOutOfBoundsException: 1
[10.09.15 14:08:20.176 INFO main com.code42.lang.ThreadUtils ] ** THREADS AND STACK TRACES **
+ Thread[main,5,main], t.isDaemon = false
Stack:
java.lang.Thread.dumpThreads(Native Method)
java.lang.Thread.getAllStackTraces(Thread.java:1640)
com.code42.lang.ThreadUtils.dumpThreads(ThreadUtils.java:91)
com.code42.lang.ThreadUtils.logThreadsAndStackTraces(ThreadUtils.java:80)
com.backup42.service.CPService.exit(CPService.java:1969)
com.backup42.service.CPService.start(CPService.java:538)
com.backup42.service.CPService.main(CPService.java:1922)
+ Thread[Reference Handler,10,system], t.isDaemon = true
Stack:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:503)
java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
+ Thread[Signal Dispatcher,9,system], t.isDaemon = true
Stack:
+ Thread[Finalizer,8,system], t.isDaemon = true
Stack:
java.lang.Object.wait(Native Method)
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209)
[10.09.15 14:08:20.177 INFO Thread-0 root ] Stopping service...
[10.09.15 14:08:20.180 WARN Thread-0 com.code42.watcher.SystemWatcher ] Attempting to stop and SystemWatcher NOT started!
[10.09.15 14:08:20.180 INFO Thread-0 root ] SystemWatcher stopped.
[10.09.15 14:08:20.181 INFO Thread-0 root ] Service stopped

----

system dead again 😞

[newuser11]

After linking /usr/bin/java to version 8 and reinstalling 4.4.1 again - it now is working....

thanks god i backed up all informations and the ./var/lib/crashplan/.identity changed.....

[sdouek]

Stephen I do not know if you were asking me about why I upgraded to 7 but here goes.

I upgrade to 7 originally when I installed CrashPlan_3.6.4_Linux and I was running the original Java 6 that came with my readynas business pro. I couldn't get it to work but then I upgraded the global Java via EJRE Installer ReadyNAS add-on and it worked. When 4.3 came out I noticed that it installed its' own local Java and now that 4.4.1 came out it did not (at least that is the behavior on my nas). I was going through some code and I found that Crashplan checks to see if and or what Java version you have and determines whether or not to install a local version. Unfortunately this type of check changes between versions and sometimes does not work.

If you look at the code in /root/crashplan-install/install.sh it has those checks for Java but like I wrote it works in one version and not another very odd.

[StephenB]

---

@sdouek wrote:

Stephen I do not know if you were asking me about why I upgraded to 7 but here goes.

---

I was actually asking newuser11, and was wondering if his particular issues were related to Java 7.

It sounds like he is past that now though.

[sdouek]

---

@StephenB wrote:

---

@sdouek wrote:

Stephen I do not know if you were asking me about why I upgraded to 7 but here goes.

---

I was actually asking newuser11, and was wondering if his particular issues were related to Java 7.

It sounds like he is past that now though.

---

Lol - ok (Just a FYI)

Crashplan seems to have an issue between versions, with installing JAVA locally or globally and JAVACOMON value pointing to the JAVA local install and if it installs a JAVA local to the install or does not.

[StephenB]

---

@sdouek wrote:

---

...Crashplan seems to have an issue between versions, with installing JAVA locally or globally and JAVACOMON value pointing to the JAVA local install and if it installs a JAVA local to the install or does not.

---

Not sure who is having more fun - Crashplan support with 4.4.1 or Netgear support with 6.4.0  

[weinelm]

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.

[weinelm]

I had this exact problem too. I'm running OS 6.5.3 on a ReadyNAS Ultra 2, so I couldn't use the addon from http://minimserver.com/ejre-installer.html to install java 8.

However I can confirm that Crashplan upgraded from 4.3 to 4.4.1 once I installed Java 7 using apt-get.

To get the Crashplan GUI to connect from Windows I had to delete .ui_info from the PC and reinstall crashplan 4.4.1. It seems the that the format of .ui_info has changed at 4.4.1. Also it looks like you don't need to set the port in .ui_<username>.properties anymore, as you had to in 4.3. Following the rest of the crashplan headless instructions to set the secuirty token worked: http://support.code42.com/CrashPlan/Latest/Configuring/Using_CrashPlan_On_A_Headless_Computer.