Hi, > > Have you been experiencing increasingly frequent 502/503 errors in > > past weeks when using salsa.debian.org? > > I'd at least separate the errors that you saw before > https://salsa.debian.org/dsa-team/mirror/dsa-puppet/-/commit/5e924edc1795a0f446a42427b2913910d4ae5bc0 > (i.e. before Sep 3) and those after. Even though that affected > healthchecks most severely, it also broke some regular request > forwarding when there were too many parallel requests. > > I also think distinguishing between proxy level and Salsa-issued errors > would be good, so that the right people can look at the corresponding > issues they are responsible for. E.g. Enrico provided .har files that > were super helpful.
Since I'm not part of DSA or Salsa Admins and have never seen an architecture diagram of the setup, it's difficult for me to report anything beyond what the outermost public HTTP layer shows me. I have now attached the HARs to !597 as you requested. Follow-up debug discussion should probably also be in the issue. On debian-devel@ I mainly wanted to raise awareness for this, as it seems many people are suffering from it. One DD even told me yesterday they are considering moving their packages to Codeberg or GitHub due to frequent issues in simply opening Salsa pages. I also noticed that none of the Salsa Admins have replied anything in the issues https://salsa.debian.org/salsa/support/-/work_items/597 and https://salsa.debian.org/salsa/support/-/work_items/598 in past two months. I wonder if they are totally overworked, would it help if we try to get more people to join that team? What is the onboarding path?
