[JENKINS-29616] java.lang.Exception: The server rejected the connection: None of the protocols were accepted - Jenkins Jira

XML

Word

Printable

Details

Type: Bug
Status: Open (View Workflow)
Priority: Critical
Resolution: Unresolved
Component/s: remoting
Labels:
- Protocol
- slave-agent
Environment:

Hide
Windows 7 - 32 bit slave attempting to connect to Windows 7 64 bit master
System Properties

Name ↓
Value
awt.toolkit sun.awt.windows.WToolkit
executable-war C:\Program Files (x86)\Jenkins\jenkins.war
file.encoding Cp1252
file.encoding.pkg sun.io
file.separator \
hudson.diyChunking true
hudson.Functions.autoRefreshSeconds 60
hudson.lifecycle hudson.lifecycle.WindowsServiceLifecycle
java.awt.graphicsenv sun.awt.Win32GraphicsEnvironment
java.awt.headless true
java.awt.printerjob sun.awt.windows.WPrinterJob
java.class.path C:\Program Files (x86)\Jenkins\jenkins.war
java.class.version 51.0
java.endorsed.dirs C:\Program Files (x86)\Jenkins\jre\lib\endorsed
java.ext.dirs C:\Program Files (x86)\Jenkins\jre\lib\ext;C:\Windows\Sun\Java\lib\ext
java.home C:\Program Files (x86)\Jenkins\jre
java.io.tmpdir C:\Windows\TEMP\
java.library.path C:\Program Files (x86)\Jenkins\jre\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\ProgramData\Oracle\Java\javapath;C:\app\Bent\product\11.2.0\client_2\bin;C:\app\Bent\product\11.2.0\client_1\bin;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;c:\Program Files (x86)\AMD APP\bin\x86_64;c:\Program Files (x86)\AMD APP\bin\x86;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Dell\Dell Data Protection\Access\Advanced\Wave\Gemalto\Access Client\v5\;C:\Program Files (x86)\Security Innovation\SI TSS\bin\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\SharpDevelop\4.3\AddIns\BackendBindings\PythonBinding\;C:\Users\bent\Documents\Oracle\instantclient_12_1;C:\Program Files (x86)\SharpDevelop\4.3\AddIns\BackendBindings\PythonBinding\;C:\Program Files (x86)\Java\jre7\bin;C:\Program Files (x86)\IBM\Client Access\Emulator;C:\Program Files (x86)\IBM\Client Access\Shared;C:\Program Files (x86)\IBM\Client Access\;C:\Program Files (x86)\Skype\Phone\;C:\Program Files (x86)\Notepad++;C:\;;.
java.runtime.name Java(TM) SE Runtime Environment
java.runtime.version 1.7.0_25-b17
java.specification.name Java Platform API Specification
java.specification.vendor Oracle Corporation
java.specification.version 1.7
java.vendor Oracle Corporation
java.vendor.url http://java.oracle.com/
java.vendor.url.bug http://bugreport.sun.com/bugreport/
java.version 1.7.0_25
java.vm.info mixed mode
java.vm.name Java HotSpot(TM) Client VM
java.vm.specification.name Java Virtual Machine Specification
java.vm.specification.vendor Oracle Corporation
java.vm.specification.version 1.7
java.vm.vendor Oracle Corporation
java.vm.version 23.25-b01
jcifs.smb.client.domain JIDomain
jnidispatch.path C:\Windows\TEMP\jna--213606140\jna839784891963646250.dll
lib.svnkit.http.methods Digest,Basic,NTLM,Negotiate
lib.svnkit.ssh2.persistent false
line.separator
mail.smtp.sendpartial true
mail.smtps.sendpartial true
os.arch x86
os.name Windows 7
os.version 6.1
path.separator ;
sun.arch.data.model 32
sun.boot.class.path C:\Program Files (x86)\Jenkins\jre\lib\resources.jar;C:\Program Files (x86)\Jenkins\jre\lib\rt.jar;C:\Program Files (x86)\Jenkins\jre\lib\sunrsasign.jar;C:\Program Files (x86)\Jenkins\jre\lib\jsse.jar;C:\Program Files (x86)\Jenkins\jre\lib\jce.jar;C:\Program Files (x86)\Jenkins\jre\lib\charsets.jar;C:\Program Files (x86)\Jenkins\jre\lib\jfr.jar;C:\Program Files (x86)\Jenkins\jre\classes
sun.boot.library.path C:\Program Files (x86)\Jenkins\jre\bin
sun.cpu.endian little
sun.cpu.isalist pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86
sun.desktop windows
sun.io.unicode.encoding UnicodeLittle
sun.java.command C:\Program Files (x86)\Jenkins\jenkins.war --httpPort=8080
sun.java.launcher SUN_STANDARD
sun.jnu.encoding Cp1252
sun.management.compiler HotSpot Client Compiler
sun.os.patch.level Service Pack 1
user.country US
user.dir C:\Program Files (x86)\Jenkins
user.home C:\Windows\System32\config\systemprofile
user.language en
user.name BWAGNERW7$
user.script
user.timezone America/New_York
user.variant

Plugins

Name ↓
Version
Enabled
Pinned
ant 1.2 true false
antisamy-markup-formatter 1.3 true true
build-history-metrics-plugin 1.2 true false
build-keeper-plugin 1.3 true false
build-node-column 0.1 true false
bulk-builder 1.5 true false
categorized-view 1.8 true false
claim 2.7 true false
compact-columns 1.10 true false
config-autorefresh-plugin 1.0 true false
credentials 1.22 true true
cvs 2.12 true true
dashboard-view 2.9.5 true false
description-column-plugin 1.3 true false
external-monitor-job 1.4 true false
extra-columns 1.15 true false
fitnesse 1.16 true false
javadoc 1.3 true true
jquery 1.11.2-0 true false
junit 1.6 true true
lastsuccessdescriptioncolumn 1.0 true false
ldap 1.11 true false
mailer 1.15 true true
mapdb-api 1.0.6.0 true false
matrix-auth 1.2 true true
matrix-project 1.6 true true
maven-plugin 2.10 true true
msbuild 1.24 true false
naginator 1.15 true false
nested-view 1.14 true false
nodelabelparameter 1.5.1 true false
pam-auth 1.2 true true
parameterized-trigger 2.27 true false
postbuildscript 0.17 false false
PrioritySorter 3.4 true false
project-stats-plugin 0.4 true false
purge-build-queue-plugin 1.0 true false
radiatorviewplugin 1.24 true false
run-condition 1.0 false false
scm-api 0.2 true false
script-security 1.14 true true
sectioned-view 1.18 true false
shiningpanda 0.21 true false
ssh-credentials 1.11 true true
ssh-slaves 1.9 true false
subversion 2.5 true true
token-macro 1.10 true false
translation 1.12 true true
view-job-filters 1.26 true false
vsphere-cloud 2.6 true false
vss 1.9 true false
windows-exe-runner 1.2 true false
windows-slaves 1.1 true true
xfpanel 1.2.3 false false

