-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Ubuntu 14.04.3 LTS, running the JRE 1.8.0_65-b17 and Jenkins 1.635
It would be great if this error could give better guidance as to what configuration option is missing or incorrect. Currently, I'm trying to setup my first Windows slave node and not having much luck.
From the Jenkins log ( http://host/jenkins/log/all ) :
Nov 19, 2015 2:02:51 AM WARNING hudson.plugins.ec2.win.WinConnection ping Failed to verify connectivity to Windows slave java.lang.IllegalArgumentException: Scheme may not be null at org.apache.http.util.Args.notNull(Args.java:48) at org.apache.http.conn.scheme.SchemeRegistry.register(SchemeRegistry.java:123) at hudson.plugins.ec2.win.winrm.WinRMClient.sendRequest(WinRMClient.java:220) at hudson.plugins.ec2.win.winrm.WinRMClient.sendRequest(WinRMClient.java:202) at hudson.plugins.ec2.win.winrm.WinRMClient.openShell(WinRMClient.java:85) at hudson.plugins.ec2.win.winrm.WinRM.ping(WinRM.java:29) at hudson.plugins.ec2.win.WinConnection.ping(WinConnection.java:117) at hudson.plugins.ec2.win.EC2WindowsLauncher.connectToWinRM(EC2WindowsLauncher.java:123) at hudson.plugins.ec2.win.EC2WindowsLauncher.launch(EC2WindowsLauncher.java:31) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:107) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:253) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
From the node log http://host/jenkins/computer/ :
Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-windows-host.compute-1.amazonaws.com(<<host ip>>) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-windows-host.compute-1.amazonaws.com(<<host ip>>) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-windows-host.compute-1.amazonaws.com(<<host ip>>) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-windows-host.compute-1.amazonaws.com(<<host ip>>) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-windows-host.compute-1.amazonaws.com(<<host ip>>) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-windows-host.compute-1.amazonaws.com(<<host ip>>) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-windows-host.compute-1.amazonaws.com(<<host ip>>) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-windows-host.compute-1.amazonaws.com(<<host ip>>) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-windows-host.compute-1.amazonaws.com(<<host ip>>) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-windows-host.compute-1.amazonaws.com(<<host ip>>) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-windows-host.compute-1.amazonaws.com(<<host ip>>) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-windows-host.compute-1.amazonaws.com(<<host ip>>) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s.
I experience this issue as well, 6 months later.