-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
production
-
Powered by SuggestiMate
Hi Carlos
recently we upgraded the plugin to 1.13.5 and we have been observing the pods entering into error state and the builds that are running are getting killed.
INFO: Protocol JNLP4-connect encountered an unexpected exception E undefined java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: jnlp-xf91v at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474) Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: jnlp-xf91v 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:816) 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:816) 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:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Suppressed: java.nio.channels.ClosedChannelException ... 7 more E undefined
- is duplicated by
-
JENKINS-58409 java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name
-
- Closed
-
- is related to
-
JENKINS-53427 Agent creation failure because of concurrent attempts to schedule a pod
-
- Reopened
-
[JENKINS-54683] Pods entering error state due to ConnectionRefusalException: Unknown client name
This behaviour occurs when your job is running with Slave spawned in k8s and some job in the background calls Jenkins.instance.reload(). Jenkins instance forgets that it has a slave of such name and this exception occurs. I'd say either do not call Jenkins.instance.reload() or reload function should be able to not forget running slaves it has created.
Partial log from master:
Sep 03, 2019 9:49:05 AM io.fabric8.jenkins.openshiftsync.BuildConfigWatcher$3 call INFO: Updated job web2-bc-admin from BuildConfig NamespaceName{web2:bc-admin} with revision: 356707991 Sep 03, 2019 9:49:05 AM io.fabric8.jenkins.openshiftsync.CredentialsUtils upsertCredential INFO: Updated credential web2-jenkins-secret-bitbucket from Secret NamespaceName{web2:jenkins-secret-bitbucket} with revision: 171272636 Sep 03, 2019 9:49:05 AM io.fabric8.jenkins.openshiftsync.BuildSyncRunListener onStarted INFO: starting polling build job/web2/job/web2-bc-admin/3/ Sep 03, 2019 9:49:08 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Kubernetes agents: 1 Sep 03, 2019 9:49:08 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Template for label java11-maven35-nodejs8-boosted: Kubernetes Pod Template Sep 03, 2019 9:49:08 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Kubernetes Pod Template from openshift with 1 executors. Remaining excess workload: 0 Sep 03, 2019 9:49:18 AM hudson.slaves.NodeProvisioner$2 run INFO: Kubernetes Pod Template provisioning successfully completed. We have now 2 computer(s) Sep 03, 2019 9:49:18 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Created Pod: web2/java11-maven35-nodejs8-boosted-m3tvb Sep 03, 2019 9:49:18 AM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? Sep 03, 2019 9:49:22 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Pod is running: web2/java11-maven35-nodejs8-boosted-m3tvb Sep 03, 2019 9:49:22 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Waiting for agent to connect (0/100): java11-maven35-nodejs8-boosted-m3tvb Sep 03, 2019 9:49:23 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Waiting for agent to connect (1/100): java11-maven35-nodejs8-boosted-m3tvb Sep 03, 2019 9:49:24 AM hudson.TcpSlaveAgentListener$ConnectionHandler run INFO: Accepted JNLP4-connect connection #12 from /10.38.49.11:56832 Sep 03, 2019 9:49:24 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Waiting for agent to connect (2/100): java11-maven35-nodejs8-boosted-m3tvb Sep 03, 2019 9:49:25 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Waiting for agent to connect (3/100): java11-maven35-nodejs8-boosted-m3tvb Sep 03, 2019 9:49:26 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Waiting for agent to connect (4/100): java11-maven35-nodejs8-boosted-m3tvb Sep 03, 2019 9:49:27 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Waiting for agent to connect (5/100): java11-maven35-nodejs8-boosted-m3tvb INFO: Terminating Kubernetes instance for agent java11-maven35-nodejs8-boosted-m3tvb Sep 03, 2019 9:58:26 AM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? FATAL: Computer for agent is null: java11-maven35-nodejs8-boosted-m3tvb Sep 03, 2019 9:58:26 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave _terminate SEVERE: Computer for agent is null: java11-maven35-nodejs8-boosted-m3tvb Sep 03, 2019 9:58:26 AM jenkins.slaves.DefaultJnlpSlaveReceiver channelClosed WARNING: Computer.threadPoolForRemoting [#109] for java11-maven35-nodejs8-boosted-m3tvb terminated java.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:209) at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:181) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.switchToNoSecure(SSLEngineFilterLayer.java:283) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:503) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doCloseSend(SSLEngineFilterLayer.java:213) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doCloseSend(ProtocolStack.java:784) at org.jenkinsci.remoting.protocol.ApplicationLayer.doCloseWrite(ApplicationLayer.java:173) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer$ByteBufferCommandTransport.closeWrite(ChannelApplicationLayer.java:314) at hudson.remoting.Channel.close(Channel.java:1452) at hudson.remoting.Channel.close(Channel.java:1405) at hudson.slaves.SlaveComputer.closeChannel(SlaveComputer.java:832) at hudson.slaves.SlaveComputer.kill(SlaveComputer.java:799) at hudson.model.AbstractCIBase.killComputer(AbstractCIBase.java:88) at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:227) at jenkins.model.Jenkins.updateComputerList(Jenkins.java:1581) at jenkins.model.Nodes$6.run(Nodes.java:261) at hudson.model.Queue._withLock(Queue.java:1381) at hudson.model.Queue.withLock(Queue.java:1258) at jenkins.model.Nodes.removeNode(Nodes.java:252) at jenkins.model.Jenkins.removeNode(Jenkins.java:2096) at hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:70) at org.jenkinsci.plugins.durabletask.executors.OnceRetentionStrategy$1$1.run(OnceRetentionStrategy.java:128) at hudson.model.Queue._withLock(Queue.java:1381) at hudson.model.Queue.withLock(Queue.java:1258) at org.jenkinsci.plugins.durabletask.executors.OnceRetentionStrategy$1.run(OnceRetentionStrategy.java:123) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Sep 03, 2019 9:58:26 AM org.jenkinsci.plugins.workflow.job.WorkflowRun finish INFO: web2/web2-bc-admin #3 completed: FAILURE Sep 03, 2019 9:58:26 AM io.fabric8.jenkins.openshiftsync.BuildSyncRunListener onCompleted INFO: onCompleted job/web2/job/web2-bc-admin/3/ Sep 03, 2019 9:58:26 AM io.fabric8.jenkins.openshiftsync.BuildSyncRunListener onFinalized INFO: onFinalized job/web2/job/web2-bc-admin/3/ Sep 03, 2019 9:58:36 AM hudson.TcpSlaveAgentListener$ConnectionHandler run INFO: Accepted JNLP4-connect connection #13 from /10.38.49.11:57212 Sep 03, 2019 9:58:36 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv INFO: [JNLP4-connect connection from 10.38.49.11/10.38.49.11:57212] Refusing headers from remote: Unknown client name: java11-maven35-nodejs8-boosted-m3tvb Sep 03, 2019 9:58:36 AM hudson.TcpSlaveAgentListener$ConnectionHandler run WARNING: Connection #14 failed java.io.EOFException at java.io.DataInputStream.readFully(DataInputStream.java:197) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:244) Sep 03, 2019 10:00:12 AM io.fabric8.jenkins.openshiftsync.BuildWatcher eventReceived WARNING: Caught: java.lang.NullPointerException java.lang.NullPointerException at io.fabric8.jenkins.openshiftsync.JenkinsUtils.deleteRun(JenkinsUtils.java:566) at io.fabric8.jenkins.openshiftsync.JenkinsUtils.deleteRun(JenkinsUtils.java:575) at io.fabric8.jenkins.openshiftsync.BuildWatcher.innerDeleteEventToJenkinsJobRun(BuildWatcher.java:424) at io.fabric8.jenkins.openshiftsync.BuildWatcher.deleteEventToJenkinsJobRun(BuildWatcher.java:453) at io.fabric8.jenkins.openshiftsync.BuildWatcher.eventReceived(BuildWatcher.java:171) at io.fabric8.jenkins.openshiftsync.BuildWatcher.eventReceived(BuildWatcher.java:187) at io.fabric8.jenkins.openshiftsync.WatcherCallback.eventReceived(WatcherCallback.java:34) at io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager$2.onMessage(WatchConnectionManager.java:237) at okhttp3.internal.ws.RealWebSocket.onReadMessage(RealWebSocket.java:310) at okhttp3.internal.ws.WebSocketReader.readMessageFrame(WebSocketReader.java:222) at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:101) at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:265) at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:204) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:153) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Sep 03, 2019 10:00:12 AM io.fabric8.jenkins.openshiftsync.BuildWatcher eventReceived WARNING: Caught: java.lang.NullPointerException java.lang.NullPointerException at io.fabric8.jenkins.openshiftsync.JenkinsUtils.deleteRun(JenkinsUtils.java:566) at io.fabric8.jenkins.openshiftsync.JenkinsUtils.deleteRun(JenkinsUtils.java:575) at io.fabric8.jenkins.openshiftsync.BuildWatcher.innerDeleteEventToJenkinsJobRun(BuildWatcher.java:424) at io.fabric8.jenkins.openshiftsync.BuildWatcher.deleteEventToJenkinsJobRun(BuildWatcher.java:453) at io.fabric8.jenkins.openshiftsync.BuildWatcher.eventReceived(BuildWatcher.java:171) at io.fabric8.jenkins.openshiftsync.BuildWatcher.eventReceived(BuildWatcher.java:187) at io.fabric8.jenkins.openshiftsync.WatcherCallback.eventReceived(WatcherCallback.java:34) at io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager$2.onMessage(WatchConnectionManager.java:237) at okhttp3.internal.ws.RealWebSocket.onReadMessage(RealWebSocket.java:310) at okhttp3.internal.ws.WebSocketReader.readMessageFrame(WebSocketReader.java:222) at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:101) at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:265) at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:204) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:153) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Sep 03, 2019 10:00:12 AM io.fabric8.jenkins.openshiftsync.BuildWatcher eventReceived WARNING: Caught: java.lang.NullPointerException java.lang.NullPointerException at io.fabric8.jenkins.openshiftsync.JenkinsUtils.deleteRun(JenkinsUtils.java:566) at io.fabric8.jenkins.openshiftsync.JenkinsUtils.deleteRun(JenkinsUtils.java:575) at io.fabric8.jenkins.openshiftsync.BuildWatcher.innerDeleteEventToJenkinsJobRun(BuildWatcher.java:424) at io.fabric8.jenkins.openshiftsync.BuildWatcher.deleteEventToJenkinsJobRun(BuildWatcher.java:453) at io.fabric8.jenkins.openshiftsync.BuildWatcher.eventReceived(BuildWatcher.java:171) at io.fabric8.jenkins.openshiftsync.BuildWatcher.eventReceived(BuildWatcher.java:187) at io.fabric8.jenkins.openshiftsync.WatcherCallback.eventReceived(WatcherCallback.java:34) at io.fabric8.kubernetes.client.dsl.internal.WatchConnectionManager$2.onMessage(WatchConnectionManager.java:237) at okhttp3.internal.ws.RealWebSocket.onReadMessage(RealWebSocket.java:310) at okhttp3.internal.ws.WebSocketReader.readMessageFrame(WebSocketReader.java:222) at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:101) at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:265) at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:204) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:153) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
I've started seeing the same issue during last week. The 2.222.4 jenkins instance is running on GKE (v1.16.8-gke.15)
We are running Hive tests in a lot of pods - and the nodes are somewhat overloaded; I think this might contribute to the appearance of the issue - but definetly not sure
I've looked into the logs (no debug logs) - and something was odd:
- for regular pods - which are actually running stuff are mentioned multiple times in the jenkins master log - most importantly that they are being provisioned
- for pods which became "Errored" don't appear at all in the logs - only when they are rejected that they are not expected to be seen there
I don't know why; but I don't see the issue in the last 2 days (nothing have changed) ...I will probably change the debug level; but I would welcome any suggestions what to try...I really don't want to start babysitting this stuff
Hi, I was going to open a ticket for similar issue regarding the error "Unknown client name", however I will put my info here to save the additional duplicate ticket.
We have been seeing this issue intermittently across multiple jenkins deployments and disparate declarative jenkins pipelines with container configurations defined within the jenkinsfile. In our experience this issue occurs at agent initialization only before the pending job executes on the agent. The logs appear to indicate that jenkins master is able to talk to the kubernetes api, receives confirmation that the pod is created and running. With in 10 seconds of the jnlp pod starting it receives the following error message
INFO: Protocol JNLP4-connect encountered an unexpected exception java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: target-3qz0v-64sp9 at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:743) at hudson.remoting.Engine.run(Engine.java:518) Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: target-3qz0v-64sp9 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:816) 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:816) 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:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:117) at java.lang.Thread.run(Thread.java:748) Suppressed: java.nio.channels.ClosedChannelException ... 7 more Jan 14, 2021 10:43:09 PM 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:828) at hudson.remoting.Engine.innerRun(Engine.java:768) at hudson.remoting.Engine.run(Engine.java:518)
We are running our jenkins masters on a dedicated instances and have a mix between instances and kubernetes agents. This issue appears to be intermittent. It's not immediately clear what the contributing factors are however we have removed all references to Jenkins.instance.reload().
Jenkins version 2.263.1
Kubernetes plugin 1.27.7
FYI.
For me, no issue in following version.
Jenkins: 2.289.2-lts
kubernetes-plugin:1.30.0
got this issue also
automation-system-tests-e2e-942-9qz18-r6zpx 4/5 Error 0 7h22m root@jenkins:~| ⮕ kubectl logs -f automation-system-tests-e2e-942-9qz18-r6zpx jnlp Jun 19, 2022 10:47:29 PM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: automation-system-tests-e2e-ha-942-9qz18-r6zpx Jun 19, 2022 10:47:29 PM hudson.remoting.jnlp.Main$CuiListener <init> INFO: Jenkins agent is running in headless mode. Jun 19, 2022 10:47:29 PM hudson.remoting.Engine startEngine INFO: Using Remoting version: 4.11 Jun 19, 2022 10:47:29 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using /home/jenkins/agent/remoting as a remoting work directory Jun 19, 2022 10:47:29 PM org.jenkinsci.remoting.engine.WorkDirManager setupLogging INFO: Both error and output logs will be printed to /home/jenkins/agent/remoting Jun 19, 2022 10:47:29 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among [http://jenkins:8080/] Jun 19, 2022 10:47:29 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Jun 19, 2022 10:47:29 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability check Jun 19, 2022 10:47:29 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful Agent address: jenkins-agent Agent port: 50000 Identity: ef:1f:6a:33:e3:10:ab:87:8e:84:22:25:6e:32:2d:73 Jun 19, 2022 10:47:29 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Jun 19, 2022 10:47:29 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to jenkins-agent:50000 Jun 19, 2022 10:47:29 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP4-connect Jun 19, 2022 10:47:29 PM org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader run INFO: Waiting for ProtocolStack to start. Jun 19, 2022 10:47:29 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Remote identity confirmed: ef:1f:6a:33:e3:10:ab:87:8e:84:22:25:6e:32:2d:73 Jun 19, 2022 10:47:29 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connected Jun 19, 2022 10:48:29 PM hudson.remoting.RemoteInvocationHandler$Unexporter reportStats INFO: rate(1min) = 55.1±58.1/sec; rate(5min) = 102.2±41.5/sec; rate(15min) = 113.5±26.0/sec; rate(total) = 16.7±37.3/sec; N = 11 Jun 19, 2022 10:49:29 PM hudson.remoting.RemoteInvocationHandler$Unexporter reportStats INFO: rate(1min) = 20.3±44.1/sec; rate(5min) = 83.7±54.4/sec; rate(15min) = 106.1±37.5/sec; rate(total) = 8.0±27.1/sec; N = 23 Jun 19, 2022 11:17:43 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Terminated Jun 19, 2022 11:17:43 PM hudson.remoting.Request$2 run INFO: Failed to send back a reply to the request UserRequest:hudson.Launcher$RemoteLauncher$KillTask@2ede9e16: hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@4a6e46c8:JNLP4-connect connection to jenkins-a gent/10.43.88.50:50000": channel is already closed Jun 19, 2022 11:17:53 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Performing onReconnect operation. Jun 19, 2022 11:17:53 PM jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$EngineListenerAdapterImpl onReconnect INFO: Restarting agent via jenkins.slaves.restarter.UnixSlaveRestarter@33ff2c43 Jun 19, 2022 11:17:54 PM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: automation-system-tests-e2e-ha-942-9qz18-r6zpx Jun 19, 2022 11:17:54 PM hudson.remoting.jnlp.Main$CuiListener <init> INFO: Jenkins agent is running in headless mode. Jun 19, 2022 11:17:54 PM hudson.remoting.Engine startEngine INFO: Using Remoting version: 4.11 Jun 19, 2022 11:17:54 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using /home/jenkins/agent/remoting as a remoting work directory Jun 19, 2022 11:17:54 PM org.jenkinsci.remoting.engine.WorkDirManager setupLogging INFO: Both error and output logs will be printed to /home/jenkins/agent/remoting Jun 19, 2022 11:17:54 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among [http://jenkins:8080/] Jun 19, 2022 11:17:54 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Jun 19, 2022 11:17:54 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability check Jun 19, 2022 11:17:54 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful Agent address: jenkins-agent Agent port: 50000 Identity: ef:1f:6a:33:e3:10:ab:87:8e:84:22:25:6e:32:2d:73 Jun 19, 2022 11:17:54 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Jun 19, 2022 11:17:54 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to jenkins-agent:50000 Jun 19, 2022 11:17:54 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP4-connect Jun 19, 2022 11:17:54 PM org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader run INFO: Waiting for ProtocolStack to start. Jun 19, 2022 11:17:54 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Remote identity confirmed: ef:1f:6a:33:e3:10:ab:87:8e:84:22:25:6e:32:2d:73 Jun 19, 2022 11:17:54 PM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv INFO: [JNLP4-connect connection to jenkins-agent/10.43.88.50:50000] Local headers refused by remote: Unknown client name: automation-system-tests-e2e-942-9qz18-r6zpx Jun 19, 2022 11:17:54 PM 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: automation-system-tests-e2e-942-9qz18-r6zpx 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: automation-system-tests-e2e-942-9qz18-r6zpx 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.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:122) at java.base/java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more Jun 19, 2022 11:17:54 PM 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:864) at hudson.remoting.Engine.innerRun(Engine.java:804) at hudson.remoting.Engine.run(Engine.java:540)
Jenkins 2.332.3
kubernetes plugin 3600.v144b_cd192ca_a_
Got this also in
`Jenkins 2.346.1`
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.5+k3s1", GitCommit:"355fff3017b06cde44dbd879408a3a6826fa7125", GitTreeState:"clean", BuildDate:"2021-03-31T06:21:52Z", GoVersion:"go1.15.10", Co mpiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.5+k3s1", GitCommit:"355fff3017b06cde44dbd879408a3a6826fa7125", GitTreeState:"clean", BuildDate:"2021-03-31T06:21:52Z", GoVersion:"go1.15.10", Co mpiler:"gc", Platform:"linux/amd64"}
Kubernetes plugin Version 3651.v908e7db_10d06
INFO: Setting up agent: automation-tests-1398-rhjt0-0sp8t Jul 23, 2022 11:17:14 PM hudson.remoting.jnlp.Main$CuiListener <init> INFO: Jenkins agent is running in headless mode. Jul 23, 2022 11:17:14 PM hudson.remoting.Engine startEngine INFO: Using Remoting version: 4.11 Jul 23, 2022 11:17:14 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using /home/jenkins/agent/remoting as a remoting work directory Jul 23, 2022 11:17:14 PM org.jenkinsci.remoting.engine.WorkDirManager setupLogging INFO: Both error and output logs will be printed to /home/jenkins/agent/remoting Jul 23, 2022 11:17:14 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among [http://jenkins:8080/] Jul 23, 2022 11:17:15 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Jul 23, 2022 11:17:15 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability check Jul 23, 2022 11:17:15 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful Agent address: jenkins-agent Agent port: 50000 Identity: ef:1f:6a:33:e3:10:ab:87:8e:84:22:25:6e:32:2d:73 Jul 23, 2022 11:17:15 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Jul 23, 2022 11:17:15 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to jenkins-agent:50000 Jul 23, 2022 11:17:15 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP4-connect Jul 23, 2022 11:17:15 PM org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader run INFO: Waiting for ProtocolStack to start. Jul 23, 2022 11:17:15 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Remote identity confirmed: ef:1f:6a:33:e3:10:ab:87:8e:84:22:25:6e:32:2d:73 Jul 23, 2022 11:17:15 PM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv INFO: [JNLP4-connect connection to jenkins-agent/10.43.88.50:50000] Local headers refused by remote: Unknown client name: automation-tests-1398-rhjt0-0sp8t Jul 23, 2022 11:17:15 PM 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: automation-tests-1398-rhjt0-0sp8t 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: automation-tests-1398-rhjt0-0sp8t 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.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:122) at java.base/java.lang.Thread.run(Unknown Source) Suppressed: java.nio.channels.ClosedChannelException ... 7 more Jul 23, 2022 11:17:15 PM 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:864) at hudson.remoting.Engine.innerRun(Engine.java:804) at hudson.remoting.Engine.run(Engine.java:540)
The same error on below versions:
Jenkins: 2.346.2-lts
kubernetes-plugin: 3670.v6ca_059233222
INFO: Protocol JNLP4-connect encountered an unexpected exception
java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: devops-demo-test-p9wzp
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: devops-demo-test-p9wzp
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.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:122)
at java.base/java.lang.Thread.run(Unknown Source)
Suppressed: java.nio.channels.ClosedChannelException
... 7 more
Jul 25, 2022 5:18:41 PM 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:864)
at hudson.remoting.Engine.innerRun(Engine.java:804)
at hudson.remoting.Engine.run(Engine.java:540)
i can connect now. Need to set the command of non jnlp containers to sleep.
will provide the requested debugging logs by the end of the weekend.