Jnlp container termination #Jenkins v2.346.1 #KubenetesPlugin

Hello Team,

Any one facing issue with Jnlp container termination in K8 agent? This is an intermittent issue and could not find the actual root cause.

Jenkins version – 2.346.2
Kubernetes plugin version - 3670.v6ca_059233222

JNLP container logs from k8 pod spinned by Jenkins + Kubernetes plugin.

INFO: Trying protocol: JNLP4-connect
Dec 29, 2022 7:13:08 AM org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader run
INFO: Waiting for ProtocolStack to start.
Dec 29, 2022 7:13:08 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed: 68:34:3f:05:d2:c3:2d:5d:a6:e1:c0:22:5b:54:f6:6c
Dec 29, 2022 7:13:08 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv
INFO: [JNLP4-connect connection to newjenkinsmaster.internal.cloudapp.net/10.10.0.4:5378] Local headers refused by remote: Unknown client name: aws-dns-builder-m69fl-mxv9j
Dec 29, 2022 7:13:08 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: Unknown client name: aws-dns-builder-m69fl-mxv9j
at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223)
at hudson.remoting.Engine.innerRun(Engine.java:778)
at hudson.remoting.Engine.run(Engine.java:540)
Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: aws-dns-builder-m69fl-mxv9j
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:825)
at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:288)
at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:170)
at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:825)
at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:49)
at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:255)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:122)
at java.lang.Thread.run(Thread.java:748)
Suppressed: java.nio.channels.ClosedChannelException
… 7 more

1 Like

This means the agent isn’t known by the Jenkins controller. Without looking at the controller logs there is no way to know.

1 Like