Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-63568

Agent connection fails after update to 2.235.5

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
    • Environment:
      2.235.5 docker container
    • Similar Issues:

      Description

      We are using the Jenkins lts docker image. After upgrading from 2.204.5 to 2.235.5 and connect and agent by running "java -jar agent.jar -jnlpUrl https://jenkisserver/slave-agent.jnlp -secret XXXXXX -workDir "c:\Jenkins" -noCertificateCheck" results in:

       

      Skipping HTTPS certificate checks altogether. Note that this is not secure at all.
      syyskuuta 01, 2020 2:20:52 IP. org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
      INFO: Using c:\Jenkins\remoting as a remoting work directory
      syyskuuta 01, 2020 2:20:52 IP. org.jenkinsci.remoting.engine.WorkDirManager setupLogging
      INFO: Both error and output logs will be printed to c:\Jenkins\remoting
      syyskuuta 01, 2020 2:20:53 IP. hudson.remoting.jnlp.Main createEngine
      INFO: Setting up agent: Farids machine
      syyskuuta 01, 2020 2:20:53 IP. hudson.remoting.jnlp.Main$CuiListener <init>
      INFO: Jenkins agent is running in headless mode.
      syyskuuta 01, 2020 2:20:53 IP. hudson.remoting.jnlp.Main createEngine
      WARNING: Certificate validation for HTTPs endpoints is disabled
      syyskuuta 01, 2020 2:20:53 IP. hudson.remoting.Engine startEngine
      INFO: Using Remoting version: 4.3
      syyskuuta 01, 2020 2:20:53 IP. org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
      INFO: Using c:\Jenkins\remoting as a remoting work directory
      syyskuuta 01, 2020 2:20:53 IP. hudson.remoting.jnlp.Main$CuiListener status
      INFO: Locating server among [https://jenkisserver/]
      syyskuuta 01, 2020 2:20:53 IP. org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver openURLConnection
      WARNING: HTTPs certificate check is disabled for the endpoint.
      syyskuuta 01, 2020 2:20:53 IP. org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
      INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
      syyskuuta 01, 2020 2:20:53 IP. hudson.remoting.jnlp.Main$CuiListener status
      INFO: Agent discovery successful
        Agent address: jenkinsserver
        Agent port:    50000
        Identity:      36:9e:3f:0f:05:11:4c:fa:22:d0:29:4f:48:86:11:67
      syyskuuta 01, 2020 2:20:53 IP. hudson.remoting.jnlp.Main$CuiListener status
      INFO: Handshaking
      syyskuuta 01, 2020 2:20:53 IP. hudson.remoting.jnlp.Main$CuiListener status
      INFO: Connecting to jenkinsserver:50000
      syyskuuta 01, 2020 2:20:54 IP. hudson.remoting.jnlp.Main$CuiListener status
      INFO: Trying protocol: JNLP4-connect
      syyskuuta 01, 2020 2:20:54 IP. hudson.remoting.jnlp.Main$CuiListener status
      INFO: Remote identity confirmed: 36:9e:3f:0f:05:11:4c:fa:22:d0:29:4f:48:86:11:67
      syyskuuta 01, 2020 2:20:54 IP. org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv
      INFO: [JNLP4-connect connection to jenkinsserver/1.2.3.4:50000] Local headers refused by remote: Unknown client name: <AGENT NAME>
      syyskuuta 01, 2020 2:20:54 IP. 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: <AGENT NAME>
              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: <JOB NAME>
              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)
      

      This prevents us from updating. I only find issues with the Kubernetes plugin with the same error "Unknown client name: <AGENT NAME>". But we do not use that.

      We did this update on the Q system, using the very same command on P works perfectly so this came with the new version.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              tomko Tom Kostiainen
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: