The instance EC2 Amazon-Linux 2 (i-xxxxxxxxxxxxx) has a blank console. Maybe the console is yet not available. If enough time has passed, consider changing the key verification strategy or the AMI used by one printing out the host key in the instance console ... INFO: The instance console is blank. Cannot check the key. The connection to EC2 Amazon-Linux 2 (i-xxxxxxxxxxxxx) is not allowed ... HTTP ERROR 404 Not Found
Windows EC2 seems super broke. Just updated the plugin, set host key verify to 'Off'
I verified the ports 5985 and 445 are both listening, and I can telnet in without issue. This worked without issue before I upgraded the plugin.
EC2 (MY-JENKINS) - win-on-demand (i-111111111111111) booted at 1595469330000
Connecting to (10.11.xxx.xxx) with WinRM as administrator
I managed to get WinRM back up and running manually updating to this PR build: https://ci.jenkins.io/job/Plugins/job/ec2-plugin/job/PR-481/2/artifact/org/jenkins-ci/plugins/ec2/1.51-rc1179.7d1283eb45d5/ec2-1.51-rc1179.7d1283eb45d5.hpi
From this PR: jenkinsci/ec2-plugin#481
What I'm finding is that SMB is able to finally connect. WinRM is still opening a ton of connections that linger on the Windows client side, so I don't think it's 100%. Seems to take a long time to spin up also.
Hey all, we're using spot instances for build agents and recently we are experiencing this issue where build agents were terminated halfway into an ongoing build. We traced the termination request back to
removeDeadNodes in the code, but we're not sure why were the agents considered dead while they are in the middle of building the project.
fetchLiveInstanceDatareturns to narrow down the issue, or
Any help is greatly appreciated, thanks!
-Dhudson.TcpSlaveAgentListener.hostName=$CONTROLLER_IPbut that setting ends up impacting ec2 windows agents failing to launch with an SSLException. This code throws SSL Exception: https://github.com/jenkinsci/ec2-plugin/blob/master/src/main/java/hudson/plugins/ec2/win/WinConnection.java#L121-L139.
-Dhudson.TcpSlaveAgentListener.hostName=$CONTROLLER_IP. Can reproduce on the latest ec2 plugin version and Jenkins 2.249.1.
2021-01-12 08:00:03.004+0000 [id=60] FINE h.p.e.NoDelayProvisionerStrategy#apply: Provisioning completed 2021-01-12 08:00:05.132+0000 [id=154] WARNING h.plugins.ec2.win.WinConnection#pingFailingIfSSHHandShakeError: Failed to verify connectivity to Windows slave java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:607) at hudson.plugins.ec2.win.WinConnection.pingFailingIfSSHHandShakeError(WinConnection.java:125) at hudson.plugins.ec2.win.EC2WindowsLauncher.connectToWinRM(EC2WindowsLauncher.java:189) at hudson.plugins.ec2.win.EC2WindowsLauncher.launchScript(EC2WindowsLauncher.java:52) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)