Arch Linux

grininmonkey

Member

Registered: 2018-09-29

Posts: 34

Gitlab fresh install - gitlab-puma.service failing

I am trying to install Gitlab on a local system for the first time, I followed https://wiki.archlinux.org/title/GitLab and Redis, postgresql services are up and running with the correct socket files existing etc.... however, when I check the services for Gitlab, sidekick, workhorse they all have a fail on dependency for gitlab-puma which is showing the following from journalctl...

Jan 06 16:29:33 nzxt1 systemd[1]: Started GitLab Puma Server.
Jan 06 16:29:34 nzxt1 gitlab-puma[38953]: {"timestamp":"2022-01-06T21:29:34.468Z","pid":38953,"message":"Puma starting in cluster mode..."}
Jan 06 16:29:34 nzxt1 gitlab-puma[38953]: {"timestamp":"2022-01-06T21:29:34.468Z","pid":38953,"message":"* Puma version: 5.3.2 (ruby 2.7.5-p203) (\"Sweetnighter\")"}
Jan 06 16:29:34 nzxt1 gitlab-puma[38953]: {"timestamp":"2022-01-06T21:29:34.468Z","pid":38953,"message":"*  Min threads: 1"}
Jan 06 16:29:34 nzxt1 gitlab-puma[38953]: {"timestamp":"2022-01-06T21:29:34.468Z","pid":38953,"message":"*  Max threads: 16"}
Jan 06 16:29:34 nzxt1 gitlab-puma[38953]: {"timestamp":"2022-01-06T21:29:34.468Z","pid":38953,"message":"*  Environment: production"}
Jan 06 16:29:34 nzxt1 gitlab-puma[38953]: {"timestamp":"2022-01-06T21:29:34.468Z","pid":38953,"message":"*   Master PID: 38953"}
Jan 06 16:29:34 nzxt1 gitlab-puma[38953]: {"timestamp":"2022-01-06T21:29:34.468Z","pid":38953,"message":"*      Workers: 3"}
Jan 06 16:29:34 nzxt1 gitlab-puma[38953]: {"timestamp":"2022-01-06T21:29:34.468Z","pid":38953,"message":"*     Restarts: (✔) hot (✖) phased"}
Jan 06 16:29:34 nzxt1 gitlab-puma[38953]: {"timestamp":"2022-01-06T21:29:34.468Z","pid":38953,"message":"* Preloading application"}
Jan 06 16:29:42 nzxt1 gitlab-puma[38953]: {"timestamp":"2022-01-06T21:29:42.641Z","pid":38953,"message":"! Unable to load application: NoMethodError: undefined method `mailgun_events_enabled' for #\u003cApplicati>
Jan 06 16:29:42 nzxt1 gitlab-puma[38953]: /usr/share/webapps/gitlab/vendor/bundle/ruby/2.7.0/gems/activemodel-6.1.4.1/lib/active_model/attribute_methods.rb:469:in `method_missing': undefined method `mailgun_event>
Jan 06 16:29:42 nzxt1 gitlab-puma[38953]: Did you mean?  mailgun_signing_key
Jan 06 16:29:42 nzxt1 gitlab-puma[38953]:         from /usr/share/webapps/gitlab/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.4.1/lib/active_support/callbacks.rb:427:in `block in make_lambda'
Jan 06 16:29:42 nzxt1 gitlab-puma[38953]:         from /usr/share/webapps/gitlab/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.4.1/lib/active_support/callbacks.rb:178:in `block (2 levels) in halting_and_conditi>
Jan 06 16:29:42 nzxt1 gitlab-puma[38953]:         from /usr/share/webapps/gitlab/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.4.1/lib/active_support/callbacks.rb:178:in `all?'
Jan 06 16:29:42 nzxt1 gitlab-puma[38953]:         from /usr/share/webapps/gitlab/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.4.1/lib/active_support/callbacks.rb:178:in `block in halting_and_conditional'
Jan 06 16:29:42 nzxt1 gitlab-puma[38953]:         from /usr/share/webapps/gitlab/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.4.1/lib/active_support/callbacks.rb:512:in `block in invoke_before'
Jan 06 16:29:42 nzxt1 gitlab-puma[38953]:         from /usr/share/webapps/gitlab/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.4.1/lib/active_support/callbacks.rb:512:in `each'
Jan 06 16:29:42 nzxt1 gitlab-puma[38953]:         from /usr/share/webapps/gitlab/vendor/bundle/ruby/2.7.0/gems/activesupport-6.1.4.1/lib/active_support/callbacks.rb:512:in `invoke_before'

.............. several pages of trace and finally -------

Jan 06 16:29:42 nzxt1 gitlab-puma[38953]:         from /usr/share/webapps/gitlab/vendor/bundle/ruby/2.7.0/bin/puma:23:in `load'
Jan 06 16:29:42 nzxt1 gitlab-puma[38953]:         from /usr/share/webapps/gitlab/vendor/bundle/ruby/2.7.0/bin/puma:23:in `<main>'
Jan 06 16:29:42 nzxt1 systemd[1]: gitlab-puma.service: Main process exited, code=exited, status=1/FAILURE
Jan 06 16:29:42 nzxt1 systemd[1]: gitlab-puma.service: Failed with result 'exit-code'.
Jan 06 16:29:42 nzxt1 systemd[1]: gitlab-puma.service: Consumed 8.537s CPU time.

I have tried to find some insight but have not had much luck in understanding where or what file to check etc... the few google hits I have on that error show running ruby gems directly and not in the context of the Github bundle deployment...

I have never messed with ruby.... so its new territory for me

Lone_Wolf

Member

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,911

Re: Gitlab fresh install - gitlab-puma.service failing

Jan 06 16:29:42 nzxt1 gitlab-puma[38953]: {"timestamp":"2022-01-06T21:29:42.641Z","pid":38953,"message":"! Unable to load application: NoMethodError: undefined method `mailgun_events_enabled' for #\u003cApplicati>
Jan 06 16:29:42 nzxt1 gitlab-puma[38953]: /usr/share/webapps/gitlab/vendor/bundle/ruby/2.7.0/gems/activemodel-6.1.4.1/lib/active_model/attribute_methods.rb:469:in `method_missing': undefined method `mailgun_event>

mailgun appears to be an email delivery service, https://www.mailgun.com/ .

https://docs.gitlab.com/ee/administrati … ilgun.html might be helpful .

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)