[JIRA] (JENKINS-59429) Failed to connect to JNLP4 protocol

[xmredmi7a@gmail.com (JIRA)]

XM Red created an issue

Jenkins / JENKINS-59429 Failed to connect to JNLP4 protocol Issue Type: Bug Assignee: godin Components: virtualbox-plugin Created: 2019-09-18 09:30 Environment: Jenkins Version 2.195, Remoting Version 3.35 Priority: Minor Reporter: XM Red 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? Thanks.   Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[xmredmi7a@gmail.com (JIRA)]

XM Red updated an issue

Jenkins / JENKINS-59429 Failed to connect to JNLP4 protocol

Change By: XM Red Attachment: error1.PNG Attachment: error2.PNG

Add Comment

[xmredmi7a@gmail.com (JIRA)]

XM Red updated an issue

Jenkins / JENKINS-59429 Failed to connect to JNLP4 protocol Change By: XM Red

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 Thanks.

Add Comment

[xmredmi7a@gmail.com (JIRA)]

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.

Add Comment

[xmredmi7a@gmail.com (JIRA)]

XM Red updated an issue

Jenkins / JENKINS-59429 Failed to connect to JNLP4 protocol Change By: XM Red

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.

Add Comment

[xmredmi7a@gmail.com (JIRA)]

XM Red updated JENKINS-59429

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

Jenkins / JENKINS-59429 Failed to connect to JNLP4 protocol

Change By: XM Red Status: Open Fixed but Unreleased Resolution: Not A Defect

Add Comment