Puma Error in init.d script about gitlab-recipes HOT 9 CLOSED

it should be -e. Sorry guys. my mistake

from gitlab-recipes.

should be fixed by 6f6e011

from gitlab-recipes.

now i'm getting
bundler: command not found: puma

from gitlab-recipes.

same here with osleg bundler: command not found: puma
but all checks in sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production shows fine ...

from gitlab-recipes.

Not sure if it's related, but I, too, am having puma issues while attempting to get GitLab running. When I try to start it with sudo service gitlab start I get this:

/usr/local/lib/ruby/gems/1.9.1/gems/bundler-1.3.5/lib/bundler/rubygems_integration.rb:214:in `block in replace_gem': puma is not part of the bundle. Add it to Gemfile. (Gem::LoadError)
        from /usr/local/bin/puma:22:in `<main>'
Gitlab service started

All the checks in sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production are passing green, save for the fact that I don't have any projects yet.

Separately, I do have the puma gem installed on the system I am trying to get GitLab running on. However, puma is not currently a part of GitLab's Gemfile (branch 5.0.1, I believe). I want to add puma to the Gemfile, because obviously something wants to use it. Alas, the git user can't sudo, so attempts at performing a bundle install always ends up at an authentication standstill. Even when I prefix the command with sudo -u git -H git the sudo invoked by bundle install always seems to want the git user's password and not mine. Any ideas on a root cause and a fix is would be greatly appreciated. If you need any more details, just ask. Thanks!

from gitlab-recipes.

I get the same thing. I tried building a new Gemfile/Gemfile.lock and bundle installing, no dice. I tried installing puma in the system gemset and changed the init script to just start up puma that way. Also no dice, running out of ideas at this point.

Should I be restricting puma to 1.6.3 or some other version?

from gitlab-recipes.

It seems that my issue is actually issue 3528, which was closed earlier today.

from gitlab-recipes.

@yesmar ahahaha, so simple. Now I feel like a dunce, good find.

from gitlab-recipes.

see https://github.com/gitlabhq/gitlabhq/issues/3528

from gitlab-recipes.