GitlabServicePingWorker throws 500 after changed from CE to EE for feature program
After I migrated to the EE version for the feature program, I've started to recieve a 500 in Sidekiq for the Service Ping.
I've tried to manually trigger it via gitlab-rails console
:
irb(main):010:0> GitlabServicePingWorker.new.perform('triggered_from_cron' => false)
/opt/gitlab/embedded/service/gitlab-rails/app/services/service_ping/submit_service.rb:26:in `execute': Unsuccessful response code: 500 (ServicePing::SubmitService::SubmissionError)
from /opt/gitlab/embedded/service/gitlab-rails/app/workers/gitlab_service_ping_worker.rb:35:in `block in perform'
from /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/exclusive_lease_helpers.rb:43:in `block in in_lock'
from /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/exclusive_lease_helpers.rb:53:in `with_instrumentation'
from /opt/gitlab/embedded/service/gitlab-rails/lib/gitlab/exclusive_lease_helpers.rb:42:in `in_lock'
from /opt/gitlab/embedded/service/gitlab-rails/app/workers/gitlab_service_ping_worker.rb:31:in `perform'
from (irb):10:in `<main>'
from /opt/gitlab/embedded/lib/ruby/gems/3.1.0/gems/railties-7.0.8.1/lib/rails/commands/console/console_command.rb:74:in `start'
from /opt/gitlab/embedded/lib/ruby/gems/3.1.0/gems/railties-7.0.8.1/lib/rails/commands/console/console_command.rb:19:in `start'
from /opt/gitlab/embedded/lib/ruby/gems/3.1.0/gems/railties-7.0.8.1/lib/rails/commands/console/console_command.rb:106:in `perform'
from /opt/gitlab/embedded/lib/ruby/gems/3.1.0/gems/thor-1.3.1/lib/thor/command.rb:28:in `run'
from /opt/gitlab/embedded/lib/ruby/gems/3.1.0/gems/thor-1.3.1/lib/thor/invocation.rb:127:in `invoke_command'
from /opt/gitlab/embedded/lib/ruby/gems/3.1.0/gems/thor-1.3.1/lib/thor.rb:527:in `dispatch'
from /opt/gitlab/embedded/lib/ruby/gems/3.1.0/gems/railties-7.0.8.1/lib/rails/command/base.rb:87:in `perform'
from /opt/gitlab/embedded/lib/ruby/gems/3.1.0/gems/railties-7.0.8.1/lib/rails/command.rb:48:in `invoke'
from /opt/gitlab/embedded/lib/ruby/gems/3.1.0/gems/railties-7.0.8.1/lib/rails/commands.rb:18:in `<top (required)>'
from <internal:/opt/gitlab/embedded/lib/ruby/site_ruby/3.1.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
... 2 levels...
I've not seen this before, and the internet does not really show someone else having the same problem. Only some similarities:
But none of these talks about error 500.
I'm a bit at loss how to go about to debug this. Is something blocking traffic out to GitLab.com for submitting, is there some bugs in the code, any wrong configuration on my part.
Tried following https://docs.gitlab.com/ee/development/internal_analytics/service_ping/troubleshooting.html to see if it could help me somehow.
Edited by Birger J. Nordølum