NAME                                        READY   STATUS      RESTARTS   AGE
base-690f9                                  0/3     Pending     0          27s
base-d7jcx                                  3/3     Running     0          44h
ks-devops-5c8d695c5d-88qmj                  1/1     Running     0          27h
ks-devops-db-ctrl-job-cz72q                 0/1     Completed   0          13d
ks-devops-db-init-job-2kwpz                 0/1     Completed   0          13d
ks-jenkins-6bbc47dfd7-wk7lh                 1/1     Running     0          12d
nodejs-0kbd5                                0/3     Pending     0          27s
nodejs-0nrp1                                0/3     Pending     0          27s
nodejs-3h9qs                                0/3     Pending     0          27s
nodejs-475r4                                0/3     Pending     0          27s
nodejs-4ssq9                                2/3     Error       0          2d6h
nodejs-4thzf                                0/3     Pending     0          27s
nodejs-56nc5                                0/3     Pending     0          27s
nodejs-5psgc                                0/3     Pending     0          27s
nodejs-5szhz                                0/3     Pending     0          27s
nodejs-62r84                                0/3     Pending     0          27s
nodejs-6c9w4                                0/3     Pending     0          27s
nodejs-746pm                                0/3     Pending     0          27s
nodejs-8sf5z                                2/3     Error       0          5d2h
nodejs-9dgsh                                0/3     Pending     0          27s
nodejs-cmxnd                                0/3     Pending     0          27s
nodejs-d5kwq                                2/3     Error       0          5d
nodejs-dw0vz                                0/3     Pending     0          27s
nodejs-gcw1r                                0/3     Pending     0          27s
nodejs-m7bkw                                0/3     Pending     0          27s
nodejs-njwlk                                0/3     Pending     0          27s
nodejs-q29wk                                0/3     Pending     0          27s
nodejs-q97x6                                2/3     Error       0          5d3h
nodejs-qm5l4                                0/3     Pending     0          27s
nodejs-s38wv                                0/3     Pending     0          27s
nodejs-s5wfj                                2/3     Error       0          5d3h
nodejs-w6q4r                                0/3     Pending     0          27s
nodejs-zbqx5                                2/3     Error       0          5d3h
nodejs-zsh9p                                0/3     Pending     0          27s
uc-jenkins-update-center-69bdddbcbb-vmstm   1/1     Running     0          13d

ubuntu@ks-allinone:~$ kubectl logs nodejs-4ssq9 -n kubesphere-devops-system
Error from server (BadRequest): a container name must be specified for pod nodejs-4ssq9, choose one of: [jnlp docker-server nodejs]
ubuntu@ks-allinone:~$ kubectl logs nodejs-4ssq9 -n kubesphere-devops-system jnlp
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
Jan 28, 2019 3:27:32 AM hudson.remoting.jnlp.Main createEngine
INFO: Setting up agent: nodejs-4ssq9
Jan 28, 2019 3:27:32 AM hudson.remoting.jnlp.Main$CuiListener <init>
INFO: Jenkins agent is running in headless mode.
Jan 28, 2019 3:27:33 AM hudson.remoting.Engine startEngine
INFO: Using Remoting version: 3.27
Jan 28, 2019 3:27:33 AM hudson.remoting.Engine startEngine
WARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jars
Jan 28, 2019 3:27:33 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [http://ks-jenkins.kubesphere-devops-system:80/]
Jan 28, 2019 3:27:33 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
Jan 28, 2019 3:27:33 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability check
Jan 28, 2019 3:27:33 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
  Agent address: ks-jenkins-agent.kubesphere-devops-system
  Agent port:    50000
  Identity:      fd:af:11:ec:99:e1:b4:26:c0:fd:ed:8e:8a:49:30:5b
Jan 28, 2019 3:27:33 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Jan 28, 2019 3:27:33 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to ks-jenkins-agent.kubesphere-devops-system:50000
Jan 28, 2019 3:27:33 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Jan 28, 2019 3:27:33 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed: fd:af:11:ec:99:e1:b4:26:c0:fd:ed:8e:8a:49:30:5b
Jan 28, 2019 3:27:34 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected
Jan 28, 2019 3:27:39 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn
WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.Git$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/
Jan 28, 2019 3:27:41 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn
WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/
Jan 28, 2019 3:38:23 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Terminated
Jan 28, 2019 3:38:33 AM jenkins.slaves.restarter.JnlpSlaveRestarterInstaller$FindEffectiveRestarters$1 onReconnect
INFO: Restarting agent via jenkins.slaves.restarter.UnixSlaveRestarter@46588df2
Jan 28, 2019 3:38:37 AM hudson.remoting.jnlp.Main createEngine
INFO: Setting up agent: nodejs-4ssq9
Jan 28, 2019 3:38:37 AM hudson.remoting.jnlp.Main$CuiListener <init>
INFO: Jenkins agent is running in headless mode.
Jan 28, 2019 3:38:37 AM hudson.remoting.Engine startEngine
INFO: Using Remoting version: 3.27
Jan 28, 2019 3:38:37 AM hudson.remoting.Engine startEngine
WARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jars
Jan 28, 2019 3:38:37 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [http://ks-jenkins.kubesphere-devops-system:80/]
Jan 28, 2019 3:38:37 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
Jan 28, 2019 3:38:37 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability check
Jan 28, 2019 3:38:37 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
  Agent address: ks-jenkins-agent.kubesphere-devops-system
  Agent port:    50000
  Identity:      fd:af:11:ec:99:e1:b4:26:c0:fd:ed:8e:8a:49:30:5b
Jan 28, 2019 3:38:37 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Jan 28, 2019 3:38:37 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to ks-jenkins-agent.kubesphere-devops-system:50000
Jan 28, 2019 3:38:37 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Jan 28, 2019 3:38:37 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed: fd:af:11:ec:99:e1:b4:26:c0:fd:ed:8e:8a:49:30:5b
Jan 28, 2019 3:38:37 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv
INFO: [JNLP4-connect connection to ks-jenkins-agent.kubesphere-devops-system/10.233.0.2:50000] Local headers refused by remote: Unknown client name: nodejs-4ssq9
Jan 28, 2019 3:38:37 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: nodejs-4ssq9
	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: nodejs-4ssq9
	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

Jan 28, 2019 3:38:37 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to ks-jenkins-agent.kubesphere-devops-system:50000
Jan 28, 2019 3:38:37 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server reports protocol JNLP4-plaintext not supported, skipping
Jan 28, 2019 3:38:37 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Protocol JNLP3-connect is not enabled, skipping
Jan 28, 2019 3:38:37 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server reports protocol JNLP2-connect not supported, skipping
Jan 28, 2019 3:38:37 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server reports protocol JNLP-connect not supported, skipping
Jan 28, 2019 3:38:37 AM 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:675)
	at hudson.remoting.Engine.innerRun(Engine.java:639)
	at hudson.remoting.Engine.run(Engine.java:474)