[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title S Sushil commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted 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 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: 7 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:7Jan 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:7] 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
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title
S Sushil updated an issue
Jenkins / JENKINS-29616
java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Change By:
S Sushil
Comment:
{code:java}The service stops frequently, but it is set to auto-restart. Here is the slave error log:---INFO: Agent discovery successful Agent address: unreal-cicd.moonwalk.io Agent port: 11 Identity: 31:49:15:6a:df:3b:70:76:81:cc:db:f2:c3:bc:57:68Jan 09, 2020 10:18:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingJan 09, 2020 10:18:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to unreal-cicd.moonwalk.io:11Jan 09, 2020 10:18:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectJan 09, 2020 10:18:01 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 10:18:01 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to unreal-cicd.moonwalk.io/13.64.158.153:11] Local headers refused by remote: AutomationEdgeServer is already connected to this master. Rejecting this connection.Jan 09, 2020 10:18:01 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 moreJan 09, 2020 10:18:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to unreal-cicd.moonwalk.io:11Jan 09, 2020 10:18:01 AM hudson.remoting.jnlp.Main$CuiListener
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title S Sushil commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted The service stops frequently, but it is set to auto-restart. Here is the slave error log: --- INFO: Agent discovery successful Agent address: unreal-cicd.moonwalk.io Agent port: 11 Identity: 31:49:15:6a:df:3b:70:76:81:cc:db:f2:c3:bc:57:68Jan 09, 2020 10:18:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingJan 09, 2020 10:18:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to unreal-cicd.moonwalk.io:11Jan 09, 2020 10:18:00 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectJan 09, 2020 10:18:01 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 10:18:01 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to unreal-cicd.moonwalk.io/13.64.158.153:11] Local headers refused by remote: AutomationEdgeServer is already connected to this master. Rejecting this connection.Jan 09, 2020 10:18:01 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 10:18:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to unreal-cicd.moonwalk.io:11Jan 09, 2020 10:18:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP4-plaintext not supported, skippingJan 09, 2020 10:18:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Server reports protocol JNLP3-connect not supported, skippingJan 09, 2020 10:18:01 AM hudson.remoting.jnlp.Main$CuiListener statusINFO:
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Nathan Neulinger commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted 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. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164090.1437742638000.11637.1575420780965%40Atlassian.JIRA.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Jeff Thompson commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted 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. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164090.1437742638000.4780.1572375060875%40Atlassian.JIRA.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title pau sabats assigned an issue to Jeff Thompson Jenkins / JENKINS-29616 java.lang.Exception: The server rejected the connection: None of the protocols were accepted Change By: pau sabats Assignee: pau sabats Jeff Thompson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164090.1437742638000.4042.1572342061507%40Atlassian.JIRA.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title pau sabats assigned an issue to pau sabats Jenkins / JENKINS-29616 java.lang.Exception: The server rejected the connection: None of the protocols were accepted Change By: pau sabats Assignee: pau sabats Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164090.1437742638000.3138.1572262681326%40Atlassian.JIRA.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title pau sabats commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted 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 -workDir "C:\JenkinsSlave" Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164090.1437742638000.634.1570114681250%40Atlassian.JIRA.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Dennis Tran commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted 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 Dan Wang 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, Dan Wang. Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164090.1437742638000.7673.1564974720899%40Atlassian.JIRA.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Владислав Ненашев commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted 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 Add Comment
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Vaibhav Mani Tripathi updated an issue Jenkins / JENKINS-29616 java.lang.Exception: The server rejected the connection: None of the protocols were accepted Change By: Vaibhav Mani Tripathi Attachment: image-2019-02-25-18-24-04-505.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Vaibhav Mani Tripathi commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted Check if JNLP setting is enabled in security configuration i.e. JENKINS_URL:PORT/configureSecurity/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Dan Wang edited a comment on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted 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! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Dan Wang commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted I also faced this issue after I update the jenkins to newest version but now is resolved. I follow Peter Sosnowski 's last update solution, and works now. Remove slave workspace directory Download the launcher (slave-agent.jnlp) on your jenkins slave page. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Frederik Meyer commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted 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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Peter Sosnowski edited a comment on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted Jenkins: 2.120I 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 HTTPSAll 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 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Peter Sosnowski edited a comment on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted Jenkins: 2.120I 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 acceptedjava.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) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Peter Sosnowski commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted 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). 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) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Eric St-Amand edited a comment on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted Using Jenkins 2.107.1I 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 / Advanced 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. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Eric St-Amand edited a comment on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted Using Jenkins 2.107.1I 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 / Advanced button), which I do not like because it is a deprecated protocol. EDIT: Also tried to update to java 1.8u171 64 bits, no luck. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Eric St-Amand commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted 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 / Advanced button), which I do not like because it is a deprecated protocol. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Aaron Jensen commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted 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. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Sukhman Sandhu commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted 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) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Xiaoming Wang commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted 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 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Benjamin Davis commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted 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. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Bilel Yahia commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted I do have the same problem. jenkins 2.19.4 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title febin babu started work on JENKINS-29616 Change By: febin babu Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
