-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
Jenkins master: Jenkins 2.235.3 on ubuntu, openjdk version "11.0.8" 2020-07-14
linux ubuntu agent: openjdk version "11.0.8" 2020-07-14
OpenJDK Runtime Environment (build 11.0.8+10-post-Ubuntu-0ubuntu120.04)
OpenJDK Server VM (build 11.0.8+10-post-Ubuntu-0ubuntu120.04, mixed mode)
Jenkins is behind nginx for TLS, with appropriate config for WS upgrade
Jenkins master: Jenkins 2.235.3 on ubuntu, openjdk version "11.0.8" 2020-07-14 linux ubuntu agent: openjdk version "11.0.8" 2020-07-14 OpenJDK Runtime Environment (build 11.0.8+10-post-Ubuntu-0ubuntu120.04) OpenJDK Server VM (build 11.0.8+10-post-Ubuntu-0ubuntu120.04, mixed mode) Jenkins is behind nginx for TLS, with appropriate config for WS upgrade
Trying to make a websocket agent connection to the master fails with
$ java -jar agent.jar -jnlpUrl https://j4.beeroclock.net/computer/s1-is.beeroclock.net/slave-agent.jnlp -secret @jenkins.locm3.secret-file -workDir /var/opt/jenkins-agent Aug 05, 2020 8:58:29 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using /var/opt/jenkins-agent/remoting as a remoting work directory Aug 05, 2020 8:58:29 PM org.jenkinsci.remoting.engine.WorkDirManager setupLogging INFO: Both error and output logs will be printed to /var/opt/jenkins-agent/remoting Aug 05, 2020 8:58:33 PM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: s1-is.beeroclock.net Aug 05, 2020 8:58:33 PM hudson.remoting.jnlp.Main$CuiListener <init> INFO: Jenkins agent is running in headless mode. Aug 05, 2020 8:58:33 PM hudson.remoting.Engine startEngine INFO: Using Remoting version: 4.3 Aug 05, 2020 8:58:33 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using /var/opt/jenkins-agent/remoting as a remoting work directory Aug 05, 2020 8:59:06 PM hudson.remoting.jnlp.Main$CuiListener error SEVERE: Handshake response not received. io.jenkins.remoting.shaded.javax.websocket.DeploymentException: Handshake response not received. at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$3$1.run(ClientManager.java:694) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$3.run(ClientManager.java:712) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager$SameThreadExecutorService.execute(ClientManager.java:866) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:511) at io.jenkins.remoting.shaded.org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:355) at hudson.remoting.Engine.runWebSocket(Engine.java:627) at hudson.remoting.Engine.run(Engine.java:469)
With the help of "halkeye" on IRC, we tested a newer remoting agent.jar (4.5) which also failed.
"halkeye" could connect happily as an agent to my master though, so we confirmed that the nginx configuration of my master was ok.
I could not connect to their master though, with either remoting 4.3 (from my master) or 4.5 (from theirs), confirming again that the master was not at fault here.
Finally, I downgraded my agent from jdk11 to jdk8, and it instantly started working.
This is a perfectly acceptable workaround to me, but (obviously) something that should get fixed
- duplicates
-
JENKINS-61212 CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
- Closed