Re: [gentoo-user] 502 Bad Gateway when accessing gitweb.gentoo.org
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 :-) :-)
Re: [gentoo-user] New install - Wayland and graphical login
On 26/06/2021 13:00, Michael wrote: On Saturday, 26 June 2021 11:50:01 BST antlists wrote: I just want a working systemd/wayland desktop system. So basically, a full-weight normal desktop. [snip ...] I've got this one selected, /desktop/plasma/systemd Select default/linux/amd64/17.1/desktop/plasma/systemd (stable). Then update @world. You should be good to go as long as video drivers and firmware are in place, but if X11 is not working this could be an area meriting further investigation. Okay, ... One new kernel later (along with some grub debugging :-), world updated, ... X11 still isn't working - first it complained it couldn't find twm, so I emerged that, now startx just runs and exits, and the log doesn't seem to show anything wrong ... Wayland is interesting ... if I try to startplasma-wayland, it comes up with the starting plasma stuff, and there's a mouse cursor, but nothing except a black screen and the cursor. When I kill it from a root tty, there's an error Failed to create wl_display (No such file or directory) which a google tells me I haven't got a compositor ... I also get further errors, but they're probably a consequence - Could not load the Qt platform plugin "Wayland" in "" even though it was found and the same error for xcb. Cheers, Wol
