502 proxy error on ci.jenkins.io

225 views
Skip to first unread message

pallen

unread,
Oct 2, 2019, 4:37:17 AM10/2/19
to Jenkins Developers
Hi Guys,

I'm getting a 502 proxy error on ci.jenkins.io?  Is it just me or is there an outage?

Kind regards,
Paul

Olblak

unread,
Oct 2, 2019, 5:24:29 AM10/2/19
to 'Gavin Mogan' via Jenkins Developers
As you can see on this status page, there is definitely something wrong, I start looking at it

---
-> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
---


--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

Paul Allen

unread,
Oct 2, 2019, 10:14:14 AM10/2/19
to Jenkins Developers
Thanks - It seems to be working now.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/bd355020-3a8e-45ec-a2cc-4eb0f87e68c8%40www.fastmail.com.

This e-mail may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.

Perforce Software UK Ltd is registered in England and Wales as company no.
3816019 at the following address: West Forest Gate,
Wellington Road, Wokingham,
RG40 2AT, UK

Tim Jacomb

unread,
Oct 3, 2019, 3:37:24 PM10/3/19
to Jenkins Developers

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5475CAA0-A0A1-4619-9983-3F49D763D1B0%40perforce.com.

Chris Kilding

unread,
Oct 24, 2019, 9:14:12 AM10/24/19
to jenkin...@googlegroups.com
It happened again this morning.

The recent 502 errors seemed to coincide with builds of certain Jenkins Core components, which have a large number of (parallel) steps.

Just an initial idea - is the master being overwhelmed by either the sheer number of steps as they enter the job queue, or the parallelism of those steps when they execute (they seem to take over almost every executor)?

Chris

Jesse Glick

unread,
Oct 24, 2019, 12:03:13 PM10/24/19
to Jenkins Dev
On Thu, Oct 24, 2019 at 9:14 AM Chris Kilding
<chris+...@chriskilding.com> wrote:
> is the master being overwhelmed by either the sheer number of steps as they enter the job queue, or the parallelism of those steps when they execute

Quite possibly. The server sets a cap on the number of active elastic
agents, which is fine, but pushing up against that limit seems to
actually cause things to explode, rather than tasks simply waiting
politely in the queue. No one with sufficient access has (to my
knowledge) yet tried to track down whether the problem is in Jenkins
core, Pipeline, the Azure agent plugin we use, or something else.

https://github.com/jenkinsci/bom/blob/f384f08edeb3da9a2ba2c5b83be3fee4b5e0c628/Jenkinsfile#L40-L43
Reply all
Reply to author
Forward
0 new messages