-
Bug
-
Resolution: Cannot Reproduce
-
Blocker
-
None
-
Jenkins 2.73.3
Kubernetes-Plugin 1.1.2
We are currently experiencing a critical regression in our Jenkins setup, with slaves erroring out with the following error (causing all builds to fail):
Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behavior Warning: SECRET is defined twice in command-line arguments and the environment variable Warning: AGENT_NAME is defined twice in command-line arguments and the environment variable Dec 04, 2017 4:36:26 PM hudson.remoting.jnlp.Main createEngine INFO: Setting up slave: jenkins-slave-r0jcd-lgp36 Dec 04, 2017 4:36:26 PM hudson.remoting.jnlp.Main$CuiListener <init> INFO: Jenkins agent is running in headless mode. Dec 04, 2017 4:36:26 PM hudson.remoting.Engine startEngine WARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jars Dec 04, 2017 4:36:26 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among [http://jenkins-internal.jenkins.svc.cluster.local:8080/] Dec 04, 2017 4:36:56 PM hudson.remoting.jnlp.Main$CuiListener error SEVERE: Failed to connect to http://jenkins-internal.jenkins.svc.cluster.local:8080/tcpSlaveAgentListener/: connect timed out java.io.IOException: Failed to connect to http://jenkins-internal.jenkins.svc.cluster.local:8080/tcpSlaveAgentListener/: connect timed out at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:161) at hudson.remoting.Engine.innerRun(Engine.java:495) at hudson.remoting.Engine.run(Engine.java:447) Caused by: java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.net.NetworkClient.doConnect(NetworkClient.java:175) at sun.net.www.http.HttpClient.openServer(HttpClient.java:463) at sun.net.www.http.HttpClient.openServer(HttpClient.java:558) at sun.net.www.http.HttpClient.<init>(HttpClient.java:242) at sun.net.www.http.HttpClient.New(HttpClient.java:339) at sun.net.www.http.HttpClient.New(HttpClient.java:357) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1202) at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1138) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1032) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:966) at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:158) ... 2 more
We have tried upgrading to latest but the error persists.
We are using https://hub.docker.com/r/jenkinsci/jnlp-slave/ which seems not to have been updated for the last 19 days so it's very difficult to see what has caused the regression as we have done no changes to our network conf.