public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Hayley <spam@foxes.systems>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] 502 Bad Gateway when accessing gitweb.gentoo.org
Date: Tue, 29 Jun 2021 14:44:08 +1000	[thread overview]
Message-ID: <ab2b44c28028eb3ec4639510d06350bc952cb521.camel@foxes.systems> (raw)
In-Reply-To: <2adbadb8-fe58-3611-422c-0ce9abc59b14@gmail.com>

Just saw the post on gentoo-dev. It'll be interesting to see the
postmortem as not being able to update the infra status page during an
outage is a bit of a problem ;)

Thanks for the reply

Hayley

On Mon, 2021-06-28 at 23:37 -0500, Dale wrote:
> Hayley wrote:
> > Hey all,
> > Since yesterday I've getting 502 Bad Gateway when trying to access
> > gitweb.gentoo.org and was wondering if anyone else is having the
> > same
> > issue?
> > The gentoo infra status page says that it should be up so I'm not
> > sure
> > what could be causing the problem but it's a 502 so I'm guessing it
> > must be a server side issue?
> > 
> > Thanks,
> > Hayley
> > 
> > 
> > 
> 
> 
> I just read a message on -project I think that was about some upgrade
> problems and some parts of infra not working correctly.  That could
> be
> the problem you were seeing.  I think fixing the problem is still in
> progress so may be a few days before everything is back up to 100%. 
> This is the message:
> 
> > Alec Warner wrote:
> > > Hi,
> > > 
> > > Many of you reported that various infra-owned services were not
> > > functioning properly these past two days. We had some package
> > > upgrades roll out that were bad, and a subset of services were
> > > non-functional while we worked through the incident.
> > > 
> > > (a) The upgrades did not appear to cause any data loss, but
> > > service
> > > availability was reduced (500s / 502s for some HTTP services.)
> > > (b) Some hosts may have had problems running some commands. E.g.
> > > I
> > > know that 'grep' didn't work for a while. If you observed errors
> > > related to missing 'GLIBC_2.33' symbols then this was likely
> > > related.
> > > (c) Many replicated services (including infra-status) rely on
> > > gitweb
> > > to take updates from git; and gitweb was not up, so they were
> > > unable
> > > to receive updates.
> > > (d) More impacted notes will follow in a postmortem that will
> > > come
> > > later this week for this incident.
> > > 
> > > Thanks to all of you who reported problems and apologies for the
> > > service disruptions.
> > > 
> > > -A
> 
> 
> Hope that helps.  Should keep you from looking for the problem on
> your
> end at least. 
> 
> Dale
> 
> :-)  :-) 
> 




      reply	other threads:[~2021-06-29  4:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29  2:48 [gentoo-user] 502 Bad Gateway when accessing gitweb.gentoo.org Hayley
2021-06-29  4:37 ` Dale
2021-06-29  4:44   ` Hayley [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ab2b44c28028eb3ec4639510d06350bc952cb521.camel@foxes.systems \
    --to=spam@foxes.systems \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox