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

AWS linux master - windows 2012R2 slaves won't start via JNLP

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Duplicate
    • Component/s: core, slave-setup-plugin
    • Labels:
      None
    • Environment:
      centos7 linux master, windows 2012R2 64 bit slave - both machines are ec2 instances in AWS
      java 1.8
      no reverse proxy or tomcat container
      IE version 11
    • Similar Issues:

      Description

      This setup works fine with Jenkins war org.jenkins-ci.main:jenkins-war:1.649, but the latest jenkins on a new server/slave doesn't work. The only way I was able to get the slave to start is on the command line and then I created a bat file which is kicked off by the task scheduler.
      I have tried this on 2 different setups. I tried all the methods here: https://wiki.jenkins-ci.org/display/JENKINS/Step+by+step+guide+to+set+up+master+and+slave+machines, and https://support.cloudbees.com/hc/en-us/articles/217423827-How-to-Install-Several-Windows-Slaves-as-a-Service, and https://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM.
      The error message is: java.net.MalformedURLException: no protocol: jnlpJars/slave.jar

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                peppe Giuseppe Landolfi
                Reporter:
                funeeldy marlene cote
              • Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: