[JIRA] (JENKINS-59137) Connectivity issues with ec2 slaves
Title: Message Title Toni Van de Voorde commented on JENKINS-59137 Re: Connectivity issues with ec2 slaves Raihaan Shouhell Updated the wiki => https://wiki.jenkins.io/display/JENKINS/Amazon+EC2+Plugin#AmazonEC2Plugin-KnownIssues Cheers 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.201569.1567062958000.5541.1567511700095%40Atlassian.JIRA.
[JIRA] (JENKINS-59137) Connectivity issues with ec2 slaves
Title: Message Title Toni Van de Voorde resolved as Not A Defect Jenkins / JENKINS-59137 Connectivity issues with ec2 slaves Change By: Toni Van de Voorde Status: Open Resolved Assignee: FABRIZIO MANFREDI Raihaan Shouhell Resolution: Not A Defect 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.201569.1567062958000.5517.1567509840935%40Atlassian.JIRA.
[JIRA] (JENKINS-59137) Connectivity issues with ec2 slaves
Title: Message Title Toni Van de Voorde commented on JENKINS-59137 Re: Connectivity issues with ec2 slaves Raihaan Shouhell I will update the wiki. Cheers 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.201569.1567062958000.5513.1567509780258%40Atlassian.JIRA.
[JIRA] (JENKINS-59137) Connectivity issues with ec2 slaves
Title: Message Title Toni Van de Voorde commented on JENKINS-59137 Re: Connectivity issues with ec2 slaves Found the culprit. From the documentation for the Amazon Linux (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-ami-basics.html#security-updates) it states: Amazon Linux is configured to download and install security updates at launch time.[...] The default setting for repo_upgrade is security. That is, if you don't specify a different value in your user data, by default, Amazon Linux performs the security upgrades at launch for any packages installed at that time Since I had pre-installed the java library, after some days/weeks there was probably an update, and the security updates kicked in messing everything up!!! So this is not something this plugin can prevent, but maybe we can have some FAQ or some "Known Issues" section? 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.201569.1567062958000.5405.1567499280242%40Atlassian.JIRA.
[JIRA] (JENKINS-59137) Connectivity issues with ec2 slaves
Title: Message Title Toni Van de Voorde commented on JENKINS-59137 Re: Connectivity issues with ec2 slaves Raihaan Shouhell true, and I saw that in the logs. But since the AMI contained a java version, it shouldn't change it right? Or does it look for a specific version? If not, maybe the issue could be linked to the amazon linux AMI? Maybe it contains some update mechanism I'm not aware of? 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.201569.1567062958000.5287.1567493880822%40Atlassian.JIRA.
[JIRA] (JENKINS-59137) Connectivity issues with ec2 slaves
Title: Message Title Toni Van de Voorde commented on JENKINS-59137 Re: Connectivity issues with ec2 slaves Hi Raihaan Shouhell, But before I didn't had any cloud-init script ... I had a simple pre-baked AMI, but somehow the JDK got update through something which I can't explain at this point ... So either the cloud-init script fixed my issue (but that doesn't seem to be the case from what you are writing), or simply the fact that the jenkins master installs the java now on the slaves, fixed the issue ... In any case with simply a pre-baked AMI it started to fail ... 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.201569.1567062958000.5268.1567489740225%40Atlassian.JIRA.
[JIRA] (JENKINS-59137) Connectivity issues with ec2 slaves
Title: Message Title Toni Van de Voorde edited a comment on JENKINS-59137 Re: Connectivity issues with ec2 slaves Hi [~raihaan], But before I didn't had any cloud-init script ... I had a simple pre-baked AMI, but somehow the JDK got update updated (or removed and reinstalled) through something which I can't explain at this point ...So either the cloud-init script fixed my issue (but that doesn't seem to be the case from what you are writing), or simply the fact that the jenkins master installs the java now on the slaves, fixed the issue ... In any case with simply a pre-baked AMI it started to fail ... 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.201569.1567062958000.5270.1567489740257%40Atlassian.JIRA.
[JIRA] (JENKINS-54326) JUnit fails on remote node after upgrading to 1.26.1
Title: Message Title Toni Van de Voorde commented on JENKINS-54326 Re: JUnit fails on remote node after upgrading to 1.26.1 Andrey Nudko I was able to fix it by removing my pre-installed JDK from my AMI and add ‘sudo yum -y update’ in the “Init script” section in the Jenkins master settings. Thanks 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.194979.1540859482000.4250.1567429380539%40Atlassian.JIRA.
[JIRA] (JENKINS-59137) Connectivity issues with ec2 slaves
Title: Message Title Toni Van de Voorde commented on JENKINS-59137 Re: Connectivity issues with ec2 slaves Hi, I’m coming back to you, as I was able to “fix” the issue. Maybe this is something that this plugin could fix or prevent, or maybe it’s not related at all, but at least should someone encounter the same issue, you know how I was able to find a way around the problem. During my research, I stumbled on issue JENKINS-54326 that describes a problem about builds failing with a stack trace saying that it could not find a jar file (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-3.b13.el7_5.x86_64/jre/lib/resources.jar). This is one of the uses cases I had too when the build didn’t fail during checkout, but just after running tests where it used again JUnit to build reports. I asked if meanwhile somebody figured out a solution, and luckily for me, Andrey Nudko answered very quickly, mentioning something very interesting and which could make a lot of sense, where “a” cloud-init script was sneakily upgrading some JDK in the background after the agent process was launched, messing all things up. This got me thinking, as this would indeed explain why some of my builds passed, some failed in the very beginning and some somewhere in the middle or the end when doing some java executions … And especially without changing anything to my Jenkins configuration (upgrades etc). That said, I have (and still don’t have) no clue about which cloud-init script this is and from where it comes?! Especially because in my case, my AMI was pre-installed with a JDK. But it all made sense, so I did 2 things that completely fixed my problem: 1. Updated my AMI by removing the pre-installed JDK 2. Edited the Jenkins cloud configuration and added ‘sudo yum -y update’ in the “Init script” section. Now when the slave server starts, it performs an upgrade of the currently installed libraries and the master Jenkins installs the corresponding JDK on the slave. Although it’s still not 100% clear to me what was the problem, this did solve it. I’m all ears with a more detailed explanation or if by any luck this plugin can solve (or document) this behavior?! Cheers Add Comment This
[JIRA] (JENKINS-54326) JUnit fails on remote node after upgrading to 1.26.1
Title: Message Title Toni Van de Voorde commented on JENKINS-54326 Re: JUnit fails on remote node after upgrading to 1.26.1 Andrey Nudko The thing is, our ami contains a java installation ... and we never had the issue before. Now I do also have another issue currently going on, so I'm not sure if there are related ... (cf https://issues.jenkins-ci.org/browse/JENKINS-59137?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel) Currently trying something out with your comment and see if it changes anything ... 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.194979.1540859482000.3179.1567164720189%40Atlassian.JIRA.
[JIRA] (JENKINS-54326) JUnit fails on remote node after upgrading to 1.26.1
Title: Message Title Toni Van de Voorde commented on JENKINS-54326 Re: JUnit fails on remote node after upgrading to 1.26.1 Hey guys, I'm also facing this issue (sometimes) ... are you still staying on version 1.24 ? Or the problem fixed itself with latest versions? 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.194979.1540859482000.3130.1567155600310%40Atlassian.JIRA.
[JIRA] (JENKINS-59137) Connectivity issues with ec2 slaves
Title: Message Title
Toni Van de Voorde updated an issue
Jenkins / JENKINS-59137
Connectivity issues with ec2 slaves
Change By:
Toni Van de Voorde
Hi guys,Since yesterday (28/08/19) we are facing a strange issue with our builds on jenkins. Either our builds are failing immediately, either the builds perform all steps but fail at the end. And each time it seems to be related with a connectivity issue with the slaves. I tried to figure out what the issue is but the it's too cryptic :/The funny part is that I don't remember upgrading anything. So I did upgrade to latest version (jenkins and plugin) but the problem persists.Hopefully the following stacktraces tell you more. This is a stacktrace I found in the jenkins log server: {code:java}2019-08-29 06:28:05.986+ [id=257] WARNING o.j.p.w.s.s.ExecutorStepExecution$PlaceholderTask$2#run: failed to shut down 75c2e395-96e2-4e6d-85d4- be32482bfdec2019-08-29 06 be32482bfdecAlso : 28:05.986+ [id=257] WARNING o.j.p.w.s.s.ExecutorStepExecution$PlaceholderTask$2#run: failed to shut down 75c2e395-96e2-4e6d-85d4-be32482bfdecAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to EC2 (jenkins-slave) - Adsdaq Jenkins Slave (i-x) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:955) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:1086) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask$2.run(ExecutorStepExecution.java:738) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) java.lang.NoClassDefFoundError: Could not initialize class hudson.slaves.SlaveComputer at hudson.util.ProcessTree.get(ProcessTree.java:414) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:1103) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:1094) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) Caused: java.io.IOException: Remote call on EC2 (jenkins-slave) - Adsdaq Jenkins Slave (i-x) failed at hudson.remoting.Channel.call(Channel.java:961) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:1086) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask$2.run(ExecutorStepExecution.java:738) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at
[JIRA] (JENKINS-59137) Connectivity issues with ec2 slaves
Title: Message Title Toni Van de Voorde created an issue Jenkins / JENKINS-59137 Connectivity issues with ec2 slaves Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-08-29 07:15 Environment: Jenkins: 2.191 ec2-plugin: 1.44.1 ec2-plugin: 1.45 Priority: Blocker Reporter: Toni Van de Voorde Hi guys, Since yesterday (28/08/19) we are facing a strange issue with our builds on jenkins. Either our builds are failing immediately, either the builds perform all steps but fail at the end. And each time it seems to be related with a connectivity issue with the slaves. I tried to figure out what the issue is but the it's too cryptic :/ The funny part is that I don't remember upgrading anything. So I did upgrade to latest version (jenkins and plugin) but the problem persists. Hopefully the following stacktraces tell you more. This is a stacktrace I found in the jenkins log server: 2019-08-29 06:28:05.986+ [id=257] WARNING o.j.p.w.s.s.ExecutorStepExecution$PlaceholderTask$2#run: failed to shut down 75c2e395-96e2-4e6d-85d4-be32482bfdec2019-08-29 06:28:05.986+ [id=257] WARNING o.j.p.w.s.s.ExecutorStepExecution$PlaceholderTask$2#run: failed to shut down 75c2e395-96e2-4e6d-85d4-be32482bfdecAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to EC2 (jenkins-slave) - Adsdaq Jenkins Slave (i-x) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:955) at
[JIRA] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Toni Van de Voorde commented on JENKINS-26493 Re: Use new EC2 API endpoint hostnames Got the same issue Any idea if this is going to be fixed soon? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-11983) Allow users to manually define job relationships to (in my case) prevent concurrent builds
Toni Van de Voorde resolved JENKINS-11983 as Not A Defect Allow users to manually define job relationships to (in my case) prevent concurrent builds Actually I discovered the Throttle plugin some time ago, but completely forgot that I posted an issue here. So I confirm that it works with that plugin. Change By: Toni Van de Voorde (04/May/13 4:21 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
