Geo: SocketError (getaddrinfo: Name or service not known) when updating Wiki paths
This is only relevant to pre-GitLab 10.0, since we've removed system hooks, but a customer had Geo enabled and saw Redis connection failures whenever pushing to a Wiki page:
Completed 500 Internal Server Error in 439ms (ActiveRecord: 26.3ms | Elasticsearch: 0.0ms)
SocketError (getaddrinfo: Name or service not known):
lib/gitlab/geo/update_queue.rb:12:in `store'
app/services/geo/enqueue_wiki_update_service.rb:11:in `execute'
lib/gitlab/geo.rb:70:in `notify_wiki_update'
app/services/ee/wiki_pages/base_service.rb:23:in `process_wiki_repository_update'
app/services/ee/wiki_pages/base_service.rb:14:in `execute_hooks'
app/services/wiki_pages/update_service.rb:5:in `execute'
app/controllers/projects/wikis_controller.rb:48:in `update'
lib/gitlab/i18n.rb:39:in `with_locale'
lib/gitlab/i18n.rb:45:in `with_user_locale'
app/controllers/application_controller.rb:307:in `set_locale'
lib/gitlab/performance_bar/peek_performance_bar_with_rack_body.rb:16:in `call'
lib/gitlab/middleware/multipart.rb:93:in `call'
lib/gitlab/request_profiler/middleware.rb:14:in `call'
lib/gitlab/database/load_balancing/rack_middleware.rb:37:in `call'
lib/gitlab/middleware/go.rb:16:in `call'
lib/gitlab/etag_caching/middleware.rb:11:in `call'
lib/gitlab/middleware/readonly_geo.rb:30:in `call'
lib/gitlab/request_context.rb:18:in `call' The Redis instance had the URL: redis://:<password>@gitlab-redis/
With object storage, we have seen weird issues where Ruby wasn't able to resolve domains: https://sentry.gitlap.com/gitlab/gitlabcom/issues/44918/ Could this be related?
Edited by Stan Hu