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

slave is getting disconnected in the middle of the job

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Blocker Blocker
    • remoting
    • None
    • Production

      FATAL: command execution failedFATAL: command execution failedjava.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:209) at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doCloseSend(ProtocolStack.java:800) at org.jenkinsci.remoting.protocol.ApplicationLayer.doCloseWrite(ApplicationLayer.java:173) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.closeWrite(ChannelApplicationLayer.java:314) at hudson.remoting.Channel.close(Channel.java:1450) at hudson.remoting.Channel.close(Channel.java:1403) at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:821) at hudson.slaves.SlaveComputer.access$800(SlaveComputer.java:105) at hudson.slaves.SlaveComputer$3.run(SlaveComputer.java:737) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) 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)Caused: java.io.IOException: Backing channel 'JNLP4-connect connection from myip/myip:49165' is disconnected. at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:214) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283) at com.sun.proxy.$Proxy128.isAlive(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1137) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1129) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)FATAL: Unable to delete script file C:\Windows\TEMP\jenkins880525539975639792.ps1java.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:209) at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doCloseSend(ProtocolStack.java:800) at org.jenkinsci.remoting.protocol.ApplicationLayer.doCloseWrite(ApplicationLayer.java:173) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.closeWrite(ChannelApplicationLayer.java:314) at hudson.remoting.Channel.close(Channel.java:1450) at hudson.remoting.Channel.close(Channel.java:1403) at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:821) at hudson.slaves.SlaveComputer.access$800(SlaveComputer.java:105) at hudson.slaves.SlaveComputer$3.run(SlaveComputer.java:737) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) 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)Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from Myip/Myip:49165 failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:948) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at hudson.FilePath.delete(FilePath.java:1563) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:123) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Build step 'Windows PowerShell' marked build as failure[htmlpublisher] Archiving HTML reports...ERROR: Build step failed with exceptionjava.lang.NullPointerException at htmlpublisher.HtmlPublisher.publishReports(HtmlPublisher.java:226) at htmlpublisher.HtmlPublisher.perform(HtmlPublisher.java:193) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1840) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Build step 'Publish HTML reports' marked build as failureERROR: Step �Publish NUnit test result report� failed: no workspace for morpheus_qa_intgr_incentive #614Email was triggered for: AlwaysSending email for trigger: AlwaysERROR: Error: No workspace found!Sending email to: sumanthnathConnection error sending email, retrying once more in 10 seconds...Connection error sending email, retrying once more in 10 seconds...Failed after second try sending emailFinished: FAILURE

          [JENKINS-52922] slave is getting disconnected in the middle of the job

          Hi Team,

          Can I get help on this issue. If you need any further information please comment in this thread, I will provide you the details.

          Thanks & Regards
          Sumanthnath G

          sumanthnath gangavarapu added a comment - Hi Team, Can I get help on this issue. If you need any further information please comment in this thread, I will provide you the details. Thanks & Regards Sumanthnath G

          Hi Team,

          This is a complete blocker for us.
          Can you please look into this on priority.

          Thanks & Regards
          Sumanthnath G

          sumanthnath gangavarapu added a comment - Hi Team, This is a complete blocker for us. Can you please look into this on priority. Thanks & Regards Sumanthnath G

          sumanthnath gangavarapu added a comment - - edited

          jthompson 00500005 0000144223 007g3m1n1 abang 0007924021 000panther 0023 fdnsjdghjhb alhen123 abhijitpaul_02 brunohe bode delphboy ajeng

          Can anyone of you please guide me how can we resolve this issue.
          I have opened this ticket one month before anticipating help from this team.
          Please guide me if I have missed anything in the process to get help.
          Thank you
          Sumanth

          sumanthnath gangavarapu added a comment - - edited jthompson 00500005 0000144223 007g3m1n1 abang 0007924021 000panther 0023 fdnsjdghjhb alhen123 abhijitpaul_02 brunohe bode delphboy ajeng Can anyone of you please guide me how can we resolve this issue. I have opened this ticket one month before anticipating help from this team. Please guide me if I have missed anything in the process to get help. Thank you Sumanth

          Jeff Thompson added a comment -

          sumanthnathg, there isn't enough information in your report to perform a meaningful diagnosis. A ClosedChannelException merely indicates that the channel the agent and master were communicating on has been closed. Nothing in the report provides any indication as to how or why the channel was closed.

          Generally, these sorts of failures are due to system or environment issues. It isn't a problem in the code but something external that causes the connection to close. You should investigate your systems and networks so that you can isolate and determine the cause of the failure.

          A short, abbreviated sample of the things you should examine:

          1. Check agent logs.
          2. Check master logs.
          3. Check system logs, such as Windows Event logs.
          4. Look for high resource usage (CPU, disk, network, etc.) on master and agent machines.
          5. Investigate network issues.
          6. Look for any commonalities among the failures such as
            1. Time of day
            2. Duration of job
            3. Operating system
            4. System uptime
          7. Check the health and logs of the hosting environments.
          8. Match all of the timestamps and events up together with the failures to try and develop a picture of what is occurring.

          As a simple example, I saw some similar behavior on my Windows machine when it decided it was time to go to sleep. (Windows server OSes don't usually have this behavior.)

          I'm sorry that I'm not able to solve this problem for you, but the investigation needs to be performed at your end. If you manage to figure out the cause, I'd be curious to learn what you discovered.

          Jeff Thompson added a comment - sumanthnathg , there isn't enough information in your report to perform a meaningful diagnosis. A ClosedChannelException merely indicates that the channel the agent and master were communicating on has been closed. Nothing in the report provides any indication as to how or why the channel was closed. Generally, these sorts of failures are due to system or environment issues. It isn't a problem in the code but something external that causes the connection to close. You should investigate your systems and networks so that you can isolate and determine the cause of the failure. A short, abbreviated sample of the things you should examine: Check agent logs. Check master logs. Check system logs, such as Windows Event logs. Look for high resource usage (CPU, disk, network, etc.) on master and agent machines. Investigate network issues. Look for any commonalities among the failures such as Time of day Duration of job Operating system System uptime Check the health and logs of the hosting environments. Match all of the timestamps and events up together with the failures to try and develop a picture of what is occurring. As a simple example, I saw some similar behavior on my Windows machine when it decided it was time to go to sleep. (Windows server OSes don't usually have this behavior.) I'm sorry that I'm not able to solve this problem for you, but the investigation needs to be performed at your end. If you manage to figure out the cause, I'd be curious to learn what you discovered.

          Hi jthompson

          Thanks for your reply.
          Here is what I did as a part of troubleshooting.
          I ran the powershell script which attempted to connect to the Linux server via 443 over and over and over again. I also changed it to 49187 after a reboot. The entire time we ran this we did not see it drop once. I believe we have layer 4 communication down.

          while ($true)

          {     "$(Get-Date);$(Test-netconnection -ComputerName <MasterNodeIP> -port 443 -informationlevel quiet)" }

          Next I went ahead and pushed a 5GB file via SCP from the Windows slave server to the Linux master server. The data was able to arrive on the server without an issue. I believe we have layer 7 communication down as well.

          I also ran the job and did some netstat information on both ends, seeing communication back and forth.

          As you have suggested I have checked for CPU memory issues and disc space issues and they are normal. I have captured logs can you please take a look at them.

          Java Log from Slave node:
          Java Web Start 11.181.2.13 x86Java Web Start 11.181.2.13 x86Using JRE version 1.8.0_181-b13 Java HotSpot(TM) Client VMUser home directory = C:\Users\saadmin---------------------------------------------------c:   clear console windowf:   finalize objects on finalization queueg:   garbage collecth:   display this help messagem:   print memory usageo:   trigger loggingp:   reload proxy configurationq:   hide consoler:   reload policy configurations:   dump system and deployment propertiest:   dump thread listv:   dump thread stack0-5: set trace level to <n>---------------------------------------------------Sep 10, 2018 2:07:12 PM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: jenkins2-win-slaveSep 10, 2018 2:07:12 PM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.25Sep 10, 2018 2:07:12 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDirINFO: Using C:\Jenkins\remoting as a remoting work directoryBoth error and output logs will be printed to C:\Jenkins\remotingSep 10, 2018 2:07:12 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Sep 10, 2018 2:07:12 PM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to ci.kantarworldpanel.com/<MasterNodeIP>:49187] Local headers refused by remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 10, 2018 2:07:12 PM hudson.remoting.jnlp.GuiListener$1 runINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more
          Sep 10, 2018 2:07:13 PM hudson.remoting.jnlp.GuiListener$2 runSEVERE: The server rejected the connection: None of the protocols were acceptedjava.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:675) at hudson.remoting.Engine.innerRun(Engine.java:639) at hudson.remoting.Engine.run(Engine.java:474)
          Sep 10, 2018 2:07:23 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Sep 10, 2018 2:07:23 PM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to ci.kantarworldpanel.com/<MasterNodeIP>:49187] Local headers refused by remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 10, 2018 2:07:23 PM hudson.remoting.jnlp.GuiListener$1 runINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more
          Sep 10, 2018 2:07:23 PM hudson.remoting.jnlp.GuiListener$2 runSEVERE: The server rejected the connection: None of the protocols were acceptedjava.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:675) at hudson.remoting.Engine.innerRun(Engine.java:639) at hudson.remoting.Engine.run(Engine.java:474)
          Sep 10, 2018 2:07:33 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Sep 10, 2018 2:07:33 PM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to ci.kantarworldpanel.com/<MasterNodeIP>:49187] Local headers refused by remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 10, 2018 2:07:33 PM hudson.remoting.jnlp.GuiListener$1 runINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more
          Sep 10, 2018 2:07:33 PM hudson.remoting.jnlp.GuiListener$2 runSEVERE: The server rejected the connection: None of the protocols were acceptedjava.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:675) at hudson.remoting.Engine.innerRun(Engine.java:639) at hudson.remoting.Engine.run(Engine.java:474)
          Sep 10, 2018 2:07:43 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Sep 10, 2018 2:07:43 PM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to ci.kantarworldpanel.com/<MasterNodeIP>:49187] Local headers refused by remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 10, 2018 2:07:43 PM hudson.remoting.jnlp.GuiListener$1 runINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more
          Sep 10, 2018 2:07:43 PM hudson.remoting.jnlp.GuiListener$2 runSEVERE: The server rejected the connection: None of the protocols were acceptedjava.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:675) at hudson.remoting.Engine.innerRun(Engine.java:639) at hudson.remoting.Engine.run(Engine.java:474)

          Jenkins Master Logs:
          Sep 12, 2018 2:56:40 AM hudson.TcpSlaveAgentListener$ConnectionHandler runSep 12, 2018 2:56:40 AM hudson.TcpSlaveAgentListener$ConnectionHandler runINFO: Accepted JNLP4-connect connection #394,549 from /<SlaveNodeIP>:63482Sep 12, 2018 2:56:40 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection from <SlaveNodeIP>/<SlaveNodeIP>:63482] Refusing headers from remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 12, 2018 2:56:41 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #394550 failedjava.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) at sun.nio.ch.IOUtil.read(IOUtil.java:197) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:192) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) at java.io.DataInputStream.readFully(DataInputStream.java:195) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242)
          Sep 12, 2018 2:56:42 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #394551 failedjava.io.EOFException at java.io.DataInputStream.readFully(DataInputStream.java:197) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242)
          Sep 12, 2018 2:56:42 AM hudson.TcpSlaveAgentListener$ConnectionHandler runINFO: Accepted JNLP4-connect connection #394,552 from /<SlaveNodeIP>:63490Sep 12, 2018 2:56:42 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection from <SlaveNodeIP>/<SlaveNodeIP>:63490] Refusing headers from remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 12, 2018 2:56:43 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #394553 failedjava.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) at sun.nio.ch.IOUtil.read(IOUtil.java:197) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:192) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) at java.io.DataInputStream.readFully(DataInputStream.java:195) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242)
          Sep 12, 2018 2:56:45 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #394554 failedjava.io.EOFException at java.io.DataInputStream.readFully(DataInputStream.java:197) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242)
          Sep 12, 2018 2:56:45 AM hudson.TcpSlaveAgentListener$ConnectionHandler runINFO: Accepted JNLP4-connect connection #394,555 from /<SlaveNodeIP>:63498Sep 12, 2018 2:56:45 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection from <SlaveNodeIP>/<SlaveNodeIP>:63498] Refusing headers from remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 12, 2018 2:56:46 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #394556 failedjava.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) at sun.nio.ch.IOUtil.read(IOUtil.java:197) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:192) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) at java.io.DataInputStream.readFully(DataInputStream.java:195) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242)
          Sep 12, 2018 2:56:47 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #394557 failedjava.io.EOFException at java.io.DataInputStream.readFully(DataInputStream.java:197) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242)
          Sep 12, 2018 2:56:48 AM hudson.TcpSlaveAgentListener$ConnectionHandler runINFO: Accepted JNLP4-connect connection #394,558 from /<SlaveNodeIP>:63506Sep 12, 2018 2:56:48 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection from <SlaveNodeIP>/<SlaveNodeIP>:63506] Refusing headers from remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 12, 2018 2:56:48 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #394559 failedjava.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) at sun.nio.ch.IOUtil.read(IOUtil.java:197) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:192) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) at java.io.DataInputStream.readFully(DataInputStream.java:195) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242)
          Sep 12, 2018 2:56:50 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #394560 failedjava.io.EOFException at java.io.DataInputStream.readFully(DataInputStream.java:197) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242)

          ++

           

          sumanthnath gangavarapu added a comment - Hi jthompson ,  Thanks for your reply. Here is what I did as a part of troubleshooting. I ran the powershell script which attempted to connect to the Linux server via 443 over and over and over again. I also changed it to 49187 after a reboot. The entire time we ran this we did not see it drop once. I believe we have layer 4 communication down. while ($true) {     "$(Get-Date);$(Test-netconnection -ComputerName <MasterNodeIP> -port 443 -informationlevel quiet)" } Next I went ahead and pushed a 5GB file via SCP from the Windows slave server to the Linux master server. The data was able to arrive on the server without an issue. I believe we have layer 7 communication down as well. I also ran the job and did some netstat information on both ends, seeing communication back and forth. As you have suggested I have checked for CPU memory issues and disc space issues and they are normal. I have captured logs can you please take a look at them. Java Log from Slave node: Java Web Start 11.181.2.13 x86Java Web Start 11.181.2.13 x86Using JRE version 1.8.0_181-b13 Java HotSpot(TM) Client VMUser home directory = C:\Users\saadmin--------------------------------------------------- c:   clear console windowf:   finalize objects on finalization queueg:   garbage collecth:   display this help messagem:   print memory usageo:   trigger loggingp:   reload proxy configurationq:   hide consoler:   reload policy configurations:   dump system and deployment propertiest:   dump thread listv:   dump thread stack0-5: set trace level to <n> ---------------------------------------------------Sep 10, 2018 2:07:12 PM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: jenkins2-win-slaveSep 10, 2018 2:07:12 PM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.25Sep 10, 2018 2:07:12 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDirINFO: Using C:\Jenkins\remoting as a remoting work directoryBoth error and output logs will be printed to C:\Jenkins\remotingSep 10, 2018 2:07:12 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Sep 10, 2018 2:07:12 PM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to ci.kantarworldpanel.com/<MasterNodeIP>:49187] Local headers refused by remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 10, 2018 2:07:12 PM hudson.remoting.jnlp.GuiListener$1 runINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more Sep 10, 2018 2:07:13 PM hudson.remoting.jnlp.GuiListener$2 runSEVERE: The server rejected the connection: None of the protocols were acceptedjava.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:675) at hudson.remoting.Engine.innerRun(Engine.java:639) at hudson.remoting.Engine.run(Engine.java:474) Sep 10, 2018 2:07:23 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Sep 10, 2018 2:07:23 PM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to ci.kantarworldpanel.com/<MasterNodeIP>:49187] Local headers refused by remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 10, 2018 2:07:23 PM hudson.remoting.jnlp.GuiListener$1 runINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more Sep 10, 2018 2:07:23 PM hudson.remoting.jnlp.GuiListener$2 runSEVERE: The server rejected the connection: None of the protocols were acceptedjava.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:675) at hudson.remoting.Engine.innerRun(Engine.java:639) at hudson.remoting.Engine.run(Engine.java:474) Sep 10, 2018 2:07:33 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Sep 10, 2018 2:07:33 PM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to ci.kantarworldpanel.com/<MasterNodeIP>:49187] Local headers refused by remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 10, 2018 2:07:33 PM hudson.remoting.jnlp.GuiListener$1 runINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more Sep 10, 2018 2:07:33 PM hudson.remoting.jnlp.GuiListener$2 runSEVERE: The server rejected the connection: None of the protocols were acceptedjava.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:675) at hudson.remoting.Engine.innerRun(Engine.java:639) at hudson.remoting.Engine.run(Engine.java:474) Sep 10, 2018 2:07:43 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Sep 10, 2018 2:07:43 PM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to ci.kantarworldpanel.com/<MasterNodeIP>:49187] Local headers refused by remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 10, 2018 2:07:43 PM hudson.remoting.jnlp.GuiListener$1 runINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more Sep 10, 2018 2:07:43 PM hudson.remoting.jnlp.GuiListener$2 runSEVERE: The server rejected the connection: None of the protocols were acceptedjava.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:675) at hudson.remoting.Engine.innerRun(Engine.java:639) at hudson.remoting.Engine.run(Engine.java:474) Jenkins Master Logs: Sep 12, 2018 2:56:40 AM hudson.TcpSlaveAgentListener$ConnectionHandler runSep 12, 2018 2:56:40 AM hudson.TcpSlaveAgentListener$ConnectionHandler runINFO: Accepted JNLP4-connect connection #394,549 from /<SlaveNodeIP>:63482Sep 12, 2018 2:56:40 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection from <SlaveNodeIP>/<SlaveNodeIP>:63482] Refusing headers from remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 12, 2018 2:56:41 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #394550 failedjava.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) at sun.nio.ch.IOUtil.read(IOUtil.java:197) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:192) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) at java.io.DataInputStream.readFully(DataInputStream.java:195) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242) Sep 12, 2018 2:56:42 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #394551 failedjava.io.EOFException at java.io.DataInputStream.readFully(DataInputStream.java:197) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242) Sep 12, 2018 2:56:42 AM hudson.TcpSlaveAgentListener$ConnectionHandler runINFO: Accepted JNLP4-connect connection #394,552 from /<SlaveNodeIP>:63490Sep 12, 2018 2:56:42 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection from <SlaveNodeIP>/<SlaveNodeIP>:63490] Refusing headers from remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 12, 2018 2:56:43 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #394553 failedjava.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) at sun.nio.ch.IOUtil.read(IOUtil.java:197) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:192) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) at java.io.DataInputStream.readFully(DataInputStream.java:195) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242) Sep 12, 2018 2:56:45 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #394554 failedjava.io.EOFException at java.io.DataInputStream.readFully(DataInputStream.java:197) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242) Sep 12, 2018 2:56:45 AM hudson.TcpSlaveAgentListener$ConnectionHandler runINFO: Accepted JNLP4-connect connection #394,555 from /<SlaveNodeIP>:63498Sep 12, 2018 2:56:45 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection from <SlaveNodeIP>/<SlaveNodeIP>:63498] Refusing headers from remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 12, 2018 2:56:46 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #394556 failedjava.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) at sun.nio.ch.IOUtil.read(IOUtil.java:197) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:192) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) at java.io.DataInputStream.readFully(DataInputStream.java:195) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242) Sep 12, 2018 2:56:47 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #394557 failedjava.io.EOFException at java.io.DataInputStream.readFully(DataInputStream.java:197) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242) Sep 12, 2018 2:56:48 AM hudson.TcpSlaveAgentListener$ConnectionHandler runINFO: Accepted JNLP4-connect connection #394,558 from /<SlaveNodeIP>:63506Sep 12, 2018 2:56:48 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection from <SlaveNodeIP>/<SlaveNodeIP>:63506] Refusing headers from remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 12, 2018 2:56:48 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #394559 failedjava.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) at sun.nio.ch.IOUtil.read(IOUtil.java:197) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:192) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) at java.io.DataInputStream.readFully(DataInputStream.java:195) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242) Sep 12, 2018 2:56:50 AM hudson.TcpSlaveAgentListener$ConnectionHandler runWARNING: Connection #394560 failedjava.io.EOFException at java.io.DataInputStream.readFully(DataInputStream.java:197) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:242) ++  

          Jenkins Slave Logs:

          Sep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful  Agent address: ci.kantarworldpanel.com  Agent port:    49187  Identity:      2b:ec:57:ae:00:0c:10:39:59:ca:a4:1c:a7:05:46:dcSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to ci.kantarworldpanel.com:49187Sep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 2b:ec:57:ae:00:0c:10:39:59:ca:a4:1c:a7:05:46:dcSep 12, 2018 2:56:01 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to ci.kantarworldpanel.com/<MasterNodeIP>:49187] Local headers refused by remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more
          Sep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to ci.kantarworldpanel.com:49187Sep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP4-plaintext not supported, skippingSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP3-connect not supported, skippingSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP2-connect not supported, skippingSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP-connect not supported, skippingSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener errorSEVERE: The server rejected the connection: None of the protocols were acceptedjava.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:675) at hudson.remoting.Engine.innerRun(Engine.java:639) at hudson.remoting.Engine.run(Engine.java:474)
          Sep 12, 2018 2:56:03 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: jenkins2-win-slaveSep 12, 2018 2:56:03 AM hudson.remoting.jnlp.Main$CuiListener <init>INFO: Jenkins agent is running in headless mode.Sep 12, 2018 2:56:03 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.25Sep 12, 2018 2:56:03 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDirINFO: Using C:\Jenkins\remoting as a remoting work directorySep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among https://ci.kantarworldpanel.com/Sep 12, 2018 2:56:04 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Sep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful  Agent address: ci.kantarworldpanel.com  Agent port:    49187  Identity:      2b:ec:57:ae:00:0c:10:39:59:ca:a4:1c:a7:05:46:dcSep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingSep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to ci.kantarworldpanel.com:49187Sep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectSep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 2b:ec:57:ae:00:0c:10:39:59:ca:a4:1c:a7:05:46:dcSep 12, 2018 2:56:04 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to ci.kantarworldpanel.com/<MasterNodeIP>:49187] Local headers refused by remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more
          Sep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to ci.kantarworldpanel.com:49187Sep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP4-plaintext not supported, skippingSep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP3-connect not supported, skippingSep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP2-connect not supported, skippingSep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP-connect not supported, skippingSep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener errorSEVERE: The server rejected the connection: None of the protocols were acceptedjava.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:675) at hudson.remoting.Engine.innerRun(Engine.java:639) at hudson.remoting.Engine.run(Engine.java:474)
          Sep 12, 2018 2:56:06 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: jenkins2-win-slaveSep 12, 2018 2:56:06 AM hudson.remoting.jnlp.Main$CuiListener <init>INFO: Jenkins agent is running in headless mode.Sep 12, 2018 2:56:06 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.25Sep 12, 2018 2:56:06 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDirINFO: Using C:\Jenkins\remoting as a remoting work directorySep 12, 2018 2:56:06 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among https://ci.kantarworldpanel.com/Sep 12, 2018 2:56:06 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Sep 12, 2018 2:56:06 AM hudson.remoting.jnlp.Main$CuiListener status

          sumanthnath gangavarapu added a comment - Jenkins Slave Logs: Sep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful  Agent address: ci.kantarworldpanel.com  Agent port:    49187  Identity:      2b:ec:57:ae:00:0c:10:39:59:ca:a4:1c:a7:05:46:dcSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to ci.kantarworldpanel.com:49187Sep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 2b:ec:57:ae:00:0c:10:39:59:ca:a4:1c:a7:05:46:dcSep 12, 2018 2:56:01 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to ci.kantarworldpanel.com/<MasterNodeIP>:49187] Local headers refused by remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more Sep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to ci.kantarworldpanel.com:49187Sep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP4-plaintext not supported, skippingSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP3-connect not supported, skippingSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP2-connect not supported, skippingSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP-connect not supported, skippingSep 12, 2018 2:56:01 AM hudson.remoting.jnlp.Main$CuiListener errorSEVERE: The server rejected the connection: None of the protocols were acceptedjava.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:675) at hudson.remoting.Engine.innerRun(Engine.java:639) at hudson.remoting.Engine.run(Engine.java:474) Sep 12, 2018 2:56:03 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: jenkins2-win-slaveSep 12, 2018 2:56:03 AM hudson.remoting.jnlp.Main$CuiListener <init>INFO: Jenkins agent is running in headless mode.Sep 12, 2018 2:56:03 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.25Sep 12, 2018 2:56:03 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDirINFO: Using C:\Jenkins\remoting as a remoting work directorySep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among https://ci.kantarworldpanel.com/ Sep 12, 2018 2:56:04 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Sep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful  Agent address: ci.kantarworldpanel.com  Agent port:    49187  Identity:      2b:ec:57:ae:00:0c:10:39:59:ca:a4:1c:a7:05:46:dcSep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingSep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to ci.kantarworldpanel.com:49187Sep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectSep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 2b:ec:57:ae:00:0c:10:39:59:ca:a4:1c:a7:05:46:dcSep 12, 2018 2:56:04 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to ci.kantarworldpanel.com/<MasterNodeIP>:49187] Local headers refused by remote: jenkins2-win-slave is already connected to this master. Rejecting this connection.Sep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: jenkins2-win-slave is already connected to this master. Rejecting this connection. at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more Sep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to ci.kantarworldpanel.com:49187Sep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP4-plaintext not supported, skippingSep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP3-connect not supported, skippingSep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP2-connect not supported, skippingSep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP-connect not supported, skippingSep 12, 2018 2:56:04 AM hudson.remoting.jnlp.Main$CuiListener errorSEVERE: The server rejected the connection: None of the protocols were acceptedjava.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:675) at hudson.remoting.Engine.innerRun(Engine.java:639) at hudson.remoting.Engine.run(Engine.java:474) Sep 12, 2018 2:56:06 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: jenkins2-win-slaveSep 12, 2018 2:56:06 AM hudson.remoting.jnlp.Main$CuiListener <init>INFO: Jenkins agent is running in headless mode.Sep 12, 2018 2:56:06 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.25Sep 12, 2018 2:56:06 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDirINFO: Using C:\Jenkins\remoting as a remoting work directorySep 12, 2018 2:56:06 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among https://ci.kantarworldpanel.com/ Sep 12, 2018 2:56:06 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Sep 12, 2018 2:56:06 AM hudson.remoting.jnlp.Main$CuiListener status

          Jeff Thompson added a comment -

          I don't know what you intended to convey with those logs, but they don't seem immediately relevant. Perhaps, though, you've got something configured in a way that attempts to create multiple connections to the same agent. I don't see how this would cause the issue you're reporting, but it would be worth investigating. Otherwise, the logs provide nothing useful.

          You mention the SSH Slaves Plugin in your description above. Are you using that to connect to Windows agents? What SSH implementation are you using for Windows?

          This presentation contains further information on diagnosing Remoting connectivity issues. You might be able to find some information in there useful for your troubleshooting exercise. https://speakerdeck.com/onenashev/day-of-jenkins-2017-dealing-with-agent-connectivity-issues

          You could try varying some of your configurations to see if you can isolate components that may be interacting poorly. You could try different types of OSes or system configurations. Instead of using the Windows Slaves plugin you could try some of the other mechanisms for connecting agents on Windows. Does this fail for all jobs on Windows? Or only a subset? You could try different jobs or creating special troubleshooting jobs. You could try experiments at reducing the plugins used on a job. Or the other resources the job uses.

          I'm unable to reproduce this error, because of some difference in our environments or configurations. My long-running Windows job ran for an hour, reaching its proper termination time.

           

          Jeff Thompson added a comment - I don't know what you intended to convey with those logs, but they don't seem immediately relevant. Perhaps, though, you've got something configured in a way that attempts to create multiple connections to the same agent. I don't see how this would cause the issue you're reporting, but it would be worth investigating. Otherwise, the logs provide nothing useful. You mention the SSH Slaves Plugin in your description above. Are you using that to connect to Windows agents? What SSH implementation are you using for Windows? This presentation contains further information on diagnosing Remoting connectivity issues. You might be able to find some information in there useful for your troubleshooting exercise. https://speakerdeck.com/onenashev/day-of-jenkins-2017-dealing-with-agent-connectivity-issues You could try varying some of your configurations to see if you can isolate components that may be interacting poorly. You could try different types of OSes or system configurations. Instead of using the Windows Slaves plugin you could try some of the other mechanisms for connecting agents on Windows. Does this fail for all jobs on Windows? Or only a subset? You could try different jobs or creating special troubleshooting jobs. You could try experiments at reducing the plugins used on a job. Or the other resources the job uses. I'm unable to reproduce this error, because of some difference in our environments or configurations. My long-running Windows job ran for an hour, reaching its proper termination time.  

          Nush Ahmd added a comment -

          We managed to resolve this by adding "-Dhudson.slaves.ChannelPinger.pingInterval=2" to the Jenkins.xml of the master.

           

          The issue was that our tests weren't printing anything out to the console,

          Nush Ahmd added a comment - We managed to resolve this by adding "-Dhudson.slaves.ChannelPinger.pingInterval=2" to the Jenkins.xml of the master.   The issue was that our tests weren't printing anything out to the console,

          Jeff Thompson added a comment -

          nush, thanks for sharing that information. I'm glad it resolved your issue and maybe it will also help others.

          Just a note: hudson.slaves.ChannelPinger.pingInterval was deprecated in Jenkins 2.37. It was replaced by hudson.slaves.ChannelPinger.pingIntervalSeconds. Instead of assigning it a value of 2 in your case, you would want to assign it a value of 120 (seconds).

          Jeff Thompson added a comment - nush , thanks for sharing that information. I'm glad it resolved your issue and maybe it will also help others. Just a note: hudson.slaves.ChannelPinger.pingInterval was deprecated in Jenkins 2.37. It was replaced by hudson.slaves.ChannelPinger.pingIntervalSeconds. Instead of assigning it a value of 2 in your case, you would want to assign it a value of 120 (seconds).

          Jeff Thompson added a comment -

          The defect report does not provide sufficient information for reproduction or action. The creator has not responded to questions. Please re-open if you can provide sufficient information.

          Jeff Thompson added a comment - The defect report does not provide sufficient information for reproduction or action. The creator has not responded to questions. Please re-open if you can provide sufficient information.

            aodo Alex Dover
            sumanthnathg sumanthnath gangavarapu
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: