search

nesquena / backburner

Simple and reliable beanstalkd job queue for ruby
http://nesquena.github.com/backburner
MIT License
428 stars 68 forks source link

Incompatible with foreman? #148

Closed haffla closed 6 years ago

haffla commented 6 years ago

Running bundle exec backburner works as expected. The output is

Starting backburner service...
Working 1 queues: [ backburner.worker.queue.backburner-jobs ]

When I put the same command into a Procfile and run foreman start it only says

22:01:41 backburner.1 | started with pid 7764

When I hit CTRL-C to abort I get

^C22:02:03 system       | SIGINT received, starting shutdown
22:02:03 backburner.1 | Starting backburner service...
22:02:03 backburner.1 | Working 1 queues: [ backburner.worker.queue.backburner-jobs ]
22:02:04 system       | sending SIGTERM to all processes
22:02:04 backburner.1 | exited with code 0

So it seems that the process only starts when I kill foreman. Any idea what could be the problem?

eltone commented 6 years ago

I'm not that familiar with foreman but there may be some stdout buffering happening here. Are jobs being reserved at all?

haffla commented 6 years ago

No jobs are not reserved. Maybe I forgot to add that this is in a Vagrant box?

Edit: Just tested it outside of the vagrant box on my host (Arch Linux). Same problem. It really seems that it just does not work with foreman.