访问Gitlab中的runners页面时显示500问题

阳光穿透心脏的1/2处 2023-07-18 11:25 5阅读 0赞

1、使用管理员登录访问 /admin/runners页面时报500

2、错误信息

Started GET "/admin/runners" for 127.0.0.1 at 2019-01-31 09:57:47 +0800
    Processing by Admin::RunnersController#index as HTML
    Completed 500 Internal Server Error in 45ms (ActiveRecord: 3.1ms | Elasticsearch: 0.0ms)
    
    ActionView::Template::Error ():
        37:
        38:     .col-sm-6
        39:       .bs-callout
        40:         = render partial: 'ci/runner/how_to_setup_runner',
        41:                  locals: { registration_token: Gitlab::CurrentSettings.runners_registration_token,
        42:                            type: 'shared',
        43:                            reset_token_url: reset_registration_token_admin_application_settings_path }
    
    lib/gitlab/crypto_helper.rb:27:in `aes256_gcm_decrypt'
    app/models/concerns/token_authenticatable_strategies/encrypted.rb:55:in `get_token'
    app/models/concerns/token_authenticatable_strategies/base.rb:33:in `ensure_token!'
    app/models/concerns/token_authenticatable.rb:43:in `block in add_authentication_token_field'
    app/models/application_setting.rb:410:in `runners_registration_token'
    lib/gitlab/current_settings.rb:15:in `method_missing'
    app/views/admin/runners/index.html.haml:40:in `_app_views_admin_runners_index_html_haml___2821790391908612173_70331852238140'
    app/controllers/application_controller.rb:113:in `render'
    lib/gitlab/i18n.rb:55:in `with_locale'
    lib/gitlab/i18n.rb:61:in `with_user_locale'
    app/controllers/application_controller.rb:417:in `set_locale'
    lib/gitlab/middleware/rails_queue_duration.rb:24:in `call'
    lib/gitlab/metrics/rack_middleware.rb:17:in `block in call'
    lib/gitlab/metrics/transaction.rb:55:in `run'
    lib/gitlab/metrics/rack_middleware.rb:17:in `call'
    lib/gitlab/middleware/multipart.rb:103:in `call'
    lib/gitlab/request_profiler/middleware.rb:16:in `call'
    ee/lib/gitlab/jira/middleware.rb:15:in `call'
    lib/gitlab/middleware/go.rb:20:in `call'
    lib/gitlab/etag_caching/middleware.rb:13:in `call'
    lib/gitlab/middleware/correlation_id.rb:16:in `block in call'
    lib/gitlab/correlation_id.rb:15:in `use_id'
    lib/gitlab/middleware/correlation_id.rb:15:in `call'
    lib/gitlab/middleware/read_only/controller.rb:42:in `call'
    lib/gitlab/middleware/read_only.rb:18:in `call'
    lib/gitlab/middleware/basic_health_check.rb:25:in `call'
    lib/gitlab/request_context.rb:20:in `call'
    lib/gitlab/metrics/requests_rack_middleware.rb:29:in `call'
    lib/gitlab/middleware/release_env.rb:13:in `call'

3、主要原因是：gitlab是从备份中恢复的数据，但是没有恢复原来的秘钥文件/etc/gitlab/gitlab-secrets.json，将新gitlab的秘钥文件备份gitlab-secrets.json.bak，复制原秘钥文件，重启gitlab。

4、如果找不到原来的秘钥文件了，可以重置秘钥。

root@gitlab:/# gitlab-rails console
    -------------------------------------------------------------------------------------
     GitLab:       11.5.1 (c90ae59)
     GitLab Shell: 8.4.1
     postgresql:   9.6.8
    -------------------------------------------------------------------------------------
    Both Deployment and its :status machine have defined a different default for "status". Use only one or the other for defining defaults to avoid unexpected behaviors.
    Loading production environment (Rails 4.2.10)
    irb(main):001:0> ApplicationSetting.current.reset_runners_registration_token!
    => true