Show
Windows 7 - 32 bit slave attempting to connect to Windows 7 64 bit master System Properties Name ↓ Value awt.toolkit sun.awt.windows.WToolkit executable-war C:\Program Files (x86)\Jenkins\jenkins.war file.encoding Cp1252 file.encoding.pkg sun.io file.separator \ hudson.diyChunking true hudson.Functions.autoRefreshSeconds 60 hudson.lifecycle hudson.lifecycle.WindowsServiceLifecycle java.awt.graphicsenv sun.awt.Win32GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.awt.windows.WPrinterJob java.class.path C:\Program Files (x86)\Jenkins\jenkins.war java.class.version 51.0 java.endorsed.dirs C:\Program Files (x86)\Jenkins\jre\lib\endorsed java.ext.dirs C:\Program Files (x86)\Jenkins\jre\lib\ext;C:\Windows\Sun\Java\lib\ext java.home C:\Program Files (x86)\Jenkins\jre java.io.tmpdir C:\Windows\TEMP\ java.library.path C:\Program Files (x86)\Jenkins\jre\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\ProgramData\Oracle\Java\javapath;C:\app\Bent\product\11.2.0\client_2\bin;C:\app\Bent\product\11.2.0\client_1\bin;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;c:\Program Files (x86)\AMD APP\bin\x86_64;c:\Program Files (x86)\AMD APP\bin\x86;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Dell\Dell Data Protection\Access\Advanced\Wave\Gemalto\Access Client\v5\;C:\Program Files (x86)\Security Innovation\SI TSS\bin\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\SharpDevelop\4.3\AddIns\BackendBindings\PythonBinding\;C:\Users\bent\Documents\Oracle\instantclient_12_1;C:\Program Files (x86)\SharpDevelop\4.3\AddIns\BackendBindings\PythonBinding\;C:\Program Files (x86)\Java\jre7\bin;C:\Program Files (x86)\IBM\Client Access\Emulator;C:\Program Files (x86)\IBM\Client Access\Shared;C:\Program Files (x86)\IBM\Client Access\;C:\Program Files (x86)\Skype\Phone\;C:\Program Files (x86)\Notepad++;C:\;;. java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.7.0_25-b17 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_25 java.vm.info mixed mode java.vm.name Java HotSpot(TM) Client VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 23.25-b01 jcifs.smb.client.domain JIDomain jnidispatch.path C:\Windows\TEMP\jna--213606140\jna839784891963646250.dll lib.svnkit.http.methods Digest,Basic,NTLM,Negotiate lib.svnkit.ssh2.persistent false line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch x86 os.name Windows 7 os.version 6.1 path.separator ; sun.arch.data.model 32 sun.boot.class.path C:\Program Files (x86)\Jenkins\jre\lib\resources.jar;C:\Program Files (x86)\Jenkins\jre\lib\rt.jar;C:\Program Files (x86)\Jenkins\jre\lib\sunrsasign.jar;C:\Program Files (x86)\Jenkins\jre\lib\jsse.jar;C:\Program Files (x86)\Jenkins\jre\lib\jce.jar;C:\Program Files (x86)\Jenkins\jre\lib\charsets.jar;C:\Program Files (x86)\Jenkins\jre\lib\jfr.jar;C:\Program Files (x86)\Jenkins\jre\classes sun.boot.library.path C:\Program Files (x86)\Jenkins\jre\bin sun.cpu.endian little sun.cpu.isalist pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86 sun.desktop windows sun.io.unicode.encoding UnicodeLittle sun.java.command C:\Program Files (x86)\Jenkins\jenkins.war --httpPort=8080 sun.java.launcher SUN_STANDARD sun.jnu.encoding Cp1252 sun.management.compiler HotSpot Client Compiler sun.os.patch.level Service Pack 1 user.country US user.dir C:\Program Files (x86)\Jenkins user.home C:\Windows\System32\config\systemprofile user.language en user.name BWAGNERW7$ user.script user.timezone America/New_York user.variant Plugins Name ↓ Version Enabled Pinned ant 1.2 true false antisamy-markup-formatter 1.3 true true build-history-metrics-plugin 1.2 true false build-keeper-plugin 1.3 true false build-node-column 0.1 true false bulk-builder 1.5 true false categorized-view 1.8 true false claim 2.7 true false compact-columns 1.10 true false config-autorefresh-plugin 1.0 true false credentials 1.22 true true cvs 2.12 true true dashboard-view 2.9.5 true false description-column-plugin 1.3 true false external-monitor-job 1.4 true false extra-columns 1.15 true false fitnesse 1.16 true false javadoc 1.3 true true jquery 1.11.2-0 true false junit 1.6 true true lastsuccessdescriptioncolumn 1.0 true false ldap 1.11 true false mailer 1.15 true true mapdb-api 1.0.6.0 true false matrix-auth 1.2 true true matrix-project 1.6 true true maven-plugin 2.10 true true msbuild 1.24 true false naginator 1.15 true false nested-view 1.14 true false nodelabelparameter 1.5.1 true false pam-auth 1.2 true true parameterized-trigger 2.27 true false postbuildscript 0.17 false false PrioritySorter 3.4 true false project-stats-plugin 0.4 true false purge-build-queue-plugin 1.0 true false radiatorviewplugin 1.24 true false run-condition 1.0 false false scm-api 0.2 true false script-security 1.14 true true sectioned-view 1.18 true false shiningpanda 0.21 true false ssh-credentials 1.11 true true ssh-slaves 1.9 true false subversion 2.5 true true token-macro 1.10 true false translation 1.12 true true view-job-filters 1.26 true false vsphere-cloud 2.6 true false vss 1.9 true false windows-exe-runner 1.2 true false windows-slaves 1.1 true true xfpanel 1.2.3 false false

Similar Issues:

Show

Description

A scheduled batch is attempting to start the slave agent with the following script:

taskkill /f /im "EXCEL.exe"
taskkill /f /im "ipy.exe"
taskkill /f /im "jp2launcher.exe"

javaws http://172.16.8.57:8080/computer/SSW73210/slave-agent.jnlp

When the slave agent opens, it fails to do anything but the enclosed error. After rebooting, this issue fails to reproduce, but this seems dramatically more common when the slave is left on overnight.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

Capture.PNG
14 kB
2015-07-24 12:34
image-2018-06-18-16-38-58-573.png
75 kB
2018-06-18 20:38
image-2018-06-18-16-39-37-521.png
21 kB
2018-06-18 20:39
image-2018-06-19-10-52-45-189.png
393 kB
2018-06-19 05:22
image-2019-02-25-18-24-04-505.png
58 kB
2019-02-25 12:54
image-2021-12-01-12-58-10-781.png
41 kB
2021-12-01 04:58
image-2021-12-03-14-49-26-792.png
31 kB
2021-12-03 06:49
javaws_4448_7882245671431844762.log
13 kB
2018-07-09 08:58
jenkins_error_mac.png
21 kB
2015-10-01 19:13

Activity

Ascending order - Click to sort in descending order

Siddhesh Jaiswal added a comment - 2015-10-01 19:12 - edited

I am seeing something similar on a mac.
Everything was working fine till 9/29/2015
Now i am seeing a similar error.
Tried deleting and creating the node again.

Issue did not go away after reboot, every time i try to launch the slave agent i get the error.

Siddhesh Jaiswal added a comment - 2015-10-01 19:12 - edited I am seeing something similar on a mac. Everything was working fine till 9/29/2015 Now i am seeing a similar error. Tried deleting and creating the node again. Issue did not go away after reboot, every time i try to launch the slave agent i get the error.

Siddhesh Jaiswal added a comment - 2015-10-01 19:58

Issue got resolved after restarting the master agent

Siddhesh Jaiswal added a comment - 2015-10-01 19:58 Issue got resolved after restarting the master agent

Neil Wang added a comment - 2015-11-29 23:23

I have got the same error. But this issue is not reproduced 100%.

Neil Wang added a comment - 2015-11-29 23:23 I have got the same error. But this issue is not reproduced 100%.

Bilel Yahia added a comment - 2016-12-27 15:08

I do have the same problem. jenkins 2.19.4

Bilel Yahia added a comment - 2016-12-27 15:08 I do have the same problem. jenkins 2.19.4

Benjamin Davis added a comment - 2017-01-26 20:34

I ran into this issue after killing the java processes running the jenkins agent manually, and then trying to start them again. The issue I saw was the agent in Jenkins, had not disconnected, even though the processes were dead. Manually clicking the agent disclosure arrow, to make the menu pop up with "Disconnect Agent" in it, then manually disconnecting the agent, allowed me to successfully start the agent again. It seems that since the agent was already "running", Jenkins wasn't listening for a new connection to it.

Benjamin Davis added a comment - 2017-01-26 20:34 I ran into this issue after killing the java processes running the jenkins agent manually, and then trying to start them again. The issue I saw was the agent in Jenkins, had not disconnected, even though the processes were dead. Manually clicking the agent disclosure arrow, to make the menu pop up with "Disconnect Agent" in it, then manually disconnecting the agent, allowed me to successfully start the agent again. It seems that since the agent was already "running", Jenkins wasn't listening for a new connection to it.

Xiaoming Wang added a comment - 2017-02-22 02:36

I get this more and more recently either during git submodule or cmake build. I tried 2.32, 2,38, 2.45 and 2.46. All the same.
Redirect stdout/stderror of console may help a little. For the same Windows slave it run OK with old Jenkins, such as Jenkins 1.6.x

Xiaoming Wang added a comment - 2017-02-22 02:36 I get this more and more recently either during git submodule or cmake build. I tried 2.32, 2,38, 2.45 and 2.46. All the same. Redirect stdout/stderror of console may help a little. For the same Windows slave it run OK with old Jenkins, such as Jenkins 1.6.x

Sukhman Sandhu added a comment - 2017-03-29 13:45

I get this even after upgrading to version 2.52. Restarting the master connects to windows jnlp agents for few hours and then see this error on slave home page:

Restarting the windows service doesn't connect and throws "None of the protocols were accepted" error in .err file.

java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:714) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1368) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112) at com.google.common.util.concurrent.ForwardingExecutorService.submit(ForwardingExecutorService.java:110) at jenkins.util.InterceptingExecutorService.submit(InterceptingExecutorService.java:49) at hudson.remoting.SingleLaneExecutorService.execute(SingleLaneExecutorService.java:105) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:595)

Caused: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@65e5440d[name=Channel to /XX.XXX.XXX.XXX] at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:210) at org.jenkinsci.remoting.nio.NioChannelHub.abortAll(NioChannelHub.java:686) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:663) 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:745)

Sukhman Sandhu added a comment - 2017-03-29 13:45 I get this even after upgrading to version 2.52. Restarting the master connects to windows jnlp agents for few hours and then see this error on slave home page: Restarting the windows service doesn't connect and throws "None of the protocols were accepted" error in .err file. java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:714) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1368) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112) at com.google.common.util.concurrent.ForwardingExecutorService.submit(ForwardingExecutorService.java:110) at jenkins.util.InterceptingExecutorService.submit(InterceptingExecutorService.java:49) at hudson.remoting.SingleLaneExecutorService.execute(SingleLaneExecutorService.java:105) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:595) Caused: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@65e5440d [name=Channel to /XX.XXX.XXX.XXX] at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:210) at org.jenkinsci.remoting.nio.NioChannelHub.abortAll(NioChannelHub.java:686) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:663) 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:745)

Chris Wilson added a comment - 2017-07-07 08:19

I had this error when there was a background jp2launcher process running, which stopped a new foreground process from starting, with this very confusing error message. Killing the background process solved the problem and allowed the foreground process to start normally again.

Chris Wilson added a comment - 2017-07-07 08:19 I had this error when there was a background jp2launcher process running, which stopped a new foreground process from starting, with this very confusing error message. Killing the background process solved the problem and allowed the foreground process to start normally again.

Ruben Coc added a comment - 2017-08-08 06:59

I have the same error . Did you found a solution?

Ruben Coc added a comment - 2017-08-08 06:59 I have the same error . Did you found a solution?

Rohit Patil added a comment - 2017-09-30 16:53

Any updates on this?

Rohit Patil added a comment - 2017-09-30 16:53 Any updates on this?

Ruben Coc added a comment - 2017-10-04 06:49

I try to reproduce this error and when i Launch agent from browser the agent start and it is ok for a while.

The problem is the agent try to connect again over the current process and that make the above error to appear.

Chris Wilson can you tell us when the background process appear because when I start the agent in background there is only one process jp2launcher.

Ruben Coc added a comment - 2017-10-04 06:49 I try to reproduce this error and when i Launch agent from browser the agent start and it is ok for a while. The problem is the agent try to connect again over the current process and that make the above error to appear. Chris Wilson can you tell us when the background process appear because when I start the agent in background there is only one process jp2launcher.

Chris Wilson added a comment - 2017-10-07 19:46

The background process was set up by our IT team, I think it ran the Jenkins agent as a service. It had no visible GUI, no way to know that it was running except for Task Manager (and presumably the Services MMC, although I didn't try that).

Chris Wilson added a comment - 2017-10-07 19:46 The background process was set up by our IT team, I think it ran the Jenkins agent as a service. It had no visible GUI, no way to know that it was running except for Task Manager (and presumably the Services MMC, although I didn't try that).

Oleg Nenashev added a comment - 2017-10-07 19:52

I doubt the issue is in progress. The component is also wrong from what I see, just noticed it in "recent updates".

I am moving it to the "remoting" component for now. In order to diagnose the issue, I need somebody to provide Support bundle (see https://wiki.jenkins.io/display/JENKINS/Support+Core+Plugin) and also logs from agent side.

Oleg Nenashev added a comment - 2017-10-07 19:52 I doubt the issue is in progress. The component is also wrong from what I see, just noticed it in "recent updates". I am moving it to the "remoting" component for now. In order to diagnose the issue, I need somebody to provide Support bundle (see https://wiki.jenkins.io/display/JENKINS/Support+Core+Plugin ) and also logs from agent side.

Aaron Jensen added a comment - 2018-03-07 20:42

We were getting this error because our instance of Jenkins is served via HTTPS (no HTTP allowed). For some reason, default Java 1.8 can't connect. We had to download and install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files and install its .jar files into $JAVA_HOME\lib\security. Once those files were in place, the agent was able to connect.

Aaron Jensen added a comment - 2018-03-07 20:42 We were getting this error because our instance of Jenkins is served via HTTPS (no HTTP allowed). For some reason, default Java 1.8 can't connect. We had to download and install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files and install its .jar files into $JAVA_HOME\lib\security . Once those files were in place, the agent was able to connect.

Eric St-Amand added a comment - 2018-04-20 13:46 - edited

Using Jenkins 2.107.1

I have this error this morning, not sure why exactly, but I checked for those JCE and they were already bundled with java 1.8u151 64 bits. Didn't help to use the one downloaded from Oracle. I found a temporary solution by reverting to JNLP protocol v3 (in Configure Global Security / Agents section / Agent protocols... button), which I do not like because it is a deprecated protocol. Using fixed port for JNLP connection.

EDIT: Also tried to update to java 1.8u171 64 bits, no luck.

Eric St-Amand added a comment - 2018-04-20 13:46 - edited Using Jenkins 2.107.1 I have this error this morning, not sure why exactly, but I checked for those JCE and they were already bundled with java 1.8u151 64 bits. Didn't help to use the one downloaded from Oracle. I found a temporary solution by reverting to JNLP protocol v3 (in Configure Global Security / Agents section / Agent protocols... button), which I do not like because it is a deprecated protocol. Using fixed port for JNLP connection. EDIT: Also tried to update to java 1.8u171 64 bits, no luck.

Peter Sosnowski added a comment - 2018-05-15 15:37 - edited

Jenkins: 2.120

I have the this issue happening on all my slaves. ~~This started once i configured Jenkins to work over HTTPS (HTTP disabled).~~ This is happening regardless whether configured to run over HTTP or HTTPS

All Java Web Start Agent protocols disabled except for protocol/4.

By launching jenkins slave manually via javaws, I can see no issues and the slaves connect, however when I install it as a windows service that's where the issue appears.

SEVERE: The server rejected the connection: None of the protocols were accepted
java.lang.Exception: The server rejected the connection: None of the protocols were accepted
at hudson.remoting.Engine.onConnectionRejected(Engine.java:296)
at hudson.remoting.Engine.run(Engine.java:267)

EDIT (UPDATE): I was able to fix my issue. When I upgraded jenkins to version 2+ I never cleared the working dir of the slaves (so all the files including jenkins-slave.xml, jenkins-slave.exe, etc remained.) After deleting the all the contents, I installed the jenkins slave as a windows service again and I no longer get the error, the slave connects as expected

Peter Sosnowski added a comment - 2018-05-15 15:37 - edited Jenkins: 2.120 I have the this issue happening on all my slaves. This started once i configured Jenkins to work over HTTPS (HTTP disabled). This is happening regardless whether configured to run over HTTP or HTTPS All Java Web Start Agent protocols disabled except for protocol/4. By launching jenkins slave manually via javaws, I can see no issues and the slaves connect, however when I install it as a windows service that's where the issue appears. SEVERE: The server rejected the connection: None of the protocols were accepted java.lang.Exception: The server rejected the connection: None of the protocols were accepted at hudson.remoting.Engine.onConnectionRejected(Engine.java:296) at hudson.remoting.Engine.run(Engine.java:267) EDIT (UPDATE): I was able to fix my issue. When I upgraded jenkins to version 2+ I never cleared the working dir of the slaves (so all the files including jenkins-slave.xml, jenkins-slave.exe, etc remained.) After deleting the all the contents, I installed the jenkins slave as a windows service again and I no longer get the error, the slave connects as expected

Yuva Kumar added a comment - 2018-06-18 20:40

Getting the above error while launching jar file from slave machine. Its Windows 10 device.

Yuva Kumar added a comment - 2018-06-18 20:40 Getting the above error while launching jar file from slave machine. Its Windows 10 device.

PRAVEEN GUPTA added a comment - 2018-06-19 05:22 - edited

I am also facing same issue when I upgraded to the latest LTS Jenkins version. But even after getting back to 2 older versions the slaves are not able to connect using any JNLP protocols even JNLP 1/2/3 doesn't work. Even after successful discovery of agent, it cant connect.

PRAVEEN GUPTA added a comment - 2018-06-19 05:22 - edited I am also facing same issue when I upgraded to the latest LTS Jenkins version. But even after getting back to 2 older versions the slaves are not able to connect using any JNLP protocols even JNLP 1/2/3 doesn't work. Even after successful discovery of agent, it cant connect.

Tapio Reijonen added a comment - 2018-07-09 09:05 - edited

We are also facing same issue when we upgraded to the LTS Jenkins ver. 2.89.4 version from version 2.73.3, where this was working as excepted.

This will failed (via windows command prompt or via browser):

javaws slave-agent.jnlp

javaws_4448_7882245671431844762.log

^{With same windows host, this work as expected:}

java -jar agent.jar -jnlpUrl https://xxx/slave-agent.jnlp -secret yyyy

Almost all jnlp protocols (not Jenkins CLI Protocol/1) are enabled from the master configuration.

All plugins are 'up to date'

java version "1.8.0_171"

Tapio Reijonen added a comment - 2018-07-09 09:05 - edited We are also facing same issue when we upgraded to the LTS Jenkins ver. 2.89.4 version from version 2.73.3, where this was working as excepted. This will failed (via windows command prompt or via browser): javaws slave-agent.jnlp javaws_4448_7882245671431844762.log With same windows host, this work as expected: java -jar agent.jar -jnlpUrl https: //xxx/slave-agent.jnlp -secret yyyy Almost all jnlp protocols (not Jenkins CLI Protocol/1) are enabled from the master configuration. All plugins are 'up to date' java version "1.8.0_171"

Frederik Meyer added a comment - 2018-11-27 11:08

I also faced this issue and was able to fix it, maybe? It happened that a same agent was running on a different VM. I closed it, tried to reconnect and no error message anymore.

Frederik Meyer added a comment - 2018-11-27 11:08 I also faced this issue and was able to fix it, maybe? It happened that a same agent was running on a different VM. I closed it, tried to reconnect and no error message anymore.

Dan Wang added a comment - 2019-01-12 01:51 - edited

I also faced this issue after I update the jenkins to newest version but now is resolved.

I follow junior1024 's last update solution, and works now.

Remove slave workspace directory
Download the launcher (slave-agent.jnlp) on your jenkins slave page.
Use task-scheduler to process slave-agent.
Enjoy it!

Dan Wang added a comment - 2019-01-12 01:51 - edited I also faced this issue after I update the jenkins to newest version but now is resolved. I follow junior1024 's last update solution, and works now. Remove slave workspace directory Download the launcher (slave-agent.jnlp) on your jenkins slave page. Use task-scheduler to process slave-agent. Enjoy it!

Vaibhav Mani Tripathi added a comment - 2019-02-25 12:54

Check if JNLP setting is enabled in security configuration i.e.

JENKINS_URL:PORT/configureSecurity/

Vaibhav Mani Tripathi added a comment - 2019-02-25 12:54 Check if JNLP setting is enabled in security configuration i.e. JENKINS_URL:PORT/configureSecurity/

Владислав Ненашев added a comment - 2019-07-16 07:37

I get a replay of this problem on Jenkins ver. 2.164.2, the above mentioned setup checked. Agent log with error:

INFO: Trying protocol: JNLP4-connect
июл 15, 2019 8:01:46 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Protocol JNLP4-connect encountered an unexpected exception
java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Connection closed before acknowledgement sent
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: Connection closed before acknowledgement sent
at org.jenkinsci.remoting.protocol.impl.AckFilterLayer.onRecvClosed(AckFilterLayer.java:280)
at org.jenkinsci.remoting.protocol.FilterLayer.abort(FilterLayer.java:164)
at org.jenkinsci.remoting.protocol.impl.AckFilterLayer.access$000(AckFilterLayer.java:43)
at org.jenkinsci.remoting.protocol.impl.AckFilterLayer$1.run(AckFilterLayer.java:176)
at org.jenkinsci.remoting.protocol.IOHub$DelayedRunnable.run(IOHub.java:964)
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)июл 15, 2019 8:01:46 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to jenkins:8081
июл 15, 2019 8:01:46 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server reports protocol JNLP4-plaintext not supported, skipping
июл 15, 2019 8:01:46 AM hudson.remoting.jnlp.Main$CuiListener status

Владислав Ненашев added a comment - 2019-07-16 07:37 I get a replay of this problem on Jenkins ver. 2.164.2 , the above mentioned setup checked. Agent log with error: INFO: Trying protocol: JNLP4-connect июл 15, 2019 8:01:46 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Protocol JNLP4-connect encountered an unexpected exception java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Connection closed before acknowledgement sent 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: Connection closed before acknowledgement sent at org.jenkinsci.remoting.protocol.impl.AckFilterLayer.onRecvClosed(AckFilterLayer.java:280) at org.jenkinsci.remoting.protocol.FilterLayer.abort(FilterLayer.java:164) at org.jenkinsci.remoting.protocol.impl.AckFilterLayer.access$000(AckFilterLayer.java:43) at org.jenkinsci.remoting.protocol.impl.AckFilterLayer$1.run(AckFilterLayer.java:176) at org.jenkinsci.remoting.protocol.IOHub$DelayedRunnable.run(IOHub.java:964) 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)июл 15, 2019 8:01:46 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to jenkins:8081 июл 15, 2019 8:01:46 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Server reports protocol JNLP4-plaintext not supported, skipping июл 15, 2019 8:01:46 AM hudson.remoting.jnlp.Main$CuiListener status

Dennis Tran added a comment - 2019-08-05 03:11

I'm facing a same issue in Jenkins 2.164.2, slave is windows 10 1809, java 18.0.221. I tried to clear slave workspace directory and download new launcher as sbc8112 suggest, but no luck, this problem still occur. However, I do not understand the point "3. Use task-scheduler to process slave-agent", can you explain more detail how to do that, sbc8112.

Thanks.

Dennis Tran added a comment - 2019-08-05 03:11 I'm facing a same issue in Jenkins 2.164.2, slave is windows 10 1809, java 18.0.221. I tried to clear slave workspace directory and download new launcher as sbc8112 suggest, but no luck, this problem still occur. However, I do not understand the point "3. Use task-scheduler to process slave-agent", can you explain more detail how to do that, sbc8112 . Thanks.

pau sabats added a comment - 2019-10-03 14:57

I reproduced this error on win10 removing the slave-agent.jnlp or having more than 1 of this files.

The problem is that the slaves loses somehow the connection configuration to the master so this error is shown.

My solution was to create a new agent slave, so a new .jnlp can be downloaded, and this one will be well configured so it will work.

If the .jnlp doesn't show you in jenkins to download, you can try with the command :

java -jar agent.jar -jnlpUrl http://jenkinsurl:port/computer/windows-agent/slave-agent.jnlp -secret xxxxxxxx -workDir "C:\JenkinsSlave"

pau sabats added a comment - 2019-10-03 14:57 I reproduced this error on win10 removing the slave-agent.jnlp or having more than 1 of this files. The problem is that the slaves loses somehow the connection configuration to the master so this error is shown. My solution was to create a new agent slave, so a new .jnlp can be downloaded, and this one will be well configured so it will work. If the .jnlp doesn't show you in jenkins to download, you can try with the command : java -jar agent.jar -jnlpUrl http://jenkinsurl:port/computer/windows-agent/slave-agent.jnlp -secret xxxxxxxx -workDir "C:\JenkinsSlave"

Jeff Thompson added a comment - 2019-10-29 18:50

It looks like people are seeing a number of different issues, generally involving the same error message. Some people report success by tracking down a different machine running the same agent. Some find that some cleanup corrects the problem, though it's not clear just what cleanup is required. In some cases it probably involves a connection timeout and the server thinks an old instance of the agent is still connected.

As Oleg said earlier, to get anywhere with this will require clear reproduction documentation and both agent and master logs. Information on whether it is specific to a certain type of platform or environment would also be important. I see some mention of different versions of Windows OSes but it's not clear if it's just a Windows issue and if it only occurs in some Windows environments or versions.

Jeff Thompson added a comment - 2019-10-29 18:50 It looks like people are seeing a number of different issues, generally involving the same error message. Some people report success by tracking down a different machine running the same agent. Some find that some cleanup corrects the problem, though it's not clear just what cleanup is required. In some cases it probably involves a connection timeout and the server thinks an old instance of the agent is still connected. As Oleg said earlier, to get anywhere with this will require clear reproduction documentation and both agent and master logs. Information on whether it is specific to a certain type of platform or environment would also be important. I see some mention of different versions of Windows OSes but it's not clear if it's just a Windows issue and if it only occurs in some Windows environments or versions.

Nathan Neulinger added a comment - 2019-12-04 00:52

FYI in case it helps any – I just had to go through a big diag effort on my site with a bunch of windows JNLP agents that stopped working sometime in past few days with the same above failures/errors.

After a long set of rabbit trails - what I found in my case – the problem wound up being reverse DNS resolution stopped working (unrelated local problem – "It's always DNS", right?) - but that inability to reverse resolve the connecting client (windows box) was causing the JNLP server side to drop the connection.

Just wanted to add this here in case it helps anyone else with future similar issues if it happens to be related.

Nathan Neulinger added a comment - 2019-12-04 00:52 FYI in case it helps any – I just had to go through a big diag effort on my site with a bunch of windows JNLP agents that stopped working sometime in past few days with the same above failures/errors. After a long set of rabbit trails - what I found in my case – the problem wound up being reverse DNS resolution stopped working (unrelated local problem – "It's always DNS", right?) - but that inability to reverse resolve the connecting client (windows box) was causing the JNLP server side to drop the connection. Just wanted to add this here in case it helps anyone else with future similar issues if it happens to be related.

S Sushil added a comment - 2020-01-09 19:32

Not sure if same issue, but the service is dying on a server 2012 node. It is set to restart and eventually it will connect but again die very frequently. Below is the slave error and slave-wrapper error logs:

********************************************** -slave error log - ***********************

INFO: ConnectedJan 09, 2020 11:24:17 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: TerminatedJan 09, 2020 11:24:27 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Performing onReconnect operation.Jan 09, 2020 11:24:27 AM jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$FindEffectiveRestarters$1 onReconnectINFO: Restarting agent via jenkins.slaves.restarter.WinswSlaveRestarter@50c19504Jan 09, 2020 11:24:32 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: AutomationEdgeServerJan 09, 2020 11:24:32 AM hudson.remoting.jnlp.Main$CuiListener <init>INFO: Jenkins agent is running in headless mode.Jan 09, 2020 11:24:32 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.36Jan 09, 2020 11:24:32 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDirINFO: Using c:\jenkins\remoting as a remoting work directoryJan 09, 2020 11:24:32 AM org.jenkinsci.remoting.engine.WorkDirManager setupLoggingINFO: Both error and output logs will be printed to c:\jenkins\remotingJan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [https://real-cicd.moonwalk.io/]Jan 09, 2020 11:24:33 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Jan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful  Agent address: real-cicd.moonwalk.io  Agent port:    70000  Identity:      31:49:15:6a:df:3b:70:76:81:cc:db:f2:c3:bc:57:68Jan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingJan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to real-cicd.moonwalk.io:70000Jan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectJan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 31:49:15:6a:df:3b:70:76:81:cc:db:f2:c3:bc:57:68Jan 09, 2020 11:24:33 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to real-cicd.moonwalk.io/11.11.111.111:70000] Local headers refused by remote: AutomationEdgeServer is already connected to this master. Rejecting this connection.Jan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: AutomationEdgeServer 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:577) at hudson.remoting.Engine.run(Engine.java:488)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: AutomationEdgeServer 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:816) 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:816) 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:97) at java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more
Jan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to real-cicd.moonwalk.io:70000Jan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP4-plaintext not supported, skippingJan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP3-connect not supported, skippingJan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP2-connect not supported, skippingJan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP-connect not supported, skippingJan 09, 2020 11:24:33 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:662) at hudson.remoting.Engine.innerRun(Engine.java:602) at hudson.remoting.Engine.run(Engine.java:488)
Jan 09, 2020 11:25:36 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: AutomationEdgeServerJan 09, 2020 11:25:36 AM hudson.remoting.jnlp.Main$CuiListener <init>INFO: Jenkins agent is running in headless mode.Jan 09, 2020 11:25:36 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.36Jan 09, 2020 11:25:36 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDirINFO: Using c:\jenkins\remoting as a remoting work directoryJan 09, 2020 11:25:36 AM org.jenkinsci.remoting.engine.WorkDirManager setupLoggingINFO: Both error and output logs will be printed to c:\jenkins\remotingJan 09, 2020 11:25:36 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [https://real-cicd.moonwalk.io/]Jan 09, 2020 11:25:37 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Jan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful  Agent address: real-cicd.moonwalk.io  Agent port:    70000  Identity:      31:49:15:6a:df:3b:70:76:81:cc:db:f2:c3:bc:57:68Jan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingJan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to real-cicd.moonwalk.io:70000Jan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectJan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 31:49:15:6a:df:3b:70:76:81:cc:db:f2:c3:bc:57:68Jan 09, 2020 11:25:37 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to real-cicd.moonwalk.io/11.11.111.111:70000] Local headers refused by remote: AutomationEdgeServer is already connected to this master. Rejecting this connection.Jan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: AutomationEdgeServer 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:577) at hudson.remoting.Engine.run(Engine.java:488)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: AutomationEdgeServer 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:816) 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:816) 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:97) at java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more
Jan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to real-cicd.moonwalk.io:70000Jan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP4-plaintext not supported, skippingJan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP3-connect not supported, skippingJan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP2-connect not supported, skippingJan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP-connect not supported, skippingJan 09, 2020 11:25:37 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:662) at hudson.remoting.Engine.innerRun(Engine.java:602) at hudson.remoting.Engine.run(Engine.java:488)


***********************Wrapper logs*******************
020-01-09 10:49:05,867 DEBUG - User requested the status of the process with id 'jenkinsslave-c__jenkins'2020-01-09 10:49:05,872 DEBUG - Completed. Exit code is 02020-01-09 11:24:28,242 DEBUG - Starting ServiceWrapper in the CLI mode2020-01-09 11:24:28,523 INFO  - Restarting the service with id 'jenkinsslave-c__jenkins'2020-01-09 11:24:28,539 DEBUG - Completed. Exit code is 02020-01-09 11:24:28,836 DEBUG - Starting ServiceWrapper in the CLI mode2020-01-09 11:24:29,071 INFO  - Restarting the service with id 'jenkinsslave-c__jenkins'2020-01-09 11:24:29,101 INFO  - Stopping jenkinsslave-c__jenkins2020-01-09 11:24:29,101 DEBUG - ProcessKill 48482020-01-09 11:24:29,226 INFO  - Found child process: 3564 Name: conhost.exe2020-01-09 11:24:29,273 INFO  - Stopping process 35642020-01-09 11:24:29,273 INFO  - Send SIGINT 35642020-01-09 11:24:29,273 WARN  - SIGINT to 3564 failed - Killing as fallback2020-01-09 11:24:29,273 INFO  - Stopping process 48482020-01-09 11:24:29,273 INFO  - Send SIGINT 48482020-01-09 11:24:29,273 WARN  - SIGINT to 4848 failed - Killing as fallback2020-01-09 11:24:29,289 INFO  - Finished jenkinsslave-c__jenkins2020-01-09 11:24:29,289 DEBUG - Completed. Exit code is 02020-01-09 11:24:30,476 INFO  - Starting ServiceWrapper in the service mode2020-01-09 11:24:30,523 DEBUG - Completed. Exit code is 02020-01-09 11:24:30,554 INFO  - Downloading: https://real-cicd.moonwalk.io/jnlpJars/slave.jar to C:\jenkins\slave.jar. failOnError=False2020-01-09 11:24:31,211 INFO  - Starting C:\Program Files\Java\jre1.8.0_231\bin\java.exe -Xrs  -jar "C:\jenkins\slave.jar" -jnlpUrl https://real-cicd.moonwalk.io/computer/AutomationEdgeServer/slave-agent.jnlp -secret 65e13a6191d47de3754d8f57cb56ba4f9ab199daeac2ccd161cd74050fd2e1cb2020-01-09 11:24:31,226 INFO  - Extension loaded: killOnStartup2020-01-09 11:24:31,242 DEBUG - Checking the potentially runaway process with PID=48482020-01-09 11:24:31,242 DEBUG - No runaway process with PID=4848. The process has been already stopped.2020-01-09 11:24:31,273 INFO  - Started process 44122020-01-09 11:24:31,289 DEBUG - Forwarding logs of the process System.Diagnostics.Process (java) to winsw.SizeBasedRollingLogAppender2020-01-09 11:24:31,320 INFO  - Recording PID of the started process:4412. PID file destination is C:\jenkins\jenkins_agent.pid2020-01-09 11:25:34,657 INFO  - Starting ServiceWrapper in the service mode2020-01-09 11:25:34,688 INFO  - Downloading: https://real-cicd.moonwalk.io/jnlpJars/slave.jar to C:\jenkins\slave.jar. failOnError=False2020-01-09 11:25:35,422 INFO  - Starting C:\Program Files\Java\jre1.8.0_231\bin\java.exe -Xrs  -jar "C:\jenkins\slave.jar" -jnlpUrl https://real-cicd.moonwalk.io/computer/AutomationEdgeServer/slave-agent.jnlp -secret 65e13a6191d47de3754d8f57cb56ba4f9ab199daeac2ccd161cd74050fd2e1cb2020-01-09 11:25:35,438 INFO  - Extension loaded: killOnStartup2020-01-09 11:25:35,438 DEBUG - Checking the potentially runaway process with PID=44122020-01-09 11:25:35,453 DEBUG - No runaway process with PID=4412. The process has been already stopped.2020-01-09 11:25:35,485 INFO  - Started process 32042020-01-09 11:25:35,485 DEBUG - Forwarding logs of the process System.Diagnostics.Process (java) to winsw.SizeBasedRollingLogAppender2020-01-09 11:25:35,516 INFO  - Recording PID of the started process:3204. PID file destination is C:\jenkins\jenkins_agent.pid2020-01-09 11:26:38,647 INFO  - Starting ServiceWrapper in the service mode2020-01-09 11:26:38,710 INFO  - Downloading: https://real-cicd.moonwalk.io/jnlpJars/slave.jar to C:\jenkins\slave.jar. failOnError=False2020-01-09 11:26:39,475 INFO  - Starting C:\Program Files\Java\jre1.8.0_231\bin\java.exe -Xrs  -jar "C:\jenkins\slave.jar" -jnlpUrl https://real-cicd.moonwalk.io/computer/AutomationEdgeServer/slave-agent.jnlp -secret 65e13a6191d47de3754d8f57cb56ba4f9ab199daeac2ccd161cd74050fd2e1cb2020-01-09 11:26:39,491 INFO  - Extension loaded: killOnStartup2020-01-09 11:26:39,491 DEBUG - Checking the potentially runaway process with PID=32042020-01-09 11:26:39,506 DEBUG - No runaway process with PID=3204. The process has been already stopped.2020-01-09 11:26:39,538 INFO  - Started process 26042020-01-09 11:26:39,538 DEBUG - Forwarding logs of the process System.Diagnostics.Process (java) to winsw.SizeBasedRollingLogAppender2020-01-09 11:26:39,569 INFO  - Recording PID of the started process:2604. PID file destination is C:\jenkins\jenkins_agent.pid

S Sushil added a comment - 2020-01-09 19:32 Not sure if same issue, but the service is dying on a server 2012 node. It is set to restart and eventually it will connect but again die very frequently. Below is the slave error and slave-wrapper error logs: ********************************************** -slave error log - *********************** INFO: ConnectedJan 09, 2020 11:24:17 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: TerminatedJan 09, 2020 11:24:27 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Performing onReconnect operation.Jan 09, 2020 11:24:27 AM jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$FindEffectiveRestarters$1 onReconnectINFO: Restarting agent via jenkins.slaves.restarter.WinswSlaveRestarter@50c19504Jan 09, 2020 11:24:32 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: AutomationEdgeServerJan 09, 2020 11:24:32 AM hudson.remoting.jnlp.Main$CuiListener <init>INFO: Jenkins agent is running in headless mode.Jan 09, 2020 11:24:32 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.36Jan 09, 2020 11:24:32 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDirINFO: Using c:\jenkins\remoting as a remoting work directoryJan 09, 2020 11:24:32 AM org.jenkinsci.remoting.engine.WorkDirManager setupLoggingINFO: Both error and output logs will be printed to c:\jenkins\remotingJan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [https: //real-cicd.moonwalk.io/]Jan 09, 2020 11:24:33 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Jan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: real-cicd.moonwalk.io Agent port: 70000 Identity: 31:49:15:6a:df:3b:70:76:81:cc:db:f2:c3:bc:57:68Jan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingJan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to real-cicd.moonwalk.io:70000Jan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectJan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 31:49:15:6a:df:3b:70:76:81:cc:db:f2:c3:bc:57:68Jan 09, 2020 11:24:33 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to real-cicd.moonwalk.io/11.11.111.111:70000] Local headers refused by remote: AutomationEdgeServer is already connected to this master. Rejecting this connection.Jan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: AutomationEdgeServer 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:577) at hudson.remoting.Engine.run(Engine.java:488)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: AutomationEdgeServer 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:816) 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:816) 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:97) at java.lang. Thread .run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more Jan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to real-cicd.moonwalk.io:70000Jan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP4-plaintext not supported, skippingJan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP3-connect not supported, skippingJan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP2-connect not supported, skippingJan 09, 2020 11:24:33 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP-connect not supported, skippingJan 09, 2020 11:24:33 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:662) at hudson.remoting.Engine.innerRun(Engine.java:602) at hudson.remoting.Engine.run(Engine.java:488) Jan 09, 2020 11:25:36 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: AutomationEdgeServerJan 09, 2020 11:25:36 AM hudson.remoting.jnlp.Main$CuiListener <init>INFO: Jenkins agent is running in headless mode.Jan 09, 2020 11:25:36 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.36Jan 09, 2020 11:25:36 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDirINFO: Using c:\jenkins\remoting as a remoting work directoryJan 09, 2020 11:25:36 AM org.jenkinsci.remoting.engine.WorkDirManager setupLoggingINFO: Both error and output logs will be printed to c:\jenkins\remotingJan 09, 2020 11:25:36 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [https: //real-cicd.moonwalk.io/]Jan 09, 2020 11:25:37 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Jan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: real-cicd.moonwalk.io Agent port: 70000 Identity: 31:49:15:6a:df:3b:70:76:81:cc:db:f2:c3:bc:57:68Jan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingJan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to real-cicd.moonwalk.io:70000Jan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectJan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 31:49:15:6a:df:3b:70:76:81:cc:db:f2:c3:bc:57:68Jan 09, 2020 11:25:37 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to real-cicd.moonwalk.io/11.11.111.111:70000] Local headers refused by remote: AutomationEdgeServer is already connected to this master. Rejecting this connection.Jan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: AutomationEdgeServer 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:577) at hudson.remoting.Engine.run(Engine.java:488)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: AutomationEdgeServer 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:816) 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:816) 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:97) at java.lang. Thread .run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more Jan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to real-cicd.moonwalk.io:70000Jan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP4-plaintext not supported, skippingJan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP3-connect not supported, skippingJan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP2-connect not supported, skippingJan 09, 2020 11:25:37 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP-connect not supported, skippingJan 09, 2020 11:25:37 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:662) at hudson.remoting.Engine.innerRun(Engine.java:602) at hudson.remoting.Engine.run(Engine.java:488) ***********************Wrapper logs******************* 020-01-09 10:49:05,867 DEBUG - User requested the status of the process with id 'jenkinsslave-c__jenkins' 2020-01-09 10:49:05,872 DEBUG - Completed. Exit code is 02020-01-09 11:24:28,242 DEBUG - Starting ServiceWrapper in the CLI mode2020-01-09 11:24:28,523 INFO - Restarting the service with id 'jenkinsslave-c__jenkins' 2020-01-09 11:24:28,539 DEBUG - Completed. Exit code is 02020-01-09 11:24:28,836 DEBUG - Starting ServiceWrapper in the CLI mode2020-01-09 11:24:29,071 INFO - Restarting the service with id 'jenkinsslave-c__jenkins' 2020-01-09 11:24:29,101 INFO - Stopping jenkinsslave-c__jenkins2020-01-09 11:24:29,101 DEBUG - ProcessKill 48482020-01-09 11:24:29,226 INFO - Found child process: 3564 Name: conhost.exe2020-01-09 11:24:29,273 INFO - Stopping process 35642020-01-09 11:24:29,273 INFO - Send SIGINT 35642020-01-09 11:24:29,273 WARN - SIGINT to 3564 failed - Killing as fallback2020-01-09 11:24:29,273 INFO - Stopping process 48482020-01-09 11:24:29,273 INFO - Send SIGINT 48482020-01-09 11:24:29,273 WARN - SIGINT to 4848 failed - Killing as fallback2020-01-09 11:24:29,289 INFO - Finished jenkinsslave-c__jenkins2020-01-09 11:24:29,289 DEBUG - Completed. Exit code is 02020-01-09 11:24:30,476 INFO - Starting ServiceWrapper in the service mode2020-01-09 11:24:30,523 DEBUG - Completed. Exit code is 02020-01-09 11:24:30,554 INFO - Downloading: https: //real-cicd.moonwalk.io/jnlpJars/slave.jar to C:\jenkins\slave.jar. failOnError=False2020-01-09 11:24:31,211 INFO - Starting C:\Program Files\Java\jre1.8.0_231\bin\java.exe -Xrs -jar "C:\jenkins\slave.jar" -jnlpUrl https://real-cicd.moonwalk.io/computer/AutomationEdgeServer/slave-agent.jnlp -secret 65e13a6191d47de3754d8f57cb56ba4f9ab199daeac2ccd161cd74050fd2e1cb2020-01-09 11:24:31,226 INFO - Extension loaded: killOnStartup2020-01-09 11:24:31,242 DEBUG - Checking the potentially runaway process with PID=48482020-01-09 11:24:31,242 DEBUG - No runaway process with PID=4848. The process has been already stopped.2020-01-09 11:24:31,273 INFO - Started process 44122020-01-09 11:24:31,289 DEBUG - Forwarding logs of the process System .Diagnostics. Process (java) to winsw.SizeBasedRollingLogAppender2020-01-09 11:24:31,320 INFO - Recording PID of the started process:4412. PID file destination is C:\jenkins\jenkins_agent.pid2020-01-09 11:25:34,657 INFO - Starting ServiceWrapper in the service mode2020-01-09 11:25:34,688 INFO - Downloading: https://real-cicd.moonwalk.io/jnlpJars/slave.jar to C:\jenkins\slave.jar. failOnError=False2020-01-09 11:25:35,422 INFO - Starting C:\Program Files\Java\jre1.8.0_231\bin\java.exe -Xrs -jar "C:\jenkins\slave.jar" -jnlpUrl https://real-cicd.moonwalk.io/computer/AutomationEdgeServer/slave-agent.jnlp -secret 65e13a6191d47de3754d8f57cb56ba4f9ab199daeac2ccd161cd74050fd2e1cb2020-01-09 11:25:35,438 INFO - Extension loaded: killOnStartup2020-01-09 11:25:35,438 DEBUG - Checking the potentially runaway process with PID=44122020-01-09 11:25:35,453 DEBUG - No runaway process with PID=4412. The process has been already stopped.2020-01-09 11:25:35,485 INFO - Started process 32042020-01-09 11:25:35,485 DEBUG - Forwarding logs of the process System .Diagnostics. Process (java) to winsw.SizeBasedRollingLogAppender2020-01-09 11:25:35,516 INFO - Recording PID of the started process:3204. PID file destination is C:\jenkins\jenkins_agent.pid2020-01-09 11:26:38,647 INFO - Starting ServiceWrapper in the service mode2020-01-09 11:26:38,710 INFO - Downloading: https://real-cicd.moonwalk.io/jnlpJars/slave.jar to C:\jenkins\slave.jar. failOnError=False2020-01-09 11:26:39,475 INFO - Starting C:\Program Files\Java\jre1.8.0_231\bin\java.exe -Xrs -jar "C:\jenkins\slave.jar" -jnlpUrl https://real-cicd.moonwalk.io/computer/AutomationEdgeServer/slave-agent.jnlp -secret 65e13a6191d47de3754d8f57cb56ba4f9ab199daeac2ccd161cd74050fd2e1cb2020-01-09 11:26:39,491 INFO - Extension loaded: killOnStartup2020-01-09 11:26:39,491 DEBUG - Checking the potentially runaway process with PID=32042020-01-09 11:26:39,506 DEBUG - No runaway process with PID=3204. The process has been already stopped.2020-01-09 11:26:39,538 INFO - Started process 26042020-01-09 11:26:39,538 DEBUG - Forwarding logs of the process System .Diagnostics. Process (java) to winsw.SizeBasedRollingLogAppender2020-01-09 11:26:39,569 INFO - Recording PID of the started process:2604. PID file destination is C:\jenkins\jenkins_agent.pid

bingchuan sun added a comment - 2021-12-01 04:58 - edited

I have the same problem. After change org.jenkinsci.remoting.protocol.ProtocolStack#handshakingTimeout to more then 20s,then it connected. My conclusion is that the connect will take more then 10s sometimes based on the network driver,but the default 'final ' value is 10s , so it will timeout and closed.

The final reason is java.net.InetSocketAddress#getHostName invoked by org.jenkinsci.remoting.engine.JnlpProtocol4Handler#createSSLEngine blocked so much time.

bingchuan sun added a comment - 2021-12-01 04:58 - edited I have the same problem. After change org.jenkinsci.remoting.protocol.ProtocolStack#handshakingTimeout to more then 20s,then it connected. My conclusion is that the connect will take more then 10s sometimes based on the network driver,but the default 'final ' value is 10s , so it will timeout and closed. The final reason is java.net.InetSocketAddress#getHostName invoked by org.jenkinsci.remoting.engine.JnlpProtocol4Handler#createSSLEngine blocked so much time.

People

Assignee:: Unassigned

Reporter:: Benjamin Wagner

Votes:: 32 Vote for this issue

Watchers:: 48 Start watching this issue

Dates

Created:: 2015-07-24 12:57

Updated:: 2 days ago 03:46