[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-53952) Linux slaves are not starting anymore
Title: Message Title Gil Shinar commented on JENKINS-53952 Re: Linux slaves are not starting anymore I have changed the configuration to use terminate/start instead of stop/start and for a week it works just fine. Maybe it might help solving this issue 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.194555.1539041035000.5337.1566204720562%40Atlassian.JIRA.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Gil Shinar commented on JENKINS-53952 Re: Linux slaves are not starting anymore Yesterday morning I came and it looked fine. This morning, again, all instances were up and all slaves were offline while there were a few jobs in the queue waiting for a long time. It's not just not starting the slaves, it's even worse, the instances are running and wasting money which is the opposite of what this plugin is all about. 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.194555.1539041035000.2479.1565765880889%40Atlassian.JIRA.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Gil Shinar commented on JENKINS-53952 Re: Linux slaves are not starting anymore OK. Seems like it got worse. Usually it happened during the weekend or after a night. Now slaves fails to start during the day I'm out of ideas 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.194555.1539041035000.1127.1565616420539%40Atlassian.JIRA.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Gil Shinar commented on JENKINS-53952 Re: Linux slaves are not starting anymore Installed 1.45 on my Jenkins. Upgraded from 1.43. Hopefully it'll solve the issue of slaves stuck in offline mode. Till today's morning, the issue was that the instances were up and running and the slaves were offline. Today's morning the instances were down as well as the slaves. 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.194555.1539041035000.905.1565591940935%40Atlassian.JIRA.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title FABRIZIO MANFREDI edited a comment on JENKINS-53952 Re: Linux slaves are not starting anymore merged in the 1.45 , can you confirm that is fixed ? 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.194555.1539041035000.463.1565463781329%40Atlassian.JIRA.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-53952 Re: Linux slaves are not starting anymore merged in the 1.45 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.194555.1539041035000.425.1565463721772%40Atlassian.JIRA.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title FABRIZIO MANFREDI started work on JENKINS-53952 Change By: FABRIZIO MANFREDI Status: Open In Progress 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.194555.1539041035000.427.1565463721794%40Atlassian.JIRA.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Michael Dodsworth commented on JENKINS-53952 Re: Linux slaves are not starting anymore Submitted a PR for this, if someone can take a look - https://github.com/jenkinsci/ec2-plugin/pull/367 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.194555.1539041035000.4768.1561058400427%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Jonathan B commented on JENKINS-53952 Re: Linux slaves are not starting anymore Any updates on this? This failure to start spot instances makes it infeasible for us to upgrade past 1.39, but the occasional deadlocks when spawning instances (fixed in 1.42, apparently https://issues.jenkins-ci.org/browse/JENKINS-54187) are extremely disruptive. 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.194555.1539041035000.25968.1560350466711%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Rajat Umrao updated an issue Jenkins / JENKINS-53952 Linux slaves are not starting anymore Change By: Rajat Umrao Labels: core ec2-plugin 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Rajat Umrao updated an issue Jenkins / JENKINS-53952 Linux slaves are not starting anymore Change By: Rajat Umrao Labels: ec2-plugin 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title
Rajat Umrao edited a comment on JENKINS-53952
Re: Linux slaves are not starting anymore
[~thoulen] The issue still persist in Plugin 1.42 as wellIssue occurs only using Spot instances, But work perfectly fine if use on-demand slaves.{code:java} // code placeholderApr Apr 01, 2019 1:17:45 PM hudson.plugins.ec2.EC2Cloud INFO: Launching instance: null Apr 01, 2019 1:17:45 PM hudson.plugins.ec2.EC2Cloud INFO: bootstrap() Apr 01, 2019 1:17:45 PM hudson.plugins.ec2.EC2Cloud INFO: Getting keypair... Apr 01, 2019 1:17:45 PM hudson.plugins.ec2.EC2Cloud INFO: Using key: access-key aa:d0:04:24:13:b4:e5:d8:88:09:6a:55:cb:a7:43:fd BEGIN RSA PRIVATE KEY MIIEpQIBAAKCAQEAxKuhBhKMikwrGYB/gWH1pBqATDR0WYW60dD6PtsLO0k76+ ntd9Mi5IS4u+V0ANiRP3Kc6d+IjrH2KmL45Y9OHMZcPRj9AoMOxz0yTRYd3sDeW Apr 01, 2019 1:17:45 PM hudson.plugins.ec2.EC2Cloud INFO: Authenticating as root ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.lang.NullPointerException at hudson.plugins.ec2.ssh.EC2UnixLauncher.getEC2HostAddress(EC2UnixLauncher.java:369) at hudson.plugins.ec2.ssh.EC2UnixLauncher.connectToSsh(EC2UnixLauncher.java:319) at hudson.plugins.ec2.ssh.EC2UnixLauncher.bootstrap(EC2UnixLauncher.java:283) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:130) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer$1.call(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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748){code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title
Rajat Umrao edited a comment on JENKINS-53952
Re: Linux slaves are not starting anymore
[~thoulen] The issue still persist in Plugin 1.42 as wellIssue occurs only using Spot instances, But work perfectly fine if use on-demand slaves.{code:java}// code placeholder{code}Apr placeholderApr 01, 2019 1:17:45 PM hudson.plugins.ec2.EC2Cloud INFO: Launching instance: null Apr 01, 2019 1:17:45 PM hudson.plugins.ec2.EC2Cloud INFO: bootstrap() Apr 01, 2019 1:17:45 PM hudson.plugins.ec2.EC2Cloud INFO: Getting keypair... Apr 01, 2019 1:17:45 PM hudson.plugins.ec2.EC2Cloud INFO: Using key: access-key aa:d0:04:24:13:b4:e5:d8:88:09:6a:55:cb:a7:43:fd - BEGIN RSA PRIVATE KEY - MIIEpQIBAAKCAQEAxKuhBhKMikwrGYB/gWH1pBqATDR0WYW60dD6PtsLO0k76+ ntd9Mi5IS4u+V0ANiRP3Kc6d+IjrH2KmL45Y9OHMZcPRj9AoMOxz0yTRYd3sDeW Apr 01, 2019 1:17:45 PM hudson.plugins.ec2.EC2Cloud INFO: Authenticating as root ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.lang.NullPointerException at hudson.plugins.ec2.ssh.EC2UnixLauncher.getEC2HostAddress(EC2UnixLauncher.java:369) at hudson.plugins.ec2.ssh.EC2UnixLauncher.connectToSsh(EC2UnixLauncher.java:319) at hudson.plugins.ec2.ssh.EC2UnixLauncher.bootstrap(EC2UnixLauncher.java:283) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:130) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer$1.call(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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Rajat Umrao commented on JENKINS-53952 Re: Linux slaves are not starting anymore FABRIZIO MANFREDI The issue still persist in Plugin 1.42 as well Issue occurs only using Spot instances, But work perfectly fine if use on-demand slaves. // code placeholder Apr 01, 2019 1:17:45 PM hudson.plugins.ec2.EC2Cloud INFO: Launching instance: null Apr 01, 2019 1:17:45 PM hudson.plugins.ec2.EC2Cloud INFO: bootstrap() Apr 01, 2019 1:17:45 PM hudson.plugins.ec2.EC2Cloud INFO: Getting keypair... Apr 01, 2019 1:17:45 PM hudson.plugins.ec2.EC2Cloud INFO: Using key: access-key aa:d0:04:24:13:b4:e5:d8:88:09:6a:55:cb:a7:43:fd BEGIN RSA PRIVATE KEY MIIEpQIBAAKCAQEAxKuhBhKMikwrGYB/gWH1pBqATDR0WYW60dD6PtsLO0k76+ ntd9Mi5IS4u+V0ANiRP3Kc6d+IjrH2KmL45Y9OHMZcPRj9AoMOxz0yTRYd3sDeW Apr 01, 2019 1:17:45 PM hudson.plugins.ec2.EC2Cloud INFO: Authenticating as root ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.lang.NullPointerException at hudson.plugins.ec2.ssh.EC2UnixLauncher.getEC2HostAddress(EC2UnixLauncher.java:369) at hudson.plugins.ec2.ssh.EC2UnixLauncher.connectToSsh(EC2UnixLauncher.java:319) at hudson.plugins.ec2.ssh.EC2UnixLauncher.bootstrap(EC2UnixLauncher.java:283) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:130) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer$1.call(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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) Add Comment
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title
Anton Yurchenko edited a comment on JENKINS-53952
Re: Linux slaves are not starting anymore
We've got the same issue. Jenkins ver 2.150.1, plugin version 1.41.+That issue occurs only when requesting a spot instance.+{code:java}Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: Launching instance: nullDec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: bootstrap()Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: Getting keypair...Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2CloudINFO: Using key: ssh-key[..]Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2CloudINFO: Authenticating as ec2-userERROR: Unexpected error in launching an agent. This is probably a bug in Jenkinsjava.lang.NullPointerException at hudson.plugins.ec2.ssh.EC2UnixLauncher.getEC2HostAddress(EC2UnixLauncher.java:367) at hudson.plugins.ec2.ssh.EC2UnixLauncher.connectToSsh(EC2UnixLauncher.java:319) at hudson.plugins.ec2.ssh.EC2UnixLauncher.bootstrap(EC2UnixLauncher.java:283) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:130) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer$1.call(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){code}{code:java}Dec 19, 2018 7:27:35 AM hudson.plugins.ec2.SlaveTemplate provisionSpotINFO: Launching ami-04750af7488d87g5c for template builderDec 19, 2018 7:27:36 AM hudson.plugins.ec2.SlaveTemplate provisionSpotINFO: Spot instance id in provision: sir-8mki4f8kDec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2RetentionStrategy startINFO: Start requested for builder (sir-8mki4f8k)Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2Cloud logINFO: Launching instance: nullDec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2Cloud logINFO: bootstrap()Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2Cloud logINFO: Getting keypair...Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2Cloud logINFO: Using key: ssh-key[]Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2Cloud logINFO: Authenticating as ec2-user{code} Manually clicking *Launch Agent* works and instances comes online fine.
Add Comment
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Anton Yurchenko commented on JENKINS-53952 Re: Linux slaves are not starting anymore We've got the same issue. Jenkins ver 2.150.1, plugin version 1.41. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title
Anton Yurchenko edited a comment on JENKINS-53952
Re: Linux slaves are not starting anymore
We've got the same issue. Jenkins ver 2.150.1, plugin version 1.41. +That issue occurs only when requesting a spot instance.+ {code:java}Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: Launching instance: nullDec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: bootstrap()Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: Getting keypair...Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2CloudINFO: Using key: ssh-key[..]Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2CloudINFO: Authenticating as ec2-userERROR: Unexpected error in launching an agent. This is probably a bug in Jenkinsjava.lang.NullPointerException at hudson.plugins.ec2.ssh.EC2UnixLauncher.getEC2HostAddress(EC2UnixLauncher.java:367) at hudson.plugins.ec2.ssh.EC2UnixLauncher.connectToSsh(EC2UnixLauncher.java:319) at hudson.plugins.ec2.ssh.EC2UnixLauncher.bootstrap(EC2UnixLauncher.java:283) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:130) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer$1.call(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){code} +That issue occurs only when requesting a spot {code:java}Dec 19, 2018 7:27:35 AM hudson.plugins.ec2.SlaveTemplate provisionSpotINFO: Launching ami-04750af7488d87g5c for template builderDec 19, 2018 7:27:36 AM hudson.plugins.ec2.SlaveTemplate provisionSpotINFO: Spot instance id in provision: sir-8mki4f8kDec 19, 2018 7:27:36 AM hudson . + plugins.ec2.EC2RetentionStrategy startINFO: Start requested for builder (sir-8mki4f8k)Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2Cloud logINFO: Launching instance: nullDec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2Cloud logINFO: bootstrap()Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2Cloud logINFO: Getting keypair...Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2Cloud logINFO: Using key: ssh-key[]Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2Cloud logINFO: Authenticating as ec2-user{code}
Add Comment
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title
Anton Yurchenko edited a comment on JENKINS-53952
Re: Linux slaves are not starting anymore
We've got the same issue. Jenkins ver 2.150.1, plugin version 1.41. {code:java}Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: Launching instance: nullDec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: bootstrap()Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: Getting keypair...Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2CloudINFO: Using key: ssh-key[..]Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2CloudINFO: Authenticating as ec2-userERROR: Unexpected error in launching an agent. This is probably a bug in Jenkinsjava.lang.NullPointerException at hudson.plugins.ec2.ssh.EC2UnixLauncher.getEC2HostAddress(EC2UnixLauncher.java:367) at hudson.plugins.ec2.ssh.EC2UnixLauncher.connectToSsh(EC2UnixLauncher.java:319) at hudson.plugins.ec2.ssh.EC2UnixLauncher.bootstrap(EC2UnixLauncher.java:283) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:130) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer$1.call(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){code}+That issue occurs only when requesting a spot instance.+
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.
For more options, visit
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Gunter Grodotzki commented on JENKINS-53952 Re: Linux slaves are not starting anymore Still having it with c5.xlarge + plugin version 1.41 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title FABRIZIO MANFREDI updated an issue Jenkins / JENKINS-53952 Linux slaves are not starting anymore Change By: FABRIZIO MANFREDI Comment: [https://github.com/jenkinsci/ec2-plugin/pull/252 :|https://github.com/jenkinsci/ec2-plugin/pull/252]It implements very simple algorithm: * if NodeProvisioner requested X executors, start to raiseX/N nodes (N is number of executors on each node). * if there is any orphant nodes (~not known by Jenkins at all), takethem in account (and start if it's neccessary) * if there is not enough orphant nodes - raise needed nodes in parallel * give them back to NodeProvisioner in RUNNING state 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-53952 Re: Linux slaves are not starting anymore https://github.com/jenkinsci/ec2-plugin/pull/252 : It implements very simple algorithm: if NodeProvisioner requested X executors, start to raise X/N nodes (N is number of executors on each node). if there is any orphant nodes (~not known by Jenkins at all), take them in account (and start if it's neccessary) if there is not enough orphant nodes - raise needed nodes in parallel give them back to NodeProvisioner in RUNNING state 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Matt Hoy commented on JENKINS-53952 Re: Linux slaves are not starting anymore Seeing identical issue using M5.Xlarge, latest Jenkins, and Spot Instances. If I hit "Launch Agent" before the timeout is hit, but after it's completed booting it is successfully able to add it. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Nick Lloyd commented on JENKINS-53952 Re: Linux slaves are not starting anymore We consistently hit this error using spot instances with the latest LTS Jenkins version. Using spot instances in a VPC with no public IP. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Perrin Morrow commented on JENKINS-53952 Re: Linux slaves are not starting anymore We just started hitting this. We've been running 1.40.1 for a couple of days (and the latest Jenkins version) without seeing it but then I added a new agent template, and trying to manually launch an agent from the template caused this error to occur. I haven't seen it in any of the instances that were started by the node provisioner, but I do see it when I manually launch an agent using one of the templates that has been working fine for the last few days. It doesn't happen every time though. We use spot instances, in a VPC, with no public IP. The instance is left running afterwards. I haven't seen it happen with on-demand instances. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-53952 Re: Linux slaves are not starting anymore Do you know if the spot instance after the restart is still alive ? Are you in VPC or in Default ? Are you using public IP ? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Ross Derewianko commented on JENKINS-53952 Re: Linux slaves are not starting anymore I've found this hit or miss, sometimes it happens sometimes it doesn't. Mostly it happens when we've changed pre-existing connections and it only happens for spot instances. Switching our instances to on demand does not have the same problem. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Gunter Grodotzki created an issue Jenkins / JENKINS-53952 Linux slaves are not starting anymore Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2018-10-08 23:23 Environment: Jenkins ver. 2.138.1 Priority: Blocker Reporter: Gunter Grodotzki Similar to https://issues.jenkins-ci.org/browse/JENKINS-53876 Unfortunately with the latest 1.40.1 EC2 nodes are not launching anymore: $ cat Jenkins\ Prebuilt\ Slave\ \(sir-p9ai6v8m\)/slave.log Oct 08, 2018 10:43:49 PM hudson.plugins.ec2.EC2Cloud INFO: Launching instance: null Oct 08, 2018 10:43:49 PM hudson.plugins.ec2.EC2Cloud INFO: bootstrap() Oct 08, 2018 10:43:49 PM hudson.plugins.ec2.EC2Cloud INFO: Getting keypair... Oct 08, 2018 10:43:49 PM hudson.plugins.ec2.EC2Cloud INFO: Using key: master xxx -BEGIN RSA PRIVATE KEY- xxx Oct 08, 2018 10:43:49 PM hudson.plugins.ec2.EC2Cloud INFO: Authenticating as ubuntu ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.lang.NullPointerException at hudson.plugins.ec2.ssh.EC2UnixLauncher.getEC2HostAddress(EC2UnixLauncher.java:368) at hudson.plugins.ec2.ssh.EC2UnixLauncher.connectToSsh(EC2UnixLauncher.java:318) at hudson.plugins.ec2.ssh.EC2UnixLauncher.bootstrap(EC2UnixLauncher.java:282) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:130) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at
