You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2024. It is now read-only.
[root@node_a ~]# service gitlab restart
Using /usr/local/rvm/gems/ruby-1.9.3-p392
Stopping puma: [FAILED]
Stopping sidekiq: [FAILED]
Starting puma: bundler: command not found: puma
Install missing gem executables with bundle install
[FAILED]
Starting sidekiq: [ OK ]
Ok - this appears to be due to a mistaken version of the init script. However, I am unable to find the proper version that both uses unicorn AND works.
The text was updated successfully, but these errors were encountered:
@balajicuttackam - I also ran into an environment problem that had to be fixed to get ruby to properly install.
In the section 'Load RVM' I had to manually set the RVM path in the environment. For some reason the RVM script sourced later doesn't set things properly until the next boot.
so : place the following at the start of the load rvm section.
PATH=$PATH:/usr/local/rvm/bin
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
[root@node_a ~]# service gitlab restart
Using /usr/local/rvm/gems/ruby-1.9.3-p392
Stopping puma: [FAILED]
Stopping sidekiq: [FAILED]
Starting puma: bundler: command not found: puma
Install missing gem executables with
bundle install
[FAILED]
Starting sidekiq: [ OK ]
Ok - this appears to be due to a mistaken version of the init script. However, I am unable to find the proper version that both uses unicorn AND works.
The text was updated successfully, but these errors were encountered: