invalid option: --control-url

[sigmike]

Steps to reproduce

1. Install puma 3.11.0

2. Create a config with only activate_control_app 'unix:///tmp/puma.sock'

3. Run pumactl -F <config file> start

Expected behavior

Starting an complaining about application not configured.

Actual behavior

invalid option: --control-url
/home/mike/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/puma-3.11.0/lib/puma/cli.rb:47:in `initialize'
/home/mike/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/puma-3.11.0/lib/puma/control_cli.rb:258:in `new'
/home/mike/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/puma-3.11.0/lib/puma/control_cli.rb:258:in `start'
/home/mike/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/puma-3.11.0/lib/puma/control_cli.rb:223:in `run'
/home/mike/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/puma-3.11.0/bin/pumactl:8:in `<top (required)>'
/home/mike/.rbenv/versions/2.4.2/bin/pumactl:23:in `load'
/home/mike/.rbenv/versions/2.4.2/bin/pumactl:23:in `<main>'

System configuration

Ruby version: 2.4.2
Rails version: N/A
Puma version: 3.11.0

Comments

Seems to be caused by commit 459ab19

Puma 3.10.0 works fine.

[crevete]

I've got the same issue and go back to 3.10 as workaround for now.

[jlduran]

459ab19

[jxa]

I get the same. The problem stems from an option mismatch between pumactl and puma cli. On puma cli the option is --control and in pumactl the option is called control-url.

Putting together a PR as soon as I figure out how to write a test for this.

[chickenham]

I noticed that a new version of puma was released but this is still not fixed. Is this going to be fixed at some point - or is there a workaround?

[jdoss]

This is a blocker on us upgrading Puma as well.

[jxa]

#1487 is a fix, but I need some help getting the new test to pass on CI. If anyone has advice or the time to look into it I'd appreciate the help.

[crevete]

@nateberkopec Why did you delete my comment ? Can you please explain me why you continue to release new versions without fixing this blocker issue ?

[frankpinto]

Just ran into this myself while upgrading from Upstart in Puma 14.04 to 16.04 and wanting to use pumactl start as the ExecStart. Any updates?

[jxa]

The fix is merged to master but not in time for the latest release. It would be really swell if they did a bugfix release for this issue.

What do you think @schneems ?

[schneems]

I have another metric I want to expose via Puma.stats probably next week. I’m fine if this goes out before then though.

[schneems]

I cut a release can this Issue be closed?

[sigmike]

Yes it's fixed in 3.12.0. Thank you.