roboRio Java installer stuck on untarring

[ming08108]

Anybody else having this issue?

Specifically the java installer in /wpilib/tools gets stuck on untarring. The progress bar stops moving. I lets it run for more than 30 minutes and no progress is made.

[majesticfish]

Hi
I'm having the exact same problem. It simply gets stuck after connecting. I've looked into this with wireshark and it seems that after acknowledging the roborio, no more packets are sent through the interface.

[Team3266Spencer]

I had a similar issue. Power cycling the rRIO fixed the issue for me.

[fsilberberg]

Originally Posted by ming08108

Anybody else having this issue?

Specifically the java installer in /wpilib/tools gets stuck on untarring. The progress bar stops moving. I lets it run for more than 30 minutes and no progress is made.

Originally Posted by majesticfish

Hi
I'm having the exact same problem. It simply gets stuck after connecting. I've looked into this with wireshark and it seems that after acknowledging the roborio, no more packets are sent through the interface.

The installer makes a log file, located in /wpilib/tools/logs/javainstaller.log. Could you please post that log?

[Fauge7]

When in doubt cycle power! Or reflash the firmware on the robotRIO. Then Try it.

[majesticfish]

Hi. I fixed the problem by imaging the roborio.

[ming08108]

Originally Posted by fsilberberg

The installer makes a log file, located in /wpilib/tools/logs/javainstaller.log. Could you please post that log?

09/Jan/2015 16:58:08,931- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/hijrah-config-umalqura.properties, putting tar entry is JRE/lib/hijrah-config-umalqura.properties
09/Jan/2015 16:58:08,932- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/jce.jar, putting tar entry is JRE/lib/jce.jar
09/Jan/2015 16:58:08,938- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/jsse.jar, putting tar entry is JRE/lib/jsse.jar
09/Jan/2015 16:58:08,954- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/jvm.hprof.txt, putting tar entry is JRE/lib/jvm.hprof.txt
09/Jan/2015 16:58:08,954- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/logging.properties, putting tar entry is JRE/lib/logging.properties
09/Jan/2015 16:58:08,955- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/meta-index, putting tar entry is JRE/lib/meta-index
09/Jan/2015 16:58:08,955- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/net.properties, putting tar entry is JRE/lib/net.properties
09/Jan/2015 16:58:08,956- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/resources.jar, putting tar entry is JRE/lib/resources.jar
09/Jan/2015 16:58:08,983- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/rt.jar, putting tar entry is JRE/lib/rt.jar
09/Jan/2015 16:58:09,660- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/security, putting tar entry is JRE/lib/security
09/Jan/2015 16:58:09,660- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/security/blacklist, putting tar entry is JRE/lib/security/blacklist
09/Jan/2015 16:58:09,661- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/security/cacerts, putting tar entry is JRE/lib/security/cacerts
09/Jan/2015 16:58:09,664- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/security/java.policy, putting tar entry is JRE/lib/security/java.policy
09/Jan/2015 16:58:09,664- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/security/java.security, putting tar entry is JRE/lib/security/java.security
09/Jan/2015 16:58:09,665- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/security/local_policy.jar, putting tar entry is JRE/lib/security/local_policy.jar
09/Jan/2015 16:58:09,666- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/security/trusted.libraries, putting tar entry is JRE/lib/security/trusted.libraries
09/Jan/2015 16:58:09,666- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/security/US_export_policy.jar, putting tar entry is JRE/lib/security/US_export_policy.jar
09/Jan/2015 16:58:09,666- DeployController: Processing file /Users/a/wpilib/tools/JRE/lib/tzdb.dat, putting tar entry is JRE/lib/tzdb.dat
09/Jan/2015 16:58:09,671- DeployController: Processing file /Users/a/wpilib/tools/JRE/release, putting tar entry is JRE/release
09/Jan/2015 16:58:09,767- DeployController: Failure to send JRE to the roboRio
com.jcraft.jsch.JSchException: java.net.ConnectException: Connection refused
at com.jcraft.jsch.Util.createSocket(Util.java:349) ~[java-installer.jar:?]
at com.jcraft.jsch.Session.connect(Session.java:215) ~[java-installer.jar:?]
at com.jcraft.jsch.Session.connect(Session.java:183) ~[java-installer.jar:?]
at edu.wpi.first.wpilib.javainstaller.Controllers.Dep loyController.lambda$initialize$10(DeployControlle r.java:85) [java-installer.jar:?]
at edu.wpi.first.wpilib.javainstaller.Controllers.Dep loyController$$Lambda$165/216870574.run(Unknown Source) [java-installer.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_25]
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:1.8.0_25]
at java.net.AbstractPlainSocketImpl.doConnect(Abstrac tPlainSocketImpl.java:345) ~[?:1.8.0_25]
at java.net.AbstractPlainSocketImpl.connectToAddress( AbstractPlainSocketImpl.java:206) ~[?:1.8.0_25]
at java.net.AbstractPlainSocketImpl.connect(AbstractP lainSocketImpl.java:188) ~[?:1.8.0_25]
at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:392) ~[?:1.8.0_25]
at java.net.Socket.connect(Socket.java:589) ~[?:1.8.0_25]
at java.net.Socket.connect(Socket.java:538) ~[?:1.8.0_25]
at java.net.Socket.<init>(Socket.java:434) ~[?:1.8.0_25]
at java.net.Socket.<init>(Socket.java:211) ~[?:1.8.0_25]
at com.jcraft.jsch.Util.createSocket(Util.java:343) ~[java-installer.jar:?]
... 5 more
10/Jan/2015 12:47:19,742- MainApp: Exiting installer from popup

[fsilberberg]

That looks like the roboRIO is not imaged. Could you try to format it with the ni image tool and then try to install Java again?

[ming08108]

Originally Posted by fsilberberg

That looks like the roboRIO is not imaged. Could you try to format it with the ni image tool and then try to install Java again?

I imaged it but I guess I can reset and try it again from the beginning on monday. Will let you know how it goes.

[JacobD]

Originally Posted by fsilberberg

That looks like the roboRIO is not imaged. Could you try to format it with the ni image tool and then try to install Java again?

I had the same problem. If imaging does not fix the problem, ensure that you are connected to the roboRIO network. You cannot just use the USB.

[Ozuru]

Honestly, the entire Java installer seemed fairly problematic. Make sure you're running it as administrator and make sure that your roboRIO is imaged and you should be fine.

[fsilberberg]

Originally Posted by JacobD

I had the same problem. If imaging does not fix the problem, ensure that you are connected to the roboRIO network. You cannot just use the USB.

We tested it on all network connections, it will fall back to the static USB and old-style 10.te.am.2 ip address if it can't find the roboRIO via mDNS.

Originally Posted by Ozuru

Honestly, the entire Java installer seemed fairly problematic. Make sure you're running it as administrator and make sure that your roboRIO is imaged and you should be fine.

What was overly problematic? Is there anything I can change to make it easier to use?

[ming08108]

Originally Posted by JacobD

I had the same problem. If imaging does not fix the problem, ensure that you are connected to the roboRIO network. You cannot just use the USB.

I had problems with imaging and had to call NI support. They told me to re image it over ethernet and that fixed the issue for some reason. Anybody know why?

[tStano]

I have no idea why. This happened to me as well when I was attempting to install off a flash drive. Once I put the file on my computer instead, it inexplicably worked.

[katabeta]

Had the same problem. Doing everything over ethernet and re-imaging the roboRio fixed it.