Home/ Questions/Q 8573519
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T19:16:10+00:00

I have a foreman script starting up some workers on a standalone ruby app.

  • 0

I have a foreman script starting up some workers on a standalone ruby app. Here’s the script

Foreman script
worker: bundle exec rake resque:work BACKGROUND=true QUEUE=image VERBOSE=true

When I run the script this is the output I get. 

$ foreman start
22:00:38 worker.1 | started with pid 882
22:00:38 worker.1 | exited with code 0
22:00:38 system   | sending SIGTERM to all processes
SIGTERM received

The process seems to have exited but when I look at the ps -eaf | grep resque log it shows a resque worker running with pid 884. I’ve tested this and its always a pid +2 than the original.

When I run the bundle exec command straight from the terminal without foreman, the command executes just fine. Is there anything I’m missing with the foreman script?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    So apparently, when running BACKGROUND=true the resque workers get daemonized and therefore the original pid gets deleted and a new one gets spanwed as an orphan process for the worker.

    Still, there is an issue when creating 2 background workers with foreman because once one of the workers gets daemonized, foreman will end all processes and only one daemonized worker will be created instead of two.

    • 0