-
Bug
-
Resolution: Fixed
-
Major
-
Jenkins running on Windows Server 2016
New version of Jenkins (2.249.1)
Java jdk1.8.0_101\bin\java.exe
After upgrade all workers fail to connect:
Sep 11, 2020 7:54:48 PM hudson.remoting.jnlp.Main$CuiListener <init> Sep 11, 2020 7:54:48 PM hudson.remoting.jnlp.Main$CuiListener <init> INFO: Jenkins agent is running in headless mode. Sep 11, 2020 7:54:48 PM hudson.remoting.Engine startEngine INFO: Using Remoting version: 3.29 Sep 11, 2020 7:54:48 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using D:\Jenkins\remoting as a remoting work directory Sep 11, 2020 7:54:48 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among [https://jenkins.cdl.af.mil/] Sep 11, 2020 7:54:48 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Sep 11, 2020 7:54:53 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver isPortVisible WARNING: connect timed out Sep 11, 2020 7:54:53 PM hudson.remoting.jnlp.Main$CuiListener error SEVERE: https://jenkins.cdl.af.mil/ provided port:51001 is not reachable java.io.IOException: https://jenkins.cdl.af.mil/ provided port:51001 is not reachable at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:287) at hudson.remoting.Engine.innerRun(Engine.java:523) at hudson.remoting.Engine.run(Engine.java:474) Sep 11, 2020 7:54:55 PM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: JenkinsWorkerOne Sep 11, 2020 7:54:55 PM hudson.remoting.jnlp.Main$CuiListener <init> INFO: Jenkins agent is running in headless mode. Sep 11, 2020 7:54:55 PM hudson.remoting.Engine startEngine INFO: Using Remoting version: 3.29 Sep 11, 2020 7:54:55 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using D:\Jenkins\remoting as a remoting work directory Sep 11, 2020 7:54:55 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among [https://jenkins.cdl.af.mil/]
After reverting to previous version (Jenkins 2.235.5) they all connect again.
Sep 11, 2020 8:37:00 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
Sep 11, 2020 8:37:00 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
Agent address: 10.101.0.203
Agent port: 52142
Identity: 40:97:48:b3:eb:09:11:33:91:c9:18:ab:c5:f2:91:25
Sep 11, 2020 8:37:00 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Sep 11, 2020 8:37:00 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to 10.101.0.203:52142
Sep 11, 2020 8:37:00 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Sep 11, 2020 8:37:00 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed: 40:97:48:b3:eb:09:11:33:91:c9:18:ab:c5:f2:91:25
Sep 11, 2020 8:37:01 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected
- relates to
-
JENKINS-63671 With Version 2.249.1 LTS the the Remote Agent over JNLP does not use the internal Hostname anymore
- Closed
- links to