Skip to content
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

Closed
naillizard opened this issue Mar 6, 2013 · 5 comments
Closed

Starting unicorn: bash: bundle: command not found #66

naillizard opened this issue Mar 6, 2013 · 5 comments

Comments

@naillizard
Copy link
Contributor

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

[gitlab@devserver gitlab]$ sudo service gitlab start
Starting unicorn: 
Starting resque:                                           [  OK  ]

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.

@antonini
Copy link

This thing happend with me too. :(
Any possible fix?

@antonini
Copy link

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

antonini added a commit to antonini/gitlab-recipes that referenced this issue Jun 14, 2013
@naillizard
Copy link
Contributor Author

Just a suggestion, try rvmsudo....

@axilleas
Copy link
Contributor

axilleas commented Aug 5, 2013

Hi, is this still an issue? Can it be closed?

@naillizard
Copy link
Contributor Author

Yes, it can be closed.

Sent from my iPhone

On 6/08/2013, at 6:39 AM, Axilleas Pipinellis notifications@github.com
wrote:

Hi, is this still an issue? Can it be closed?


Reply to this email directly or view it on
GitHubhttps://github.com//issues/66#issuecomment-22127003
.

@Razer6 Razer6 closed this as completed Aug 5, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants