[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title KRUNAL PATIL commented on JENKINS-34610 Re: Windows AMI in endless loop I was facing same problem, I solved it by mentioning Remote user as "administrator" and then specifying admin password. Also make sure that SMB port 445 and Winrm port 5985(for http) or else winrm port 5986( in case you are using https) must allow incoming connections to it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170238.1462391043000.674.1577603280435%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title ovi craciun edited a comment on JENKINS-34610 Re: Windows AMI in endless loop I have managed to fix it, the culprit: port 445 need needs to be opened on the slave machines. More details here: https://stackoverflow.com/questions/38011683/how-to-run-windows-instance-on-ec2-from-jenkins Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170238.1462391043000.7118.1574768880376%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title ovi craciun commented on JENKINS-34610 Re: Windows AMI in endless loop I have managed to fix it, the culprit: port 445 need to be opened on the slave machines. More details here: https://stackoverflow.com/questions/38011683/how-to-run-windows-instance-on-ec2-from-jenkins Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170238.1462391043000.7107.1574768820423%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title
ovi craciun edited a comment on JENKINS-34610
Re: Windows AMI in endless loop
I am facing the same issue I have tried what [Alex Taylor|https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=ataylor] and [Brendan Stewart|https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=mumbles76] have suggested (all the settings for WinRM and everything else) but the master is still logging the same error:{code:java} EC2 (AWS ID account_id) - windows slave (sir-31i1js7h) booted at 1574726631000 Connecting to (17.30.6.34) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Waiting for WinRM to come up. Sleeping 10s.{code}However, I can telnet the slave on the 5985 port from master jenkins server and it connects. Does it mean it can't pass authentication or there's something else going won when the plugin is trying to connect via WinRM? The plugin doc is saying "By default, the plugin connects to the slave agent using an in-process Java SSH client.". What is the port is using the connect to this in-process ssh client? Any other ideas what should I try here? I've lost already two days to get this to work.Thank you
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170238.1462391043000.6991.1574760361297%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title
ovi craciun edited a comment on JENKINS-34610
Re: Windows AMI in endless loop
I am facing the same issue I have tried what [Alex Taylor|https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=ataylor] and [Brendan Stewart|https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=mumbles76] have suggested but the master is still logging the same error: ` {code:java} EC2 (AWS ID account_id) - windows slave (sir-31i1js7h) booted at 1574726631000 Connecting to (17.30.6.34) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Waiting for WinRM to come up. Sleeping 10s. ` {code} However, I can telnet the slave on the 5985 port from master jenkins server and it connects. Does it mean it can't pass authentication or there's something else going won when the plugin is trying to connect via WinRM?Any other ideas what should I try here? I've lost already two days to get this to work.Thank you
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170238.1462391043000.6839.1574739600674%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title
ovi craciun edited a comment on JENKINS-34610
Re: Windows AMI in endless loop
I am facing the same issue I have tried what [Alex Taylor|https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=ataylor] and [Brendan Stewart|https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=mumbles76] have suggested (all the settings for WinRM and everything else) but the master is still logging the same error:{code:java} EC2 (AWS ID account_id) - windows slave (sir-31i1js7h) booted at 1574726631000 Connecting to (17.30.6.34) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Waiting for WinRM to come up. Sleeping 10s.{code}However, I can telnet the slave on the 5985 port from master jenkins server and it connects. Does it mean it can't pass authentication or there's something else going won when the plugin is trying to connect via WinRM?Any other ideas what should I try here? I've lost already two days to get this to work.Thank you
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170238.1462391043000.6850.1574739600825%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title ovi craciun edited a comment on JENKINS-34610 Re: Windows AMI in endless loop I am facing the same issue I have tried what [ Alex Taylor |https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=ataylor] and [Brendan Stewart |https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=mumbles76]have suggested but the master is still logging the same error:`EC2 (AWS ID account_id) - windows slave (sir-31i1js7h) booted at 1574726631000 Connecting to (17.30.6.34) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Waiting for WinRM to come up. Sleeping 10s.`However, I can telnet the slave on the 5985 port from master jenkins server and it connects. Does it mean it can't pass authentication or there's something else going won when the plugin is trying to connect via WinRM?Any other ideas what should I try here? I've lost already two days to get this to work.Thank you Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170238.1462391043000.6808.1574734200325%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title ovi craciun edited a comment on JENKINS-34610 Re: Windows AMI in endless loop I am facing the same issue I have tried what Alex Taylor has and [Brendan Stewart |https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=mumbles76]have suggested but the master is still logging the same error:`EC2 (AWS ID account_id) - windows slave (sir-31i1js7h) booted at 1574726631000 Connecting to (17.30.6.34) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Waiting for WinRM to come up. Sleeping 10s.`However, I can telnet the slave on the 5985 port from master jenkins server and it connects. Does it mean it can't pass authentication or there's something else going won when the plugin is trying to connect via WinRM?Any other ideas what should I try here? I've lost already two days to get this to work.Thank you Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170238.1462391043000.6797.1574734140495%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title ovi craciun edited a comment on JENKINS-34610 Re: Windows AMI in endless loop I am facing the same issue I have tried what Alex Taylor has suggested but the master is still logging the same error:`EC2 (AWS ID account_id) - windows slave (sir-31i1js7h) booted at 1574726631000Connecting to (17.30.6.34) with WinRM as AdministratorWaiting for WinRM to come up. Sleeping 10s.Waiting for WinRM to come up. Sleeping 10s.`However, I can telnet the slave on the 5985 port from master jenkins server and it connects. Does it mean it can't pass authentication or there's something else going won when the plugin is trying to connect via WinRM?Any other ideas what should I try here? I've lost already two days to get this to work.Thank you Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170238.1462391043000.6655.1574729520547%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title ovi craciun commented on JENKINS-34610 Re: Windows AMI in endless loop I am facing the same issue I have tried what Alex Taylor has suggested but the master is still logging the same error: `EC2 (AWS ID account_id) - windows slave (sir-31i1js7h) booted at 1574726631000 Connecting to (17.30.6.34) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Waiting for WinRM to come up. Sleeping 10s.` However, I can telnet the slave on the 5985 port and it connects. Does it mean it can't pass authentication or there's something else going won when the plugin is trying to connect via WinRM? Any other ideas what should I try here? I've lost already two days to get this to work. Thank you Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170238.1462391043000.6638.1574728740349%40Atlassian.JIRA.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title
Alex Taylor edited a comment on JENKINS-34610
Re: Windows AMI in endless loop
We were able to get the windows agent to run by setting the "Allow remote server management through WinRM" IP settings to "*". Screenshot attached.We also had to run the below commands. !Screenshot 2019-05-09 11.58.27.png|thumbnail! {code:java} winrm quickconfig winrm set winrm/config/service/Auth @{Basic="true"} winrm set winrm/config/service @{AllowUnencrypted="true"} winrm set winrm/config/winrs @{MaxMemoryPerShellMB="10240"} {code} Should this exist on the wiki page [~francisu]? I was thinking there is not much "official troubleshooting" for windows EC2 connections and it seems lots of people are having troubles. !Screenshot 2019-05-09 11.58.27.png|thumbnail!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170238.1462391043000.1431.1557753362081%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title
Alex Taylor commented on JENKINS-34610
Re: Windows AMI in endless loop
We were able to get the windows agent to run by setting the "Allow remote server management through WinRM" IP settings to "*". Screenshot attached. We also had to run the below commands. winrm quickconfig winrm set winrm/config/service/Auth @ {Basic="true"} winrm set winrm/config/service @ {AllowUnencrypted="true"} winrm set winrm/config/winrs @ {MaxMemoryPerShellMB="10240"} Should this exist on the wiki page Francis Upton? I was thinking there is not much "official troubleshooting" for windows EC2 connections and it seems lots of people are having troubles.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170238.1462391043000.1422.1557753361938%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-34610 Windows AMI in endless loop Change By: Alex Taylor Attachment: Screenshot 2019-05-09 11.58.27.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170238.1462391043000.1394.1557753300439%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title Brendan Stewart commented on JENKINS-34610 Re: Windows AMI in endless loop Ultimately, opposite of my previous comment, we ended up giving up on this plugin for various reasons. But, we did enable all WinRm ports, including secure as well. That wasn't the cause of this issue. Thank you for getting back though. We hope to try and use it again in the future. But for our configuration it just wasn't up to the task. Perhaps it is today though, through bug fixing. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34610) Windows AMI in endless loop
Title: Message Title Peter Backx commented on JENKINS-34610 Re: Windows AMI in endless loop Thank you Brendan for this information. I also found another cause of connection issues: the Windows 10 server AMIs on Amazon will block incoming WinRM traffic from the public network by default (I think this is the default setting in Windows). This needs to be changed in the firewall rules. (BTW I would suggest to only allow traffic from the Jenkins master IP, either through the Windows firewall or the Amazon security group or both) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
