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

Failed to connect to JNLP4 protocol

    Details

    • Type: Bug
    • Status: Fixed but Unreleased (View Workflow)
    • Priority: Minor
    • Resolution: Not A Defect
    • Component/s: virtualbox-plugin
    • Labels:
      None
    • Environment:
      Jenkins Version 2.195, Remoting Version 3.35
    • Similar Issues:

      Description

      When trying to connect the slave (run in a virtualbox environment) to the jenkins master, i encountered the following error:

      java.util.concurrent.ExecutionException:org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: MYNODE is not an inbound agent.

      It is able to discover the agent successfully but failed at JNLP4-connect.

      May i know how can i set MYNODE to be an inbound agent?

      Update on 19-Sep

      Have checked the Master log, it stated the following:

      "WARNING j.s.DefaultJnlpSlaveReceiver#afterProperties : Rejecting connection to MYNODE from XXXX/168.172.100.2:XXXX as an inbound agent as the launcher class hudson.plugins.virtualbox.VirtualBoxComputerLauncher does not extend JNLPLauncher or does not implement DelegatingComputerLauncher with a delegation chain leading to a JNLPLauncher. Set system property jenkins.slaves.DefaultJnlpSlaveReceiver.disableStrictVerification=true to allowconnections until the plugin has been fixed."

      The problem still persists with the above error message even after I have added the property -Djenkins.slaves.DefaultJnlpSlaveReceiver.disableStrictVerification=true into the <arguments> before -jar in jenkins.xml. Furthermore, i have verified inside "Manage Jenkins">"System Properties" that "jenkins.slaves.DefaultJnlpSlaveReceiver.disableStrictVerification" has indeed been set to "true".

      Thanks.

       

        Attachments

        1. error1.PNG
          error1.PNG
          65 kB
        2. error2.PNG
          error2.PNG
          36 kB

          Activity

          Hide
          xmredmi7a XM Red added a comment -

          Its due to jenkins.slaves.DefaultJnlpSlaveReceiver.disableStrictVerification not being set properly. After it has been set, restart the Jenkins server.

          Show
          xmredmi7a XM Red added a comment - Its due to jenkins.slaves.DefaultJnlpSlaveReceiver.disableStrictVerification not being set properly. After it has been set, restart the Jenkins server.

            People

            • Assignee:
              godin godin
              Reporter:
              xmredmi7a XM Red
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: