Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-31050

Slave goes offline during the build

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • remoting
    • None

      The slave goes offline during the job execution and throws the error as mentioned below

      Slave went offline during the build
      01:20:15 ERROR: Connection was broken: java.io.EOFException
      01:20:15 at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:613)
      01:20:15 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
      01:20:15 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
      01:20:15 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
      01:20:15 at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
      01:20:15 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
      01:20:15 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
      01:20:15 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
      01:20:15 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
      01:20:15 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
      01:20:15 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
      01:20:15 at java.lang.Thread.run(Thread.java:724)
      01:20:15

          [JENKINS-31050] Slave goes offline during the build

          Sujith Dinakar created issue -

          Sujith Dinakar added a comment -

          I have found few jira issues realted to this but I do not see a fix or a workaround for the same. Please let me know if you require more information on this.

          Sujith Dinakar added a comment - I have found few jira issues realted to this but I do not see a fix or a workaround for the same. Please let me know if you require more information on this.

          Sujith Dinakar added a comment -

          Also I see this issue on multiple slaves, currently its blocking us.

          Sujith Dinakar added a comment - Also I see this issue on multiple slaves, currently its blocking us.

          Sujith Dinakar added a comment -

          Does anyone even look at these defects? May I have an update please?

          Sujith Dinakar added a comment - Does anyone even look at these defects? May I have an update please?

          Kevin Navero added a comment -

          I'm getting the same problem on Jenkins 1.625.1 LTS. The configuration I have set up is that I have a slave node running Windows 7 natively which is running a Windows Server 2003 virtual machine. The slave-agent client is running on the virtual machine. The Windows Server 2003 VM is running java version 1.7.0_80. Let me know if I can supply more information.

          Kevin Navero added a comment - I'm getting the same problem on Jenkins 1.625.1 LTS. The configuration I have set up is that I have a slave node running Windows 7 natively which is running a Windows Server 2003 virtual machine. The slave-agent client is running on the virtual machine. The Windows Server 2003 VM is running java version 1.7.0_80. Let me know if I can supply more information.

          charles s added a comment -

          Same issue here for a couple of months. Our jenkins script triggers Java ProcessBuilder and redirect IO then the issue appears.

          charles s added a comment - Same issue here for a couple of months. Our jenkins script triggers Java ProcessBuilder and redirect IO then the issue appears.

          Fernando Abad added a comment -

          I had the same issue, it was because other process (automatic testing) was killing the Java process in the slave machine.

          Fernando Abad added a comment - I had the same issue, it was because other process (automatic testing) was killing the Java process in the slave machine.

          Roberto Flores added a comment -

          Hi Fernando, it seems I'm having this same problem. How did you get around it? Would really appreciate your help on this

          Roberto Flores added a comment - Hi Fernando, it seems I'm having this same problem. How did you get around it? Would really appreciate your help on this

          Fernando Abad added a comment -

          We use jenkins slave to run UFT automatic test. (500 Test cases) a few of them had a "TSKILL java" in the code. Review that no one of process that you are runing in the slave machine is not killing java proces.

          I think this error is displayed when java process on the slave machine is clodes suddenly.

          Fernando Abad added a comment - We use jenkins slave to run UFT automatic test. (500 Test cases) a few of them had a "TSKILL java" in the code. Review that no one of process that you are runing in the slave machine is not killing java proces. I think this error is displayed when java process on the slave machine is clodes suddenly.

          Todd B added a comment - - edited

          I have been seeing this too on Windows based VMs. The Node VM is not being reset so it must just the Jenkins service that is crashing and restarting. I am seeing this as much as twice a day since some of the jobs run at the start of node. This is really bad when it happen mid job and logging the message Slave goes offline during the build.

          Todd B added a comment - - edited I have been seeing this too on Windows based VMs. The Node VM is not being reset so it must just the Jenkins service that is crashing and restarting. I am seeing this as much as twice a day since some of the jobs run at the start of node. This is really bad when it happen mid job and logging the message Slave goes offline during the build.

            Unassigned Unassigned
            nutcracker66 Sujith Dinakar
            Votes:
            24 Vote for this issue
            Watchers:
            31 Start watching this issue

              Created:
              Updated: