-
Notifications
You must be signed in to change notification settings - Fork 422
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Starting unicorn: bash: bundle: command not found #66
Comments
This thing happend with me too. :( |
I mapped manually all the executables of the ruby to the system so every user can execute the all comands. Here is the command that I used: ln -s /usr/local/rvm/rubies/ruby-1.9.3-p429/bin/erb /sbin/erb
ln -s /usr/local/rvm/rubies/ruby-1.9.3-p429/bin/gem /sbin/gem
ln -s /usr/local/rvm/rubies/ruby-1.9.3-p429/bin/irb /sbin/irb
ln -s /usr/local/rvm/rubies/ruby-1.9.3-p429/bin/rake /sbin/rake
ln -s /usr/local/rvm/rubies/ruby-1.9.3-p429/bin/rdoc /sbin/rdoc
ln -s /usr/local/rvm/rubies/ruby-1.9.3-p429/bin/ri /sbin/ri
ln -s /usr/local/rvm/rubies/ruby-1.9.3-p429/bin/ruby /sbin/ruby
ln -s /usr/local/rvm/rubies/ruby-1.9.3-p429/bin/testrb /sbin/testrb
ln -s /usr/local/rvm/gems/ruby-1.9.3-p429/bin/bundle /sbin/bundle
ln -s /usr/local/rvm/gems/ruby-1.9.3-p429/bin/ruby_noexec_wrapper /sbin/ruby_noexec_wrapper |
Just a suggestion, try rvmsudo.... |
Hi, is this still an issue? Can it be closed? |
Yes, it can be closed. Sent from my iPhone On 6/08/2013, at 6:39 AM, Axilleas Pipinellis notifications@github.com Hi, is this still an issue? Can it be closed? — |
Finally after so many hours trying to setup GitLab-4-0 on our local server I managed to get it working on Centos 6.3.
Unfortunately, not everything is 100%. The /etc/init.d/ that I got from https://raw.github.com/gitlabhq/gitlab-recipes/4-0-stable/init.d/gitlab doesn't really work.
when I run sudo service gitlab start resque starts fine, unicorn doesn't.
Starting unicorn: bash: bundle: command not found [FAILED] Starting resque: [ OK ]
I have to switch to gitlab user, cd into /home/gitlab/gitlab and manually start unicorn:
bundle exec unicorn_rails -c config/unicorn.rb -E production -D
Once unicorn is running I can sudo service gitlab start
The problem with this is that if my server restarts for whatever reason, I have to manually do it all over again.
Anyone know why Starting unicorn: bash: bundle: command not found is happening?
I'm using rvm to manage ruby versions and version is 1.9.3-p385, ruby is on my path.
The text was updated successfully, but these errors were encountered: