Suddenly cant push to roborio

[popcorn107]

Last night we attempted loading new code to our roborio. The night before we could push fine but now we keep getting told that no process in pidfile found. We tried re imaging the roborio and installing java again and the message persists. I have also updated all software after we got started getting this. The program is building sucsefully and locating the roborio on the network. We get two different errors normally.

Here are the two different build logs:

Buildfile: C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\build.xml
Trying to override old definition of task classloader
clean:
   [delete] Deleting directory C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\build
   [delete] Deleting directory C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\dist
compile:
    [mkdir] Created dir: C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\build
     [echo] [athena-compile] Compiling src with classpath=C:\Users\Brian/wpilib/java/current/lib/WPILib.jar:C:\Users\Brian/wpilib/java/current/lib/NetworkTables.jar to build
    [javac] Compiling 1 source file to C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\build
jar:
     [echo] [athena-jar] Making jar dist/FRCUserProgram.jar.
    [mkdir] Created dir: C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\dist
    [mkdir] Created dir: C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\build\jars
     [echo] [athena-jar] Copying jars from C:\Users\Brian/wpilib/java/current/lib/WPILib.jar:C:\Users\Brian/wpilib/java/current/lib/NetworkTables.jar to build/jars.
     [copy] Copying 2 files to C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\build\jars
      [jar] Building jar: C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\dist\FRCUserProgram.jar
get-target-ip:
     [echo] Trying Target: roboRIO-2386.local
     [echo] roboRIO found via mDNS
dependencies:
     [echo] roboRIO image version validated
     [echo] Checking for JRE. If this fails install the JRE using these instructions: https://wpilib.screenstepslive.com/s/4485/m/13503/l/288822-installing-java-8-on-the-roborio-using-the-frc-roborio-java-installer-java-only
  [sshexec] Connecting to roboRIO-2386.local:22
  [sshexec] cmd : test -d /usr/local/frc/JRE
deploy:
     [echo] [athena-deploy] Copying code over.
      [scp] Connecting to roboRIO-2386.local:22
      [scp] done.
  [sshexec] Connecting to roboRIO-2386.local:22
  [sshexec] cmd : killall netconsole-host
  [sshexec] killall: netconsole-host: no process killed
  [sshexec] Remote command failed with exit status 1
      [scp] Connecting to roboRIO-2386.local:22
      [scp] done.
      [scp] Connecting to roboRIO-2386.local:22
      [scp] done.
     [echo] [athena-deploy] Starting program.
  [sshexec] Connecting to roboRIO-2386.local:22
  [sshexec] cmd : . /etc/profile.d/natinst-path.sh; /usr/local/frc/bin/frcKillRobot.sh -t -r;
  [sshexec] no process in pidfile '/var/run/natinst/FRC_UserProgram.pid' found; none killed
BUILD SUCCESSFUL
Total time: 17 seconds

and:

Buildfile: C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\build.xml
Trying to override old definition of task classloader
clean:
   [delete] Deleting directory C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\build
   [delete] Deleting directory C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\dist
compile:
    [mkdir] Created dir: C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\build
     [echo] [athena-compile] Compiling src with classpath=C:\Users\Brian/wpilib/java/current/lib/WPILib.jar:C:\Users\Brian/wpilib/java/current/lib/NetworkTables.jar to build
    [javac] Compiling 1 source file to C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\build
jar:
     [echo] [athena-jar] Making jar dist/FRCUserProgram.jar.
    [mkdir] Created dir: C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\dist
    [mkdir] Created dir: C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\build\jars
     [echo] [athena-jar] Copying jars from C:\Users\Brian/wpilib/java/current/lib/WPILib.jar:C:\Users\Brian/wpilib/java/current/lib/NetworkTables.jar to build/jars.
     [copy] Copying 2 files to C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\build\jars
      [jar] Building jar: C:\Users\Brian\Documents\Central Schoolwork\Robotics\frc 2015\programming\Teleop\dist\FRCUserProgram.jar
get-target-ip:
     [echo] Trying Target: roboRIO-2386.local
     [echo] roboRIO found via mDNS
dependencies:
     [echo] roboRIO image version validated
     [echo] Checking for JRE. If this fails install the JRE using these instructions: https://wpilib.screenstepslive.com/s/4485/m/13503/l/288822-installing-java-8-on-the-roborio-using-the-frc-roborio-java-installer-java-only
  [sshexec] Connecting to roboRIO-2386.local:22
  [sshexec] cmd : test -d /usr/local/frc/JRE
deploy:
     [echo] [athena-deploy] Copying code over.
      [scp] Connecting to roboRIO-2386.local:22
      [scp] done.
  [sshexec] Connecting to roboRIO-2386.local:22
  [sshexec] cmd : killall netconsole-host
      [scp] Connecting to roboRIO-2386.local:22
      [scp] done.
      [scp] Connecting to roboRIO-2386.local:22
      [scp] done.
     [echo] [athena-deploy] Starting program.
  [sshexec] Connecting to roboRIO-2386.local:22
  [sshexec] cmd : . /etc/profile.d/natinst-path.sh; /usr/local/frc/bin/frcKillRobot.sh -t -r;
  [sshexec] start-stop-daemon: warning: killing process 1795: No such process
BUILD SUCCESSFUL
Total time: 15 seconds

[GeeTwo]

There's probably a simpler solution, but we had that about a week ago, and after an hour or two of futzing with it we decided to re-image the 'RIO.

[popcorn107]

Originally Posted by GeeTwo

There's probably a simpler solution, but we had that about a week ago, and after an hour or two of futzing with it we decided to re-image the 'RIO.

This was one of the first things we attempted. We re imaged the rio and put java on it again and still get these error messages.

[Jared]

Both logs show a successful upload.

During the upload process, the roboRIO attempts to stop the previous version of the robot code, but it fails to do so. This may be because your code is crashing or there is an exception that causes the user program to stop running. This may also be because you have just reimaged the roborio and there is no code running yet.

[cad321]

Not sure what we did but we are now able to push our code to the robot.

[Ben Wolsieffer]

Those errors are normal and can be safely ignored, that is probably why you found that you could deploy code again.

[Brian Selle]

  [sshexec] Remote command failed with exit status 1

We spent a fair amount of time trying to resolve this issue. Re-imaging may fix it for some but I don't think the issue is on the roboRIO, it's on the IDE side. When we synced our code to another machine it deployed fine.

Last night we discovered that it happens every time we try to deploy code the first time after running in debug. Deleting the bin, build, and dist directories for the project resolved the issue.

[Jared]

Originally Posted by Brian Selle

  [sshexec] Remote command failed with exit status 1

We spent a fair amount of time trying to resolve this issue. Re-imaging may fix it for some but I don't think the issue is on the roboRIO, it's on the IDE side. When we synced our code to another machine it deployed fine.

Last night we discovered that it happens every time we try to deploy code the first time after running in debug. Deleting the bin, build, and dist directories for the project resolved the issue.

This isn't an error!

If it says build successful, it's worked.

This simply means that it can't find a normal running robot program to kill during the deploy process. It makes perfect sense because you were previously running a debug program, which is different.

[Brian Selle]

Never said it was an error, but you are correct it is not an error. The first time this appeared we were unable to deploy code to the roboRIO but it was coupled with another issue. Removing the files simply makes the message go away.