[JIRA] [ec2-plugin] (JENKINS-31641) Unclear error upon launching Windows build node

142 views
Skip to first unread message

brian.b.long@gmail.com (JIRA)

unread,
Nov 18, 2015, 9:14:02 PM11/18/15
to jenkinsc...@googlegroups.com
Brian L created an issue
 
Jenkins / Bug JENKINS-31641
Unclear error upon launching Windows build node
Issue Type: Bug Bug
Assignee: Francis Upton
Components: ec2-plugin
Created: 19/Nov/15 2:13 AM
Environment:  Ubuntu 14.04.3 LTS, running the JRE 1.8.0_65-b17 and Jenkins 1.635
Priority: Minor Minor
Reporter: Brian L

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.
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

bstewart@novetta.com (JIRA)

unread,
May 4, 2016, 2:16:01 PM5/4/16
to jenkinsc...@googlegroups.com
Brendan Stewart commented on Bug JENKINS-31641
 
Re: Unclear error upon launching Windows build node

I experience this issue as well, 6 months later.

anton.doar@gmail.com (JIRA)

unread,
Dec 19, 2018, 12:42:02 AM12/19/18
to jenkinsc...@googlegroups.com

Seems like a network or WinRM issue.

I would have tried the following from master while launching the instance:

  1. ping the instance (see if I were able to reach the machine)
  2. see that port is reachable with: 
    telnet <IP> 5985
  1. connect through pywinrm python module:

 

import winrm

s = winrm.Session('<IP>', auth=('administrator', '<password>'))
r = s.run_cmd('time', ['/t'])
print(r.std_out)

 

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

anton.doar@gmail.com (JIRA)

unread,
Dec 19, 2018, 12:43:02 AM12/19/18
to jenkinsc...@googlegroups.com
Anton Yurchenko edited a comment on Bug JENKINS-31641
Seems like a network or WinRM issue.

I would have tried the following from master while launching the instance:
# ping the instance (see if I were able to reach the machine)
# see that port is reachable with: 
{code:java}
telnet <IP> 5985{code}

# connect through *pywinrm* python module:

 
{code:java}

import winrm

s = winrm.Session('<IP>', auth=('administrator', '<password>'))
r = s.run_cmd('time', ['/t'])
print(r.std_out)
{code}
 

anton.doar@gmail.com (JIRA)

unread,
Dec 19, 2018, 12:44:02 AM12/19/18
to jenkinsc...@googlegroups.com
Anton Yurchenko edited a comment on Bug JENKINS-31641
Seems like a network or WinRM issue.

I would have tried the following from master while launching the instance:
# * ping the instance (see if I were able to reach the machine)
# * see that port is reachable with: 

{code:java}
telnet <IP> 5985{code}

#
* connect through *pywinrm* python module:


{code:java}
import winrm

s = winrm.Session('<IP>', auth=('administrator', '<password>'))
r = s.run_cmd('time', ['/t'])
print(r.std_out)
{code}
 
Reply all
Reply to author
Forward
0 new messages