Gitlab.com throwing 500 errors

General
1

Since a couple of minutes ago, trying to visit this URL results in a 500 error.

https://gitlab.com/exosphere/exosphere/-/merge_requests?scope=all&state=merged&author_username=cmart&search=orchestration

image
image899×624 61.6 KB

I don’t see anything pertinent from the status page.

2

It seems to only happen with a search term (search= query parameter populated), and not all search terms cause the issue! A search for “jetstream2” returns results, while a search for “orchestration” reliably 500s.

3

I just did a search for “orchestration” and it works.

Screenshot from 2024-09-04 07-59-02
Screenshot from 2024-09-04 07-59-021632×936 42.5 KB

as you can see the url pretty much matches what you have searched for with the exception that I do not search for a specific user/author.

4

It seems to be just for my account! I can reproduce it 100% of the time, but a colleague cannot reproduce it at all with the exact same search query.

Digging a little deeper,

  • Changing the search term:
    • Changing from “orchestration” to “orchestra” still returns a 500.
    • Changing to “orch” works, returns 6 results.
    • Adding letters back into the search term, “orches” works but “orchest” returns a 500.
      • Hypothesis: 6-letter search terms work, but 7-letter terms break?
      • The answer is “not always”! The search term “guacamole” (9 letters) works, returning 16 results. (It’s the name of a technology in our project.)
  • Removing author_username=cmart& from the original query string works, returns 9 results.
  • Removing scope=all&state=merged& from the original query string works, returns 0 results for “open”. The other tabs appear to have results:
    • image
    • “Merged” tab returns a 500
    • “Closed” tab works
    • “All” tab returns a 500

Another hypothesis is the existence of a “poison” merge request in this repository (that breaks the back-end when it would appear in search results), but I reject this hypothesis, because a search for “orch” successfully returns what I’d expect are the same 6 search results for “orchestration”.

I give up for now. If there’s a 500 error, maybe there’s a traceback that I cannot see, but surely GitLab staff can. :slightly_smiling_face:

5

After spelunking the bug reports, this seems somewhat similar to these two issues:

6

You definitely got a weird one there :slight_smile: but glad to see you added a comment on the issue as that should help get it resolved.

1 Like
7

@cmart, I found your error in our logs based on the Request ID of the screenshot. For future reference, try to include this as a text that we can copy/paste - typing that wasn’t fun :sweat_smile:

I can confirm that this is not happening to other users, so you might be hitting a corner case somewhere. The error is a DB timeout, and I see that it’s happened 19 times for you and it stopped after 5/Sep.

If this starts to happen again, please create a new bug issue in gitlab-org/gitlab, and include the Request ID. Someone in the team will triage it.

1 Like