Skip to content

Gitlab 14.4.0 shows on start: Unable to load application: NameError: uninitialized constant Sidekiq::JobLogger

Summary

Starting gitlab-ce on FreeBSD (I'm the maintainer of the gitlab-ce port) is not possible. Maybe someone has an idea what the problem could be.

Steps to reproduce

As packages are not yet running, they are not published yet. But it could be related to the upgrade of sidekiq from version 5 to 6.

What is the current bug behavior?

It shows the error:

.{"severity":"INFO","time":"2021-10-22T20:34:48.199Z","message":"Starting cluster with 1 processes"}
.{"timestamp":"2021-10-22T20:34:49.109Z","pid":9349,"message":"Puma starting in cluster mode..."}
{"timestamp":"2021-10-22T20:34:49.109Z","pid":9349,"message":"* Puma version: 5.3.2 (ruby 2.7.4-p191) (\"Sweetnighter\")"}
{"timestamp":"2021-10-22T20:34:49.109Z","pid":9349,"message":"*  Min threads: 1"}
{"timestamp":"2021-10-22T20:34:49.109Z","pid":9349,"message":"*  Max threads: 16"}
{"timestamp":"2021-10-22T20:34:49.109Z","pid":9349,"message":"*  Environment: production"}
{"timestamp":"2021-10-22T20:34:49.109Z","pid":9349,"message":"*   Master PID: 9349"}
{"timestamp":"2021-10-22T20:34:49.109Z","pid":9349,"message":"*      Workers: 3"}
{"timestamp":"2021-10-22T20:34:49.109Z","pid":9349,"message":"*     Restarts: (✔) hot (✖) phased"}
{"timestamp":"2021-10-22T20:34:49.109Z","pid":9349,"message":"* Preloading application"}
...................{"timestamp":"2021-10-22T20:35:08.704Z","pid":9349,"message":"! Unable to load application: NameError: uninitialized constant Sidekiq::JobLogger"}
bundler: failed to load command: puma (/usr/local/bin/puma)
Traceback (most recent call last):
        60: from /usr/local/bin/bundle:23:in `<main>'
        59: from /usr/local/bin/bundle:23:in `load'
        58: from /usr/local/lib/ruby/gems/2.7/gems/bundler-2.2.28/exe/bundle:37:in `<top (required)>'
        57: from /usr/local/lib/ruby/gems/2.7/gems/bundler-2.2.28/lib/bundler/friendly_errors.rb:128:in `with_friendly_errors'
        56: from /usr/local/lib/ruby/gems/2.7/gems/bundler-2.2.28/exe/bundle:49:in `block in <top (required)>'
        55: from /usr/local/lib/ruby/gems/2.7/gems/bundler-2.2.28/lib/bundler/cli.rb:25:in `start'
        54: from /usr/local/lib/ruby/gems/2.7/gems/bundler-2.2.28/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
        53: from /usr/local/lib/ruby/gems/2.7/gems/bundler-2.2.28/lib/bundler/cli.rb:31:in `dispatch'
        52: from /usr/local/lib/ruby/gems/2.7/gems/bundler-2.2.28/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
        51: from /usr/local/lib/ruby/gems/2.7/gems/bundler-2.2.28/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
        50: from /usr/local/lib/ruby/gems/2.7/gems/bundler-2.2.28/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
        49: from /usr/local/lib/ruby/gems/2.7/gems/bundler-2.2.28/lib/bundler/cli.rb:478:in `exec'
        48: from /usr/local/lib/ruby/gems/2.7/gems/bundler-2.2.28/lib/bundler/cli/exec.rb:23:in `run'
        47: from /usr/local/lib/ruby/gems/2.7/gems/bundler-2.2.28/lib/bundler/cli/exec.rb:58:in `kernel_load'
        46: from /usr/local/lib/ruby/gems/2.7/gems/bundler-2.2.28/lib/bundler/cli/exec.rb:58:in `load'
        45: from /usr/local/bin/puma:23:in `<top (required)>'
        44: from /usr/local/bin/puma:23:in `load'
        43: from /usr/local/lib/ruby/gems/2.7/gems/puma-5.3.2/bin/puma:10:in `<top (required)>'
        42: from /usr/local/lib/ruby/gems/2.7/gems/puma-5.3.2/lib/puma/cli.rb:80:in `run'
        41: from /usr/local/lib/ruby/gems/2.7/gems/puma-5.3.2/lib/puma/launcher.rb:181:in `run'
        40: from /usr/local/lib/ruby/gems/2.7/gems/puma-5.3.2/lib/puma/cluster.rb:349:in `run'
        39: from /usr/local/lib/ruby/gems/2.7/gems/puma-5.3.2/lib/puma/runner.rb:143:in `load_and_bind'
        38: from /usr/local/lib/ruby/gems/2.7/gems/puma-5.3.2/lib/puma/configuration.rb:267:in `app'
        37: from /usr/local/lib/ruby/gems/2.7/gems/puma-5.3.2/lib/puma/configuration.rb:345:in `load_rackup'
        36: from /usr/local/lib/ruby/gems/2.7/gems/rack-2.2.3/lib/rack/builder.rb:66:in `parse_file'
        35: from /usr/local/lib/ruby/gems/2.7/gems/rack-2.2.3/lib/rack/builder.rb:105:in `load_file'
        34: from /usr/local/lib/ruby/gems/2.7/gems/rack-2.2.3/lib/rack/builder.rb:116:in `new_from_string'
        33: from /usr/local/lib/ruby/gems/2.7/gems/rack-2.2.3/lib/rack/builder.rb:116:in `eval'
        32: from config.ru:5:in `block in <main>'
        31: from config.ru:5:in `require'
        30: from /usr/local/www/gitlab-ce/config/environment.rb:7:in `<top (required)>'
        29: from /usr/local/lib/ruby/gems/2.7/gems/railties-6.1.4.1/lib/rails/application.rb:391:in `initialize!'
        28: from /usr/local/lib/ruby/gems/2.7/gems/railties-6.1.4.1/lib/rails/initializable.rb:60:in `run_initializers'
        27: from /usr/local/lib/ruby/2.7/tsort.rb:205:in `tsort_each'
        26: from /usr/local/lib/ruby/2.7/tsort.rb:226:in `tsort_each'
        25: from /usr/local/lib/ruby/2.7/tsort.rb:347:in `each_strongly_connected_component'
        24: from /usr/local/lib/ruby/2.7/tsort.rb:347:in `call'
        23: from /usr/local/lib/ruby/2.7/tsort.rb:347:in `each'
        22: from /usr/local/lib/ruby/2.7/tsort.rb:349:in `block in each_strongly_connected_component'
        21: from /usr/local/lib/ruby/2.7/tsort.rb:431:in `each_strongly_connected_component_from'
        20: from /usr/local/lib/ruby/2.7/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
        19: from /usr/local/lib/ruby/2.7/tsort.rb:228:in `block in tsort_each'
        18: from /usr/local/lib/ruby/gems/2.7/gems/railties-6.1.4.1/lib/rails/initializable.rb:61:in `block in run_initializers'
        17: from /usr/local/lib/ruby/gems/2.7/gems/railties-6.1.4.1/lib/rails/initializable.rb:32:in `run'
        16: from /usr/local/lib/ruby/gems/2.7/gems/railties-6.1.4.1/lib/rails/initializable.rb:32:in `instance_exec'
        15: from /usr/local/lib/ruby/gems/2.7/gems/railties-6.1.4.1/lib/rails/application/finisher.rb:133:in `block in <module:Finisher>'
        14: from /usr/local/lib/ruby/gems/2.7/gems/zeitwerk-2.4.2/lib/zeitwerk/loader.rb:508:in `eager_load_all'
        13: from /usr/local/lib/ruby/gems/2.7/gems/zeitwerk-2.4.2/lib/zeitwerk/loader.rb:508:in `each'
        12: from /usr/local/lib/ruby/gems/2.7/gems/zeitwerk-2.4.2/lib/zeitwerk/loader.rb:393:in `eager_load'
        11: from /usr/local/lib/ruby/gems/2.7/gems/zeitwerk-2.4.2/lib/zeitwerk/loader.rb:393:in `synchronize'
        10: from /usr/local/lib/ruby/gems/2.7/gems/zeitwerk-2.4.2/lib/zeitwerk/loader.rb:404:in `block in eager_load'
         9: from /usr/local/lib/ruby/gems/2.7/gems/zeitwerk-2.4.2/lib/zeitwerk/loader.rb:725:in `ls'
         8: from /usr/local/lib/ruby/gems/2.7/gems/zeitwerk-2.4.2/lib/zeitwerk/loader.rb:725:in `foreach'
         7: from /usr/local/lib/ruby/gems/2.7/gems/zeitwerk-2.4.2/lib/zeitwerk/loader.rb:733:in `block in ls'
         6: from /usr/local/lib/ruby/gems/2.7/gems/zeitwerk-2.4.2/lib/zeitwerk/loader.rb:409:in `block (2 levels) in eager_load'
         5: from /usr/local/lib/ruby/gems/2.7/gems/zeitwerk-2.4.2/lib/zeitwerk/loader.rb:409:in `const_get'
         4: from /usr/local/lib/ruby/gems/2.7/gems/zeitwerk-2.4.2/lib/zeitwerk/kernel.rb:26:in `require'
         3: from /usr/local/lib/ruby/gems/2.7/gems/zeitwerk-2.4.2/lib/zeitwerk/kernel.rb:26:in `require'
         2: from /usr/local/www/gitlab-ce/lib/gitlab/sidekiq_logging/structured_logger.rb:6:in `<top (required)>'
         1: from /usr/local/www/gitlab-ce/lib/gitlab/sidekiq_logging/structured_logger.rb:7:in `<module:Gitlab>'
/usr/local/www/gitlab-ce/lib/gitlab/sidekiq_logging/structured_logger.rb:8:in `<module:SidekiqLogging>': uninitialized constant Sidekiq::JobLogger (NameError)
....................................................................................................
Waited 120s for the processes to write their pids, something probably went wrong.

What is the expected correct behavior?

It should start like version 14.3.x did it.

Relevant logs and/or screenshots

Output of checks

root@gitlab:/usr/local/www/gitlab-ce # su -l git -c "cd /usr/local/www/gitlab-ce && rake gitlab:env:info RAILS_ENV=production"

System information
System:
Current User:   git
Using RVM:      no
Ruby Version:   2.7.4p191
Gem Version:    3.0.8
Bundler Version:2.2.28
Rake Version:   13.0.6
Redis Version:  6.2.6
Git Version:    2.33.0
Sidekiq Version:6.2.2
Go Version:     unknown

GitLab information
Version:        14.4.0
Revision:       Unknown
Directory:      /usr/local/www/gitlab-ce
DB Adapter:     PostgreSQL
DB Version:     12.8
URL:            http://gitlab.idefix.lan
HTTP Clone URL: http://gitlab.idefix.lan/some-group/some-project.git
SSH Clone URL:  git@gitlab.idefix.lan:some-group/some-project.git
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers:

GitLab Shell
Version:        13.21.1
Repository storage paths:
- default:      /usr/local/git/repositories
GitLab Shell path:              /usr/local/share/gitlab-shell
Git:            /usr/local/bin/git

Some checks are failing, as gitlab could not be started.

root@gitlab:/usr/local/www/gitlab-ce # su -l git -c "cd /usr/local/www/gitlab-ce && rake gitlab:check RAILS_ENV=production"
Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 13.21.1 ? ... OK (13.21.1)
Running /usr/local/share/gitlab-shell/bin/check
Internal API available: FAILED - Internal API error (502)
gitlab-shell self-check failed
  Try fixing it:
  Make sure GitLab is running;
  Check the gitlab-shell configuration file:
  sudo -u git -H editor /usr/local/share/gitlab-shell/config.yml
  Please fix the error above and rerun the checks.

Checking GitLab Shell ... Finished

Checking Gitaly ...

Gitaly: ... default ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... no
  Try fixing it:
  sudo -u git -H RAILS_ENV=production bin/background_jobs start
  For more information see:
  doc/install/installation.md in section "Install Init Script"
  see log/sidekiq.log for possible errors
  Please fix the error above and rerun the checks.

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Reply by email is disabled in config/gitlab.yml

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab App ...

Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... no
  Try fixing it:
  Install the init script
  For more information see:
  doc/install/installation.md in section "Install Init Script"
  Please fix the error above and rerun the checks.
Init script up-to-date? ... can't check because of previous errors
Projects have namespace: ...
Matthias Fechner / abook ... yes
... (I remove all repositories, all checks were yes)
Matthias Fechner / test2 ... yes
Redis version >= 5.0.0? ... yes
Ruby version >= 2.7.2 ? ... yes (2.7.4)
Git version >= 2.33.0 ? ... yes (2.33.0)
Git user has default SSH configuration? ... yes
Active users: ... 3
Is authorized keys file accessible? ... yes
GitLab configured to store new projects in hashed storage? ... yes
All projects are in hashed storage? ... yes

Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check
root@gitlab:/usr/local/www/gitlab-ce # su -l git -c "cd /usr/local/www/gitlab-ce && bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true"
Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 13.21.1 ? ... OK (13.21.1) Running /usr/local/share/gitlab-shell/bin/check Internal API available: FAILED - Internal API error (502) gitlab-shell self-check failed Try fixing it: Make sure GitLab is running; Check the gitlab-shell configuration file: sudo -u git -H editor /usr/local/share/gitlab-shell/config.yml Please fix the error above and rerun the checks.

Checking GitLab Shell ... Finished

Checking Gitaly ...

Gitaly: ... default ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... no Try fixing it: sudo -u git -H RAILS_ENV=production bin/background_jobs start For more information see: doc/install/installation.md in section "Install Init Script" see log/sidekiq.log for possible errors Please fix the error above and rerun the checks.

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Reply by email is disabled in config/gitlab.yml

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab App ...

Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... no Try fixing it: Install the init script For more information see: doc/install/installation.md in section "Install Init Script" Please fix the error above and rerun the checks. Init script up-to-date? ... can't check because of previous errors Projects have namespace: ... 1/1 ... yes 5/3 ... yes 1/4 ... yes 1/5 ... yes 1/6 ... yes 11/7 ... yes 11/8 ... yes 1/9 ... yes 1/10 ... yes 1/11 ... yes 1/12 ... yes 1/13 ... yes 2/14 ... yes 3/15 ... yes 1/16 ... yes 5/17 ... yes 4/18 ... yes 4/19 ... yes 4/20 ... yes 4/21 ... yes 4/22 ... yes 4/23 ... yes 4/24 ... yes 4/25 ... yes 4/26 ... yes 4/27 ... yes 1/28 ... yes 8/29 ... yes 9/30 ... yes 3/31 ... yes 1/32 ... yes 3/33 ... yes 1/34 ... yes 1/35 ... yes 3/36 ... yes 3/37 ... yes 3/38 ... yes 1/39 ... yes 1/40 ... yes 3/41 ... yes 1/42 ... yes 1/43 ... yes 1/44 ... yes 1/45 ... yes 1/46 ... yes 1/47 ... yes 1/48 ... yes 3/49 ... yes 3/50 ... yes 3/51 ... yes 3/52 ... yes 1/53 ... yes 10/54 ... yes 1/55 ... yes 1/56 ... yes 1/57 ... yes 1/58 ... yes 1/59 ... yes 1/60 ... yes 1/61 ... yes 1/62 ... yes 1/63 ... yes 1/64 ... yes 1/65 ... yes 1/66 ... yes 1/67 ... yes 3/68 ... yes 1/69 ... yes 1/70 ... yes 1/71 ... yes 1/72 ... yes 1/73 ... yes 1/74 ... yes 1/75 ... yes 1/76 ... yes 1/77 ... yes 1/78 ... yes 1/79 ... yes 1/80 ... yes 1/81 ... yes 1/82 ... yes 1/83 ... yes 1/84 ... yes 9/85 ... yes 9/86 ... yes 11/87 ... yes 2/88 ... yes 1/89 ... yes 1/90 ... yes 1/91 ... yes 4/92 ... yes 1/97 ... yes 12/98 ... yes 1/101 ... yes 1/105 ... yes Redis version >= 5.0.0? ... yes Ruby version >= 2.7.2 ? ... yes (2.7.4) Git version >= 2.33.0 ? ... yes (2.33.0) Git user has default SSH configuration? ... yes Active users: ... 3 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes

Checking GitLab App ... Finished

Checking GitLab subtasks ... Finished

Possible fixes