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

Slave goes offline when running as windows service

    Details

    • Similar Issues:

      Description

      Build_Slave-1 [Jenkins]
      Connection was broken
      java.io.EOFException at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:614) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748)

        Attachments

          Activity

          Hide
          anoopkv39 Anoop Kv added a comment -

          Mark Waite Can you help me with more details on - "use ssh public key / private key pairs to access your git repository instead of https."?

          Show
          anoopkv39 Anoop Kv added a comment - Mark Waite Can you help me with more details on - "use ssh public key / private key pairs to access your git repository instead of https."?
          Hide
          markewaite Mark Waite added a comment -

          Git repositories are commonly accessed either through the https (or http) protocol or through the ssh protocol. The protocol is selected by URL of the remote repository.

          If your repository url starts with "https" or with "http", then it is using https (or http) protocol. The https protocol with the Jenkins git plugin accepts username / password credentials only. Any other credential type (like public key / private key) will not work.

          If your repository url does not start with "https" and does not start with "http", then it is most likely using ssh protocol. The ssh protocol with the Jenkins git plugin accepts public key / private key credentials only. Any other credential type (like username / password) will not work. Some examples of ssh URL's include mwaite@example.com:/srv/git/my-repo.git, git@github.com:MarkEWaite/git-plugin.git, ssh://mwaite@example.com/srv/git/my-repo.git, and more. Additional examples of URL specification syntax are available from the git documentation.

          Show
          markewaite Mark Waite added a comment - Git repositories are commonly accessed either through the https (or http) protocol or through the ssh protocol. The protocol is selected by URL of the remote repository. If your repository url starts with "https" or with "http", then it is using https (or http) protocol. The https protocol with the Jenkins git plugin accepts username / password credentials only. Any other credential type (like public key / private key) will not work. If your repository url does not start with "https" and does not start with "http", then it is most likely using ssh protocol. The ssh protocol with the Jenkins git plugin accepts public key / private key credentials only. Any other credential type (like username / password) will not work. Some examples of ssh URL's include mwaite@example.com:/srv/git/my-repo.git , git@github.com:MarkEWaite/git-plugin.git , ssh://mwaite@example.com/srv/git/my-repo.git , and more. Additional examples of URL specification syntax are available from the git documentation.
          Hide
          anoopkv39 Anoop Kv added a comment -

          I am getting below error very frequently while running the build job. Is there a way to fix this? Running slave as a windows service.
          Agent went offline during the build
          ERROR: Connection was broken: java.io.EOFException
          at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:614)
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
          at java.util.concurrent.FutureTask.run(FutureTask.java:266)
          at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
          at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
          at java.util.concurrent.FutureTask.run(FutureTask.java:266)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
          at java.lang.Thread.run(Thread.java:748)
          Build step 'Windows PowerShell' marked build as failure

          Show
          anoopkv39 Anoop Kv added a comment - I am getting below error very frequently while running the build job. Is there a way to fix this? Running slave as a windows service. Agent went offline during the build ERROR: Connection was broken: java.io.EOFException at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:614) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Build step 'Windows PowerShell' marked build as failure
          Hide
          anoopkv39 Anoop Kv added a comment -

          More logs here. Also, this appears to be happening every time and we are stuck with this.

          FATAL: channel is already closed
          hudson.remoting.ChannelClosedException: channel is already closed
          at hudson.remoting.Channel.send(Channel.java:578)
          at hudson.remoting.Request.call(Request.java:130)
          at hudson.remoting.Channel.call(Channel.java:796)
          at hudson.Launcher$RemoteLauncher.kill(Launcher.java:953)
          at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:540)
          at hudson.model.Run.execute(Run.java:1720)
          at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
          at hudson.model.ResourceController.execute(ResourceController.java:98)
          at hudson.model.Executor.run(Executor.java:404)
          Caused by: java.io.EOFException
          at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:614)
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
          at java.util.concurrent.FutureTask.run(FutureTask.java:266)
          at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
          at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
          at java.util.concurrent.FutureTask.run(FutureTask.java:266)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
          at java.lang.Thread.run(Thread.java:748)
          Started calculate disk usage of build
          Finished Calculation of disk usage of build in 0 seconds

          Show
          anoopkv39 Anoop Kv added a comment - More logs here. Also, this appears to be happening every time and we are stuck with this. FATAL: channel is already closed hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:578) at hudson.remoting.Request.call(Request.java:130) at hudson.remoting.Channel.call(Channel.java:796) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:953) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:540) at hudson.model.Run.execute(Run.java:1720) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Caused by: java.io.EOFException at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:614) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          I do not anticipate to get any time for Remoting maintenance in next few months, so I am going to unassign the issue. Everybody is welcome to work on that.

          Show
          oleg_nenashev Oleg Nenashev added a comment - I do not anticipate to get any time for Remoting maintenance in next few months, so I am going to unassign the issue. Everybody is welcome to work on that.

            People

            • Assignee:
              Unassigned
              Reporter:
              anoopkv39 Anoop Kv
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: