-
Bug
-
Resolution: Cannot Reproduce
-
Critical
-
None
-
Jenkins ver. 2.73.2
Slaves run on: Windows 7 32-bit
Java version: Java 1.8.0_102 32-bit
Remoting version: 3.10.2
Every day our slaves get disconnected. We are running them with a command:
java -jar slave.jar -jnlpUrl https://sample.com/computer/node-pf4t-1/slave-agent.jnlp -secret JENKINS_SECRET
Here are the logs when it was connected and after few hours disconnected:
Jan 26, 2018 1:50:09 PM hudson.remoting.jnlp.Main createEngine
INFO: Setting up slave: node-pf4t-1
Jan 26, 2018 1:50:09 PM hudson.remoting.jnlp.Main$CuiListener <init>
INFO: Jenkins agent is running in headless mode.
Jan 26, 2018 1:50:09 PM hudson.remoting.Engine startEngine
WARNING: No Working Directory. Using the legacy JAR Cache location: C:\Users\Administrator\.jenkins\cache\jars
Jan 26, 2018 1:50:09 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among https://sample.com/
Jan 26, 2018 1:50:09 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping, JNLP3-connect]
Jan 26, 2018 1:50:09 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
Agent address: sample.com
Agent port: 9150
Identity: 85:d2:61:cd:1c:88:79:28:6f:b4:94:02:ad:6b:a9:9e
Jan 26, 2018 1:50:09 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Jan 26, 2018 1:50:09 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to sample.com:9150
Jan 26, 2018 1:50:09 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Jan 26, 2018 1:50:09 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed: 85:d2:61:cd:1c:88:79:28:6f:b4:94:02:ad:6b:a9:9e
Jan 26, 2018 1:50:10 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected
Jan 27, 2018 6:00:29 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Terminated
Jan 27, 2018 6:00:39 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among https://sample.com/
Jan 27, 2018 6:00:39 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping, JNLP3-connect]
Jan 27, 2018 6:00:39 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
Agent address: sample.com
Agent port: 9150
Identity: 85:d2:61:cd:1c:88:79:28:6f:b4:94:02:ad:6b:a9:9e
Jan 27, 2018 6:00:39 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Jan 27, 2018 6:00:39 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to sample.com:9150
Jan 27, 2018 6:00:39 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Jan 27, 2018 6:00:39 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed: 85:d2:61:cd:1c:88:79:28:6f:b4:94:02:ad:6b:a9:9e
Jan 27, 2018 6:00:39 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv
INFO: [JNLP4-connect connection to sample.com/10.254.28.89:9150] Local headers refused by remote: node-pf4t-1 is already connected to this master. Rejecting this connection.
Jan 27, 2018 6:00:39 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: node-pf4t-1 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:590)
at hudson.remoting.Engine.run(Engine.java:451)
Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: node-pf4t-1 is already connected to this master. Rejecting this connection.
at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:377)
at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:432)
at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)
at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287)
at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172)
at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)
at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48)
at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at hudson.remoting.Engine$1$1.run(Engine.java:98)
at java.lang.Thread.run(Thread.java:745)
Suppressed: java.nio.channels.ClosedChannelException
... 7 more
Jan 27, 2018 6:00:39 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to sample.com:9150
Jan 27, 2018 6:00:39 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server reports protocol JNLP4-plaintext not supported, skipping
Jan 27, 2018 6:00:39 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP3-connect
Jan 27, 2018 6:00:39 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Protocol JNLP3-connect encountered an unexpected exception
java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: JNLP3-connect: Master rejected connection:
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at hudson.remoting.Engine.innerRun(Engine.java:590)
at hudson.remoting.Engine.run(Engine.java:451)
Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: JNLP3-connect: Master rejected connection:
at org.jenkinsci.remoting.engine.JnlpProtocol3Handler.sendHandshake(JnlpProtocol3Handler.java:241)
at org.jenkinsci.remoting.engine.JnlpProtocol3Handler.sendHandshake(JnlpProtocol3Handler.java:125)
at org.jenkinsci.remoting.engine.LegacyJnlpProtocolHandler$2.call(LegacyJnlpProtocolHandler.java:162)
at org.jenkinsci.remoting.engine.LegacyJnlpProtocolHandler$2.call(LegacyJnlpProtocolHandler.java:158)
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 hudson.remoting.Engine$1$1.run(Engine.java:98)
at java.lang.Thread.run(Thread.java:745)
Jan 27, 2018 6:00:39 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to sample.com:9150
Jan 27, 2018 6:00:39 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server reports protocol JNLP2-connect not supported, skipping
Jan 27, 2018 6:00:39 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server reports protocol JNLP-connect not supported, skipping
Jan 27, 2018 6:00:39 AM hudson.remoting.jnlp.Main$CuiListener error
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:651)
at hudson.remoting.Engine.innerRun(Engine.java:615)
at hudson.remoting.Engine.run(Engine.java:451)