Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

'foreman start' command doesn't run in windows 7 #216

Closed
ghost opened this Issue · 3 comments

4 participants

@ghost

Hi,

I'm using foreman gem for delayed jobs.
When I try to run 'foreman start' I get the following error:

C:/Ruby192/lib/ruby/gems/1.9.1/gems/foreman-0.48.0.pre1/lib/foreman/engine.rb:42:in trap': unsupported signal SIGHUP (ArgumentError)
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/foreman-0.48.0.pre1/lib/foreman/engine.rb:42:in
start'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/foreman-0.48.0.pre1/lib/foreman/cli.rb:35:in start'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor/task.rb:22:in
run'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor/invocation.rb:118:in invoke_task'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor.rb:263:in
dispatch'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor/base.rb:389:in start'
from C:/Ruby192/lib/ruby/gems/1.9.1/gems/foreman-0.48.0.pre1/bin/foreman:7:in
'
from C:/Ruby192/bin/foreman:23:in load'
from C:/Ruby192/bin/foreman:23:in

'

It used to work until ~10 days ago.
Any help would be appreciated.

Best,
Roi

@aaronkhoo

I'm running into the same exact issue as well with the 0.47 version of foreman:

c:\Users\Aaron\RubyMineProjects\traderpogserver>foreman.bat start
C:/ruby-1.9.3/lib/ruby/gems/1.9.1/gems/foreman-0.47.0/lib/foreman/engine.rb:39:i
n trap': unsupported signal SIGHUP (ArgumentError)
from C:/ruby-1.9.3/lib/ruby/gems/1.9.1/gems/foreman-0.47.0/lib/foreman/e
ngine.rb:39:in
start'
from C:/ruby-1.9.3/lib/ruby/gems/1.9.1/gems/foreman-0.47.0/lib/foreman/c
li.rb:34:in start'
from C:/ruby-1.9.3/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor/task.rb
:22:in
run'
from C:/ruby-1.9.3/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor/invocat
ion.rb:118:in invoke_task'
from C:/ruby-1.9.3/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor.rb:263:
in
dispatch'
from C:/ruby-1.9.3/lib/ruby/gems/1.9.1/gems/thor-0.14.6/lib/thor/base.rb
:389:in start'
from C:/ruby-1.9.3/lib/ruby/gems/1.9.1/gems/foreman-0.47.0/bin/foreman:7
:in
'
from C:/ruby-1.9.3/bin/foreman:19:in load'
from C:/ruby-1.9.3/bin/foreman:19:in

'

@MarkDBlackwell

See this pull request. Useful information here says:

If you want to know which kill signals you have:

$ kill -l

If you want to know which kill signals Ruby recognizes:

$ ruby -e"p ::Signal.list.keys.join ',' "
@rwdaigle

Can be closed.

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