Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Puma Error in init.d script #76

antoinelyset opened this Issue · 9 comments

6 participants

puma-2.0.0.b7/lib/puma/cli.rb:337:in `parse_options': invalid option: -E (OptionParser::InvalidOption)

-E option for Puma is not valid :(


it should be -e. Sorry guys. my mistake


should be fixed by 6f6e011


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


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 ...


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!


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?


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


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

@randx randx closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.