Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    alok0310
    @alok0310
    Why there? Any specific reason?
    Alex Earl
    @slide
    It's what is in the default sshd_config
    also, you need to make sure permissions are correct on the file
    alok0310
    @alok0310
    @slide Can you be kind enough to please let me know your results once it works for you...I will keep trying myself as well
    Alex Earl
    @slide
    @alok0310 sure, I'll let you know if I find anything out
    LutherJolliff
    @LutherJolliff
    Hi all! Running the EC2 plugin in Govcloud in us-gov-east-1 region. After inputting IAM creds and alternate EC2 endpoint the region selection stalls and spits out The proxy server received an invalid response from an upstream server. Is there maybe some network configuration that is also needed?
    Ken Rachynski
    @kenrachynski
    @LutherJolliff that's an open issue, apparently: https://issues.jenkins-ci.org/browse/JENKINS-29983
    LutherJolliff
    @LutherJolliff
    Thanks for the find @kenrachynski
    Alex Earl
    @slide
    @alok0310 I got the windows agents working over ssh, did you ever get things working?
    bencovi
    @bencovi
    hi there. can I get an idea when the next ec2-plugin release will be? I think I need this fix, and there hasn't been a new release since January: jenkinsci/ec2-plugin#431
    bluwavesd
    @bluwavesd
    hi, can someone provide some insight on how the plug-in determines idle timeout for the agent? we have instances where jenkins is pulling the rug out from under the build
    alok0310
    @alok0310
    @slide Yes, I was able to make it work...Thanks for all the help and direction :-)
    alok0310
    @alok0310
    @alok0310
    Hey...does anyone here know why some of the EC2 agents keep losing connection saying timeout exception in the log...these slaves run jobs that typically run for 1h
    When I go to these agents under the nodes section and click on the launch agent button ...it gets connected again and the job which was running on it continues further
    Have you faced a similar issue..Please note that I am using SSH mechanism for connection to Windows machines
    Alex Earl
    @slide
    We see something similar on ci.j.io
    alok0310
    @alok0310
    @slide you are right...Thanks for pointing out...Do you have any idea on how to fix it?
    Alex Earl
    @slide
    I do not...we've been wondering that too
    Kalby Imanie
    @kalbyimanie
    Hi
    i have been trying to connect to my ec2 windows agent from my jenkins, the agent has successfully spawned but the log kept saying "Waiting for WinRM to come up. Sleeping 10s."
    i have configured :
    1. jenkins ec2-plugin
    2. open port for winRM
    is there anything that i missed during windows agent configuration ?
    Alex Earl
    @slide
    I ended up switching to SSH for my agents on ec2
    for Windows even
    Kalby Imanie
    @kalbyimanie
    why is that ?
    is it that hard to make it work ?
    Alex Earl
    @slide
    I just found that the WinRM stuff wasn't as stable
    I setup my AMI using packer and installed the OpenSSH-Win32 port and the hostkey into the image. Then you switch the AMI type to Linux in the cloud configuration
    Fabrizio Manfredi Furuholmen
    @thoulen
    @alok0310 that sometime happen when the jenkins queue stuck, do you have also job that are reported completed in the job page and are still running in the left bar ?
    alok0310
    @alok0310
    @thoulen No, I don't think so.
    James Brown
    @Roguelazer
    I just upgraded to 1.50 and Jenkins somehow was no longer able to see the labels on my builders (every job was stuck waiting for a builder to appear with the right label). Downgrading to 1.49.1 fixed it immediately. Anyone seen anything like that?
    Attempting to terminate an instance also crashed with a NPE
    (all on Jenkins LTS)
    Raihaan Shouhell
    @res0nance
    @Roguelazer I have not seen this. Do you have a stacktrace or some way to replicate this?
    tburow
    @tburow
    Im seeing the same behavior with 1.50 - downgraded to fix. could not interact with executors - could not schedule jobs - could not delete executors - could not allocate new executors - got the “oops” window everytime.
    Here is the stack trace
    java.lang.NullPointerException at hudson.plugins.ec2.util.MinimumInstanceChecker.lambda$countQueueItemsForAgentTemplate$8(MinimumInstanceChecker.java:67) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.LongPipeline.reduce(LongPipeline.java:461) at java.util.stream.LongPipeline.sum(LongPipeline.java:419) at java.util.stream.ReferencePipeline.count(ReferencePipeline.java:593) at hudson.plugins.ec2.util.MinimumInstanceChecker.countQueueItemsForAgentTemplate(MinimumInstanceChecker.java:68) at hudson.plugins.ec2.util.MinimumInstanceChecker.lambda$null$11(MinimumInstanceChecker.java:87) at java.util.ArrayList.forEach(ArrayList.java:1257) at java.util.Collections$UnmodifiableCollection.forEach(Collections.java:1082) at hudson.plugins.ec2.util.MinimumInstanceChecker.lambda$checkForMinimumInstances$12(MinimumInstanceChecker.java:76) at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) at java.util.Iterator.forEachRemaining(Iterator.java:116) at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150) at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:485) at hudson.plugins.ec2.util.MinimumInstanceChecker.checkForMinimumInstances(MinimumInstanceChecker.java:75) at hudson.plugins.ec2.SlaveTemplate$OnSaveListener.onChange(SlaveTemplate.java:1410) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:81) at jenkins.model.Jenkins.save(Jenkins.java:3385) at jenkins.model.Jenkins.<init>(Jenkins.java:985) at hudson.model.Hudson.<init>(Hudson.java:85) at hudson.model.Hudson.<init>(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:262)
    looks like MinimumInstanceChecker.java is the problem child
    Raihaan Shouhell
    @res0nance
    @tburow Your large stacktrace should be fixed in 1.50 but there is the other bug which has an open PR we are just waiting for more reviews
    James Brown
    @Roguelazer
    https://gist.github.com/Roguelazer/e81719d2a1d5f0799edbf01f57d145ab is what happens if I try to terminate an instance on 1.50
    I can't get a traceback for no labels matching, but it does recur if I roll forward
    I have every EC2 slave assigned a label and I have a job that uses a label filter to only run on those instances, but it just says "waiting for builder" if I am on 1.50
    ^ @res0nance
    Raihaan Shouhell
    @res0nance
    1.50.1 has been released
    Philip Hyunsu Cho
    @hcho3
    When I upgraded to 1.50 today, I got error "Network interfaces and an instance-level security groups may not be specified on the same request" when my server attempted to launch new EC2 workers. I worked around the problem by downgrading to 1.49.1. So the same configuration worked for 1.49.1 but didn't for 1.50. How should I change my configuration? Any guess what's going on? Ps. Thanks for the great plugin!
    Fabrizio Manfredi Furuholmen
    @thoulen
    can you send you configuration ?
    we aer aslo releaseing 1.50.1 , 1.50 has some heavy bugs
    Philip Hyunsu Cho
    @hcho3
    Should I take the screenshot of the configuration page?
    Fabrizio Manfredi Furuholmen
    @thoulen
    yes it is fine , please open a ticket an attach to it
    Philip Hyunsu Cho
    @hcho3
    Where is the issue tracker? Is it the same as the main Jenkins project?
    Fabrizio Manfredi Furuholmen
    @thoulen
    yes it is the same , you have to specify the plugin in the component field