500 Error - Unable to log in

How to Use GitLab Self-managed
1

Upgraded to 16.1 a couple days ago and our CE install was working fine. When the team went to log in today they started getting 500 errors. Running sudo gitlab-rake gitlab:check --trace I see the following:

Gitaly: … default … FAIL: 14:connections to all backends failing. debug_error_string:{“created”:“@1687971742.156911789”,“description”:“Failed to pick subchannel”,“file”:“src/core/ext/filters/client_channel/client_channel.cc”,“file_line”:3093,“referenced_errors”:[{“created”:“@1687971742.156910734”,“description”:“connections to all backends failing”,“file”:“src/core/lib/transport/error_utils.cc”,“file_line”:163,“grpc_status”:14}]}

2

Hello rcoyle23 :wave:,

It seems like you’re encountering a 500 error after upgrading to GitLab 16.1. The error message indicates that there’s an issue with the Gitaly service, which is crucial for Git repository access. The error Failed to pick subchannel and connections to all backends failing suggest that the Gitaly service is unable to establish a connection.

Here are a few steps you can take to troubleshoot this issue:

  1. Check Gitaly’s status: Run the command gitlab-ctl status gitaly to check if Gitaly is running. If it’s not, try starting it with gitlab-ctl start gitaly.
  2. Inspect Gitaly’s logs: The logs can provide more detailed information about the error. You can find them at /var/log/gitlab/gitaly/current.
  3. Check Gitaly’s configuration: Ensure that the Gitaly configuration in /etc/gitlab/gitlab.rb is correct. You can refer to the Gitaly configuration documentation for more details.
  4. Reconfigure GitLab: After checking and potentially modifying the configuration, run gitlab-ctl reconfigure to apply the changes.
  5. Restart GitLab: If the issue persists, try restarting GitLab with gitlab-ctl restart.

I hope this helps! Let us know how it goes. :blush: