[JIRA] (JENKINS-29798) Failed to listen to incoming slave connection after fixing port through init.groovy.d
Title: Message Title ovi craciun commented on JENKINS-29798 Re: Failed to listen to incoming slave connection after fixing port through init.groovy.d Brendan Holmes It's been several months and I really do not remember exactly how I got around this/fixed this. I think I just changed the port to the next one and it stopped having this problem. We encountered numerous problems with jenkins, to my unpleasant surprise. I am still astounded at how many problems one can encounter with jenkins vs its reputation in the wild. 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.164374.1438763471000.1199.1581966120181%40Atlassian.JIRA.
[JIRA] (JENKINS-29798) Failed to listen to incoming slave connection after fixing port through init.groovy.d
Title: Message Title ovi craciun updated an issue Jenkins / JENKINS-29798 Failed to listen to incoming slave connection after fixing port through init.groovy.d Change By: ovi craciun Comment: pls see my previous comment here:https://issues.jenkins-ci.org/browse/JENKINS-29798?focusedCommentId=380626=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-380626 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.164374.1438763471000.1194.1581965940254%40Atlassian.JIRA.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title
ovi craciun edited a comment on JENKINS-53952
Re: Linux slaves are not starting anymore
Jenkins ver. 2.204.2 EC2 plugin: 1.48we see a similar problem, it crashes on _getPrivateIpAddress_, or _getPublicIpAddress_ call depending on what I have chosen as connection strategy (public IP or private IP). the interesting part is this: it fails for spot inst images c5.2xlarge (or any higher, I made sure we bid enough to get those instances), if I use t2.2xlarge it works well.here's the error we are seeing{code:java}ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkinsjava.lang.NullPointerException at hudson.plugins.ec2.EC2HostAddressProvider.getPrivateIpAddress(EC2HostAddressProvider.java:49) at hudson.plugins.ec2.EC2HostAddressProvider.windows(EC2HostAddressProvider.java:28) at hudson.plugins.ec2.win.EC2WindowsLauncher.connectToWinRM(EC2WindowsLauncher.java:134) at hudson.plugins.ec2.win.EC2WindowsLauncher.launchScript(EC2WindowsLauncher.java:39) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:291) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source){code} Later edit: we updated the EC2 plugin to version [1.49.1|http://52.206.240.15:8080/pluginManager/plugin/ec2/thirdPartyLicenses] and it doesn't repro anymore.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title
ovi craciun edited a comment on JENKINS-53952
Re: Linux slaves are not starting anymore
Jenkins ver. 2.204.2 EC2 plugin: 1.48we see a similar problem, it crashes on _getPrivateIpAddress_, or _getPublicIpAddress_ call depending on what I have chosen as connection strategy (public IP or private IP). the interesting part is this: it fails for spot inst images c5.2xlarge (or any higher , I made sure we bid enough to get those instances ), if I use t2.2xlarge it works well.here's the error we are seeing{code:java}ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkinsjava.lang.NullPointerException at hudson.plugins.ec2.EC2HostAddressProvider.getPrivateIpAddress(EC2HostAddressProvider.java:49) at hudson.plugins.ec2.EC2HostAddressProvider.windows(EC2HostAddressProvider.java:28) at hudson.plugins.ec2.win.EC2WindowsLauncher.connectToWinRM(EC2WindowsLauncher.java:134) at hudson.plugins.ec2.win.EC2WindowsLauncher.launchScript(EC2WindowsLauncher.java:39) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:291) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source){code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title
ovi craciun edited a comment on JENKINS-53952
Re: Linux slaves are not starting anymore
Jenkins ver. 2.204.2 EC2 plugin: 1.48we see a similar problem, it crashes on _getPrivateIpAddress_, or _getPublicIpAddress_ call depending on what I have chosen as connection strategy (public IP or private IP). the interesting part is this: it fails for spot inst images c5.2xlarge (or any higher) , if I use t2.2xlarge it works well.here's the error we are seeing{code:java}ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkinsjava.lang.NullPointerException at hudson.plugins.ec2.EC2HostAddressProvider.getPrivateIpAddress(EC2HostAddressProvider.java:49) at hudson.plugins.ec2.EC2HostAddressProvider.windows(EC2HostAddressProvider.java:28) at hudson.plugins.ec2.win.EC2WindowsLauncher.connectToWinRM(EC2WindowsLauncher.java:134) at hudson.plugins.ec2.win.EC2WindowsLauncher.launchScript(EC2WindowsLauncher.java:39) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:291) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source){code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title
ovi craciun edited a comment on JENKINS-53952
Re: Linux slaves are not starting anymore
[ Jenkins ver. 2.204.2 EC2 plugin: 1.48we see a similar problem, it crashes on _getPrivateIpAddress_, or _getPublicIpAddress_ call depending on what I have chosen as connection strategy (public IP or private IP). the interesting part is this: it fails for spot inst images c5.2xlarge, if I use t2.2xlarge it works well.here's the error we are seeing{code:java}ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkinsjava.lang.NullPointerException at hudson.plugins.ec2.EC2HostAddressProvider.getPrivateIpAddress(EC2HostAddressProvider.java:49) at hudson.plugins.ec2.EC2HostAddressProvider.windows(EC2HostAddressProvider.java:28) at hudson.plugins.ec2.win.EC2WindowsLauncher.connectToWinRM(EC2WindowsLauncher.java:134) at hudson.plugins.ec2.win.EC2WindowsLauncher.launchScript(EC2WindowsLauncher.java:39) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:291) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source){code}
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
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title
ovi craciun edited a comment on JENKINS-53952
Re: Linux slaves are not starting anymore
[Jenkins ver. 2.204.2EC2 plugin: 1.48 |https://jenkins.io/] we see a similar problem, it crashes on _getPrivateIpAddress_, or _getPublicIpAddress_ call depending on what I have chosen as connection strategy (public IP or private IP). the interesting part is this: it fails for spot inst images c5.2xlarge, if I use t2.2xlarge it works well.here's the error we are seeing{code:java}ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkinsjava.lang.NullPointerException at hudson.plugins.ec2.EC2HostAddressProvider.getPrivateIpAddress(EC2HostAddressProvider.java:49) at hudson.plugins.ec2.EC2HostAddressProvider.windows(EC2HostAddressProvider.java:28) at hudson.plugins.ec2.win.EC2WindowsLauncher.connectToWinRM(EC2WindowsLauncher.java:134) at hudson.plugins.ec2.win.EC2WindowsLauncher.launchScript(EC2WindowsLauncher.java:39) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:291) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source){code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title ovi craciun commented on JENKINS-53952 Re: Linux slaves are not starting anymore [Jenkins ver. 2.204.2 EC2 plugin: 1.48 https://jenkins.io/] we see a similar problem, it crashes on getPrivateIpAddress, or getPublicIpAddress call depending on what I have chosen as connection strategy (public IP or private IP). the interesting part is this: it fails for spot inst images c5.2xlarge, if I use t2.2xlarge it works well. here's the error we are seeing ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.lang.NullPointerException at hudson.plugins.ec2.EC2HostAddressProvider.getPrivateIpAddress(EC2HostAddressProvider.java:49) at hudson.plugins.ec2.EC2HostAddressProvider.windows(EC2HostAddressProvider.java:28) at hudson.plugins.ec2.win.EC2WindowsLauncher.connectToWinRM(EC2WindowsLauncher.java:134) at hudson.plugins.ec2.win.EC2WindowsLauncher.launchScript(EC2WindowsLauncher.java:39) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:291) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Add Comment
[JIRA] (JENKINS-36516) EC2 plugin: Plugin fails to automatically launch slaves to meet demand
Title: Message Title
ovi craciun edited a comment on JENKINS-36516
Re: EC2 plugin: Plugin fails to automatically launch slaves to meet demand
still an issue with 1.48I can see this log but the spotinst mentioned is never spawned, no other error:```Spot instance id in provision: sir-px3sj14hSlaveTemplate{ami='ami-17de70f54e3bad981', labels='windows'}. Attempting provision finished, excess workload: 0We have now 5 computers, waiting for 1 more```and then```Started EC2 alive slaves monitorEC2 alive slaves monitor. 112 ms```and ```Available capacity=1, currentDemand=1Provisioning completedFinished ```however capacity is 0 cause there is a build in progress already and one in the waiting queue.and thus, the build queue keeps having that one waiting build to pe pushed to a provisioned slave but the slave is never provisioned. Later: even when there's no build in progress, I see this message`Available capacity=1, currentDemand=1`and a new slave is not provisioned when there's a build waiting in the build queue.How can I get around this mess?
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.172536.1467957761000.2569.1579518840811%40Atlassian.JIRA.
[JIRA] (JENKINS-36516) EC2 plugin: Plugin fails to automatically launch slaves to meet demand
Title: Message Title
ovi craciun edited a comment on JENKINS-36516
Re: EC2 plugin: Plugin fails to automatically launch slaves to meet demand
still an issue with 1.48I can see this log but the spotinst mentioned is never spawned, no other error:```Spot instance id in provision: sir-px3sj14hSlaveTemplate{ami='ami-17de70f54e3bad981', labels='windows'}. Attempting provision finished, excess workload: 0We have now 5 computers, waiting for 1 more```and then```Started EC2 alive slaves monitorEC2 alive slaves monitor. 112 ms```and ```Available capacity=1, currentDemand=1Provisioning completedFinished ```however capacity is 0 cause there is a build in progress already and one in the waiting queue .and thus, the build queue keeps having that one waiting build to pe pushed to a provisioned slave but the slave is never provisioned.
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.172536.1467957761000.1858.1579343762597%40Atlassian.JIRA.
[JIRA] (JENKINS-36516) EC2 plugin: Plugin fails to automatically launch slaves to meet demand
Title: Message Title
ovi craciun edited a comment on JENKINS-36516
Re: EC2 plugin: Plugin fails to automatically launch slaves to meet demand
still an issue with 1.48I can see this log but the spotinst mentioned is never spawned, no other error:```Spot instance id in provision: sir-px3sj14hSlaveTemplate{ami='ami-17de70f54e3bad981', labels='windows'}. Attempting provision finished, excess workload: 0We have now 5 computers, waiting for 1 more```and then```Started EC2 alive slaves monitor Finished EC2 alive slaves monitor. 112 ms``` and ```Available capacity=1, currentDemand=1Provisioning completedFinished ```however capacity is 0 cause there is a build in progress already.and thus, the build queue keeps having that one waiting build to pe pushed to a provisioned slave but the slave is never provisioned.
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.172536.1467957761000.1832.1579343761120%40Atlassian.JIRA.
[JIRA] (JENKINS-36516) EC2 plugin: Plugin fails to automatically launch slaves to meet demand
Title: Message Title
ovi craciun edited a comment on JENKINS-36516
Re: EC2 plugin: Plugin fails to automatically launch slaves to meet demand
still an issue with 1.48I can see this log but the spotinst mentioned is never spawned, no other error:```Spot instance id in provision: sir-px3sj14hSlaveTemplate{ami='ami-17de70f54e3bad981', labels='windows'}. Attempting provision finished, excess workload: 0We have now 5 computers, waiting for 1 more```and then```Started EC2 alive slaves monitorFinished EC2 alive slaves monitor. 112 ms```the build queue keeps having that one waiting build to pe pushed to a provisioned slave but the slave is never provisioned .
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.172536.1467957761000.1802.1579341960753%40Atlassian.JIRA.
[JIRA] (JENKINS-36516) EC2 plugin: Plugin fails to automatically launch slaves to meet demand
Title: Message Title
ovi craciun commented on JENKINS-36516
Re: EC2 plugin: Plugin fails to automatically launch slaves to meet demand
still an issue with 1.48 I can see this log but the spotinst mentioned is never spawned, no other error: ``` Spot instance id in provision: sir-px3sj14h SlaveTemplate {ami='ami-17de70f54e3bad981', labels='windows'} . Attempting provision finished, excess workload: 0 We have now 5 computers, waiting for 1 more ``` and then ``` Started EC2 alive slaves monitor Finished EC2 alive slaves monitor. 112 ms ``` the build queue keeps having that one waiting build to pe pushed to a provisioned slave.
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.172536.1467957761000.1776.1579341840606%40Atlassian.JIRA.
[JIRA] (JENKINS-60431) Cancel outdated jobs for Bitbucket Pull Requests Builder is not honored
Title: Message Title ovi craciun commented on JENKINS-60431 Re: Cancel outdated jobs for Bitbucket Pull Requests Builder is not honored ping 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.203503.1576024387000.10234.1576593840047%40Atlassian.JIRA.
[JIRA] (JENKINS-55524) Triggers on wrong branch when pushing multiple merges
Title: Message Title ovi craciun commented on JENKINS-55524 Re: Triggers on wrong branch when pushing multiple merges we are seeing this behavior 1. we have a project with "Build when a change is pushed to BitBucket" checked and "Branch Specifier (blank for 'any') " as origin/development. This one works as expected. 2. we have a second project with "Build when a change is pushed to BitBucket" checked and "Branch Specifier (blank for 'any') " as origin/master. This project is triggered for any commit to any branch. the only difference between the two projects is the branch it is supposed to build. 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.196657.1547153222000.5333.1576068900552%40Atlassian.JIRA.
[JIRA] (JENKINS-60431) Cancel outdated jobs for Bitbucket Pull Requests Builder is not honored
Title: Message Title ovi craciun created an issue Jenkins / JENKINS-60431 Cancel outdated jobs for Bitbucket Pull Requests Builder is not honored Issue Type: Bug Assignee: Unassigned Components: bitbucket-pullrequest-builder-plugin Created: 2019-12-11 00:33 Environment: Jenkins ver. 2.190.3 installed on Windows 2016 Priority: Critical Reporter: ovi craciun The option "Cancel outdated jobs?" although selected in "Bitbucket Pull Requests Builder" settings section is not honored. The build in progress is not cancelled by a new commit for the same PR, even worse, a new build is never triggered, so the PR gets approved although the latest commit was not built Add Comment
[JIRA] (JENKINS-12003) GIT_BRANCH not set on initial checkout
Title: Message Title ovi craciun commented on JENKINS-12003 Re: GIT_BRANCH not set on initial checkout Gyula Juhasz, so if it is the workspace that is the culprit, where the fix should go? How can one fix this situation in which $GIT_BRANCH is ending up incorrect? 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.142275.1323177235000.8772.1574947260368%40Atlassian.JIRA.
[JIRA] (JENKINS-29798) Failed to listen to incoming slave connection after fixing port through init.groovy.d
Title: Message Title ovi craciun edited a comment on JENKINS-29798 Re: Failed to listen to incoming slave connection after fixing port through init.groovy.d I can still see this happeningJenkins ver. 2.190.3, windows OSFailed to listen to incoming agent connectionsjava.net.BindException: Address already in use: bind at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Unknown Source) at sun.nio.ch.Net.bind(Unknown Source) at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source) at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source) at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source) at hudson.TcpSlaveAgentListener.(TcpSlaveAgentListener.java:103)Caused: java.net.BindException: Failed to listen on port 49994 because it's already in use. at hudson.TcpSlaveAgentListener.(TcpSlaveAgentListener.java:105) at jenkins.model.Jenkins.launchTcpSlaveAgentListener(Jenkins.java:1287) at jenkins.model.Jenkins.(Jenkins.java:983) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233)the netstat reveals the port is occupied by a process id which points to services.exeI did not installed any new app on this server, it is just another aws instance spawned. It used to work just fine before.I have serious reasons to believe this is a problem with how the port is binded first and then maybe lost the code flow is losing it and tries to bind again without releases the initial connection?... 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
[JIRA] (JENKINS-29798) Failed to listen to incoming slave connection after fixing port through init.groovy.d
Title: Message Title ovi craciun edited a comment on JENKINS-29798 Re: Failed to listen to incoming slave connection after fixing port through init.groovy.d I can still see this happeningJenkins ver. 2.190.3 , windows OS Failed to listen to incoming agent connectionsjava.net.BindException: Address already in use: bind at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Unknown Source) at sun.nio.ch.Net.bind(Unknown Source) at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source) at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source) at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source) at hudson.TcpSlaveAgentListener.(TcpSlaveAgentListener.java:103)Caused: java.net.BindException: Failed to listen on port 49994 because it's already in use. at hudson.TcpSlaveAgentListener.(TcpSlaveAgentListener.java:105) at jenkins.model.Jenkins.launchTcpSlaveAgentListener(Jenkins.java:1287) at jenkins.model.Jenkins.(Jenkins.java:983) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233)the netstat reveals the port is occupied by a process id which points to services.exeI did not installed any new app on this server, it is just another aws instance spawned. It used to work just fine before.I have serious reasons to believe this is a problem with how the port is binded first and then maybe lost in and tries to bind again without releases the initial connection?... 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
[JIRA] (JENKINS-29798) Failed to listen to incoming slave connection after fixing port through init.groovy.d
Title: Message Title ovi craciun reopened an issue pls see my previous comment here: https://issues.jenkins-ci.org/browse/JENKINS-29798?focusedCommentId=380626=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-380626 Jenkins / JENKINS-29798 Failed to listen to incoming slave connection after fixing port through init.groovy.d Change By: ovi craciun Resolution: Fixed Status: Resolved Reopened 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
[JIRA] (JENKINS-29798) Failed to listen to incoming slave connection after fixing port through init.groovy.d
Title: Message Title ovi craciun edited a comment on JENKINS-29798 Re: Failed to listen to incoming slave connection after fixing port through init.groovy.d I can still see this happening , there's no other app running on that port on my server Jenkins ver. 2.190.3 Failed to listen to incoming agent connectionsjava.net.BindException: Address already in use: bind at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Unknown Source) at sun.nio.ch.Net.bind(Unknown Source) at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source) at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source) at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source) at hudson.TcpSlaveAgentListener.(TcpSlaveAgentListener.java:103)Caused: java.net.BindException: Failed to listen on port 49994 because it's already in use. at hudson.TcpSlaveAgentListener.(TcpSlaveAgentListener.java:105) at jenkins.model.Jenkins.launchTcpSlaveAgentListener(Jenkins.java:1287) at jenkins.model.Jenkins.(Jenkins.java:983) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233) the netstat reveals the port is occupied by a process id which points to services.exeI did not installed any new app on this server, it is just another aws instance spawned. It used to work just fine before.I have serious reasons to believe this is a problem with how the port is binded first and then maybe lost in tries to bind again without releases the initial connection?... 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
[JIRA] (JENKINS-29798) Failed to listen to incoming slave connection after fixing port through init.groovy.d
Title: Message Title ovi craciun commented on JENKINS-29798 Re: Failed to listen to incoming slave connection after fixing port through init.groovy.d I can still see this happening, there's no other app running on that port on my server Failed to listen to incoming agent connections java.net.BindException: Address already in use: bind at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Unknown Source) at sun.nio.ch.Net.bind(Unknown Source) at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source) at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source) at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source) at hudson.TcpSlaveAgentListener.(TcpSlaveAgentListener.java:103) Caused: java.net.BindException: Failed to listen on port 49994 because it's already in use. at hudson.TcpSlaveAgentListener.(TcpSlaveAgentListener.java:105) at jenkins.model.Jenkins.launchTcpSlaveAgentListener(Jenkins.java:1287) at jenkins.model.Jenkins.(Jenkins.java:983) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233) 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.164374.1438763471000.7718.1574860980182%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-60258) NullPointerException using EC2-plugin version 1.46.1
Title: Message Title ovi craciun resolved as Cannot Reproduce Jenkins / JENKINS-60258 NullPointerException using EC2-plugin version 1.46.1 Change By: ovi craciun Status: Open Resolved Assignee: FABRIZIO MANFREDI ovi craciun Resolution: Cannot Reproduce 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.203245.1574601298000.6820.1574735580326%40Atlassian.JIRA.
[JIRA] (JENKINS-60258) NullPointerException using EC2-plugin version 1.46.1
Title: Message Title ovi craciun commented on JENKINS-60258 Re: NullPointerException using EC2-plugin version 1.46.1 I had a bunch of other plugins not up to date, I have updated them and now the error is gone. Those other plugins did not seem to be related at all with the EC2 plugin. Anyhow , I am glad I am passed this, but I am facing no a different issue, this one here: https://issues.jenkins-ci.org/browse/JENKINS-34610 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.203245.1574601298000.6818.1574734920165%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-60258) NullPointerException using EC2-plugin version 1.46.1
Title: Message Title
ovi craciun updated an issue
Jenkins / JENKINS-60258
NullPointerException using EC2-plugin version 1.46.1
Change By:
ovi craciun
Jenkins log shows this error when it is trying to provision a windows jenkins slave:{code:java}SlaveTemplate{ami='ami-0782a9361d328f5fb', labels='windows'}. Attempting to provision slave needed by excess workload of 1 unitsNov 24, 2019 1:10:00 PM SEVERE hudson.triggers.SafeTimerTask runTimer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@462f29b7 failedjava.lang.NullPointerException at hudson.plugins.ec2.EC2SpotSlave.getSpotRequest(EC2SpotSlave.java:123) at hudson.plugins.ec2.EC2Cloud.countCurrentEC2Slaves(EC2Cloud.java:482) at hudson.plugins.ec2.EC2Cloud.getPossibleNewSlavesCount(EC2Cloud.java:552) at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:570) at hudson.plugins.ec2.EC2Cloud.provision(EC2Cloud.java:615) at hudson.plugins.ec2.NoDelayProvisionerStrategy.apply(NoDelayProvisionerStrategy.java:47) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:332) at hudson.slaves.NodeProvisioner.access$900(NodeProvisioner.java:63) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:821) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.runAndReset(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source){code}I tried changing various configuration settings but did not manage to get around this error.Any clues what can I do?thank you *Later edit:*After restarting jenkins now, in the logs I can see this error which seems very much related:{code:java}Started EC2 alive slaves monitorNov 25, 2019 7:55:16 PM SEVERE hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtExceptionA thread (EC2 alive slaves monitor thread/202) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code. java.lang.NullPointerException at hudson.plugins.ec2.EC2SpotSlave.getSpotRequest(EC2SpotSlave.java:123) at hudson.plugins.ec2.EC2SpotSlave.isSpotRequestDead(EC2SpotSlave.java:144) at hudson.plugins.ec2.EC2SpotSlave.isAlive(EC2SpotSlave.java:60) at hudson.plugins.ec2.EC2SlaveMonitor.removeDeadNodes(EC2SlaveMonitor.java:49) at hudson.plugins.ec2.EC2SlaveMonitor.execute(EC2SlaveMonitor.java:40) at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:101) at java.lang.Thread.run(Unknown Source){code}
[JIRA] (JENKINS-60258) NullPointerException using EC2-plugin version 1.46.1
Title: Message Title
ovi craciun created an issue
Jenkins / JENKINS-60258
NullPointerException using EC2-plugin version 1.46.1
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2019-11-24 13:14
Environment:
Jenkins ver. 2.190.3 installed on windows server 2016 ec2 plugin version 1.46.1
Priority:
Critical
Reporter:
ovi craciun
Jenkins log shows this error when it is trying to provision a windows jenkins slave:
SlaveTemplate{ami='ami-0782a9361d328f5fb', labels='windows'}. Attempting to provision slave needed by excess workload of 1 units
Nov 24, 2019 1:10:00 PM SEVERE hudson.triggers.SafeTimerTask runTimer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@462f29b7 failed
java.lang.NullPointerException
at hudson.plugins.ec2.EC2SpotSlave.getSpotRequest(EC2SpotSlave.java:123)
at hudson.plugins.ec2.EC2Cloud.countCurrentEC2Slaves(EC2Cloud.java:482)
at hudson.plugins.ec2.EC2Cloud.getPossibleNewSlavesCount(EC2Cloud.java:552)
at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:570)
at hudson.plugins.ec2.EC2Cloud.provision(EC2Cloud.java:615)
at hudson.plugins.ec2.NoDelayProvisionerStrategy.apply(NoDelayProvisionerStrategy.java:47)
at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:332)
at hudson.slaves.NodeProvisioner.access$900(NodeProvisioner.java:63)
at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:821)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72)
at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58)
at
