[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Shaun Keenan commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors thank you! 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-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Shaun Keenan commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors Another ping - when will this make it into LTS? 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-38906) Remove lock resource name from global configuration when lock is released
Title: Message Title Shaun Keenan commented on JENKINS-38906 Re: Remove lock resource name from global configuration when lock is released Bump - curious if anything can be done about this. Not having the ability to clean up locks that are auto-created seems like more than a "minor" priority... this could quickly balloon out of control. Thanks a lot for the cleanup suggestion Mikko P 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-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Shaun Keenan updated an issue Jenkins / JENKINS-33412 Jenkins locks when started in HTTPS mode on a host with 37+ processors Change By: Shaun Keenan Attachment: lwps.txt 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-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Shaun Keenan commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors I see 1 parent with 112 LWPs. Attached lwps.txt 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-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Shaun Keenan commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors Would love to know when we can expect to see this change in LTS - until this is in, I'll be stuck on 2.107.3, which has quite a few vulnerabilities we'd like to mitigate. The nodes this runs on are 72-core amd64 kubernetes nodes. FWIW, here's an example node: Capacity: cpu: 72 memory: 528332604Ki pods: 110 System Info: Machine ID: 833e0926ee21aed71ec075d726cbcfe0 System UUID: ----0CC47AC64A64 Boot ID: 786d3795-f026-4556-9047-923f95a9a331 Kernel Version: 4.14.44-coreos-r1 OS Image: Container Linux by CoreOS 1745.5.0 (Rhyolite) Operating System: linux Architecture: amd64 Container Runtime Version: docker://18.3.1 Kubelet Version: v1.8.10+coreos.0 Kube-Proxy Version: v1.8.10+coreos.0 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-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title
Shaun Keenan edited a comment on JENKINS-33412
Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors
I just tested this on a 72-core k8s node and it worked perfectly. Published a docker image built off of this at ` {code:java} skeenan947/jenkinstest ` {code}
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-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Shaun Keenan commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors I just tested this on a 72-core k8s node and it worked perfectly. Published a docker image built off of this at `skeenan947/jenkinstest` 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-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Shaun Keenan edited a comment on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors I'm seeing this happen again on the latest Jenkins (well, every LTS above 2.107.3, as well as latest), which are running winstone 4The issue that I'm seeing is that Jenkins fails to completely initialize the * HTTP * listener (HTTPS isn't enabled - k8s ingress takes care of HTTPS, so no need) whenever it's running on a host with >36 CPU's. If I run Jenkins on a host with 36 or fewer CPU's, it starts up just fine. I took the same kubernetes pod (tried with both latest LTS and latest non-LTS), pinned it to a 72-CPU node and it initialized, said everything was good, but never responded to HTTP requests, re-pinned it to a 20-CPU node, and it started correctly.Nothing in the logs indicates that there's an issue at all. The same thing happens both with a completely fresh jenkins_home and one that has been in use for years and has a bunch of plugins installed.For me, rolling back to 2.107.3 makes everything work again. Moving to any newer LTS version breaks everything.This is a rather frustrating issue. I need to update to pick up a bunch of vulnerability fixes. At least I can pin to nodes with fewer CPU's, but this isn't exactly the best workaround. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Shaun Keenan commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors I'm seeing this happen again on the latest Jenkins (well, every LTS above 2.107.3, as well as latest), which are running winstone 4 The issue that I'm seeing is that Jenkins fails to completely initialize the HTTP listener whenever it's running on a host with >36 CPU's. If I run Jenkins on a host with 36 or fewer CPU's, it starts up just fine. I took the same kubernetes pod (tried with both latest LTS and latest non-LTS), pinned it to a 72-CPU node and it initialized, said everything was good, but never responded to HTTP requests, re-pinned it to a 20-CPU node, and it started correctly. Nothing in the logs indicates that there's an issue at all. The same thing happens both with a completely fresh jenkins_home and one that has been in use for years and has a bunch of plugins installed. For me, rolling back to 2.107.3 makes everything work again. Moving to any newer LTS version breaks everything. This is a rather frustrating issue. I need to update to pick up a bunch of vulnerability fixes. At least I can pin to nodes with fewer CPU's, but this isn't exactly the best workaround. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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.
