error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
Hi, I am using Sameersbn/gitlab 14.1.1, we are seeing the error "error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500" very frequently when developers are trying to fetch the repos from IDEs(Intellij) or local CMDs.
Here is my configuration
System information System: Current User: git Using RVM: no Ruby Version: 2.7.2p137 Gem Version: 3.1.4 Bundler Version:2.1.4 Rake Version: 13.0.3 Redis Version: 5.0.7 Git Version: 2.32.0 Sidekiq Version:5.2.9 Go Version: unknown
GitLab information Version: 14.1.1 Revision: c8edb9de30c Directory: /home/git/gitlab DB Adapter: PostgreSQL DB Version: 12.3 URL: http://xxxxxxxxxx HTTP Clone URL: http://xxxxxxxxxx SSH Clone URL: ssh://git@xxxxxxxxxxxxxxx Using LDAP: yes Using Omniauth: no
GitLab Shell Version: 13.19.0 Repository storage paths:
- default: /home/git/data/repositories GitLab Shell path: /home/git/gitlab-shell Git: /usr/bin/git
Have you tried upgrading redis to 6.2 ? I have similar issues with 5XX errors and this seems to do the trick
Thank you for your response, but I don’t see Sameersbn/redis 6.2 image.
From: bascouba @.> Sent: Friday, October 8, 2021 8:22 AM To: sameersbn/docker-gitlab @.> Cc: Vutkuri, Rammohan @.>; Author @.> Subject: Re: [sameersbn/docker-gitlab] error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 (#2418)
This message was sent from an external source outside of Western & Southern's network. Do not click links or open attachments unless you recognize the sender and know the contents are safe.
Have you tried upgrading redis to 6.2 ? I have similar issues with 5XX errors and this seems to do the trick
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/sameersbn/docker-gitlab/issues/2418#issuecomment-938599030, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AP2DHJBH4AELZMK7OHGEEIDUF3O6DANCNFSM5FAQVREQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
On the docker-compose example file, it uses the default redis docker image : redis:6.2
Hi, I have upgraded to 6.2, but still getting the same error, and also seeing the following error while logging using a browser
Here are the containers running sameersbn/gitlab:14.2.5 redis:6.2 sameersbn/postgresql:12-20200524
Error1 fatal: unable to access 'xxxxxxxxxxx/': The requested URL returned error: 500 error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 fatal: expected flush after ref listing
Error2:when I click on Metrics and profiling, I am getting http 500 error
@.***
Environment: @.***
From: bascouba @.> Sent: Friday, October 8, 2021 10:22 AM To: sameersbn/docker-gitlab @.> Cc: Vutkuri, Rammohan @.>; Author @.> Subject: Re: [sameersbn/docker-gitlab] error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 (#2418)
This message was sent from an external source outside of Western & Southern's network. Do not click links or open attachments unless you recognize the sender and know the contents are safe.
On the docker-compose example file, it uses the default redis docker image : redis:6.2
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/sameersbn/docker-gitlab/issues/2418#issuecomment-938683329, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AP2DHJHSRSIVJE23PSCRK3DUF35AJANCNFSM5FAQVREQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
The metrics page issue is linked to #2387
The issue with error 500 can be so many things.. Like a problem between a proxy configuration (size limitations on nginx for example) and your server. Or it can be something between your services (just like I had with my old redis version). Try to look after your proxy logs if you don't find anything in the git logs
Thank you for the quick response, here is the error found Production.log, any suggestion?
Completed 500 Internal Server Error in 5107ms (ActiveRecord: 4.3ms | Elasticsearch: 0.0ms | Allocations: 5724)
Net::LDAP::Error (Connection timed out - user specified timeout):
lib/gitlab/auth/ldap/authentication.rb:29:in login' lib/gitlab/auth.rb:108:in block (2 levels) in find_with_user_password'
lib/gitlab/auth.rb:107:in each' lib/gitlab/auth.rb:107:in find'
lib/gitlab/auth.rb:107:in block in find_with_user_password' lib/gitlab/auth/unique_ips_limiter.rb:19:in limit_user!'
lib/gitlab/auth.rb:84:in find_with_user_password' lib/gitlab/auth.rb:172:in user_with_password_for_git'
lib/gitlab/auth.rb:55:in find_for_git_client' app/controllers/repositories/git_http_client_controller.rb:118:in handle_basic_authentication'
app/controllers/repositories/git_http_client_controller.rb:41:in authenticate_user' lib/gitlab/middleware/speedscope.rb:13:in call'
lib/gitlab/request_profiler/middleware.rb:17:in call' lib/gitlab/jira/middleware.rb:19:in call'
lib/gitlab/middleware/go.rb:20:in call' lib/gitlab/etag_caching/middleware.rb:21:in call'
lib/gitlab/middleware/multipart.rb:172:in call' lib/gitlab/middleware/read_only/controller.rb:50:in call'
lib/gitlab/middleware/read_only.rb:18:in call' lib/gitlab/middleware/same_site_cookies.rb:27:in call'
lib/gitlab/middleware/handle_malformed_strings.rb:21:in call' lib/gitlab/middleware/basic_health_check.rb:25:in call'
lib/gitlab/middleware/handle_ip_spoof_attack_error.rb:25:in call' lib/gitlab/middleware/request_context.rb:21:in call'
config/initializers/fix_local_cache_middleware.rb:11:in call' lib/gitlab/middleware/rack_multipart_tempfile_factory.rb:19:in call'
lib/gitlab/metrics/requests_rack_middleware.rb:74:in call' lib/gitlab/middleware/release_env.rb:12:in call'
Started GET "/zeus/lead-management.git/info/refs?service=git-upload-pack" for 10.
From: bascouba @.> Sent: Tuesday, October 26, 2021 11:06 AM To: sameersbn/docker-gitlab @.> Cc: Vutkuri, Rammohan @.>; Author @.> Subject: Re: [sameersbn/docker-gitlab] error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 (#2418)
This message was sent from an external source outside of Western & Southern's network. Do not click links or open attachments unless you recognize the sender and know the contents are safe.
The metrics page issue is linked to #2387https://github.com/sameersbn/docker-gitlab/issues/2387
The issue with error 500 can be so many things.. Like a problem between a proxy configuration (size limitations on nginx for example) and your server. Or it can be something between your services (just like I had with my old redis version). Try to look after your proxy logs if you don't find anything in the git logs
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/sameersbn/docker-gitlab/issues/2418#issuecomment-952034217, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AP2DHJBWVQGOX6C7RTSBSDTUI3GXDANCNFSM5FAQVREQ. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.