Jenkins
Space shortcuts
Child pages
  • Windows slaves fail to start via JNLP

Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
  • Created by Unknown User (rseguy), last modified by Unknown User (mymarck) on Nov 10, 2015
Go to start of metadata

In some specific situations, when trying to instantiate a slave through JNLP, Java Web Start may raise an error saying that it's unable to run the application "Slave agent for <your machine>":

This occurs because the Hudson master node has used the loopback IP address (127.0.0.1) rather than using the standard (non-loopback) one.
This is clearly shown when going to the slave node's page in the Hudson console:

Here we can see that the IP loopback address appears several times, depicting the problem that occurs.

To fix it:

  • Go to the E-mail Notification section of the Hudson main configuration panel.
  • Set the Hudson URL using the non-loopback IP address.
  • No labels

1 Comment

  1. Unknown User (jstruck)

    it could also be that the port hudson trying to comunicate on is blocked in some firewall, because that hudson takes a new random port each time you restart it. this can be overwritten under Managed hudson -> Configure system -> Select "Enable security"
    Then u swicht TCP port for JNLP slave agents from Random to fixed and type ind the port u wish to use