ruby on rails - Missing PID file when using a process manager to start delayed job -

In the BluePill log, I'm using BluePill to manage processes such as Delay jobs Receiving message:

  W, [2010-09-27T01: 23: 20.447053 # 19441] Warning -: [fsg_distro: delayed_job] pid_file / srv / fsg_distro / shared / pids / delayed_job Pid does not exist or can not be read W, [2010-09-27T01: 23: 20.447368 # 1 9 441] WARNING:: [fsg_distro: delayed_job] Start command execution: start Ruby script / delay_Jub-E production I, [ 2010-09-27 T01: 23: 20.469165 # 1 9 441] Junk Ri -: [fsg_distro: delayed_job] going down = & gt;  

So it is claiming that a PID file is missing, which is that, but should not it be made when Blu-pill starts the delayed job process?

Update To be a bit clearer about this error, I can manually run commands but bluepel fails to run the start command . When I run it manually, it looks like:

  rails @ george: / srv / fsg_distro / current $ / usr / bin / env / RAILS_ENV = output / usr / bin / Ruby / srv / fsg_distro / current / script / delayed_job start delayed_job: start pid 17564 with process.  

When I run it with bluupil, it looks like:

  W, [2010-10-03T21: 24: 13.943136 # 17326] Warning -: [Fsg_distro: delayed_job] pid_file /srv/fsg_distro/shared/pids/delayed_job.pid does not exist or can not be read W, [2010-10-03T21: 24: 13.943391 # 17326] Warning -: [fsg_distro: delayed_job ] Pid_file /srv/fsg_distro/shared/pids/delayed_job.pid does not exist or can not be read I, [2010-10-03T21: 24: 13.943811 # 17326] Information -: [fsg_distro: delayed_job] by starting> gt; ; Down w, [2010-10-03 t 21: 24: 14.945274 # 17326] Warning -: [fsg_distro: delayed_job] pid_file /srv/fsg_distro/shared/pids/delayed_job.pid does not exist or can not be read W, [ 2010-10-03 T21: 24: 14.945495 # 17326] Warning -: [fsg_distro: delayed_job] pid_file /srv/fsg_distro/shared/pids/delayed_job.pid does not exist or can not be read W, [2010-10-03T21 : 24: 14.945826 # 17326] Warning -: [fsg_distro: delayed_job] start command command: / usr / bin / env RAILS_ENV = output / usr / bin / ruby ​​/ srv / fsg_distro / current / script / delayed_job start w, [ 2010-10- 03T21: 24: 15.049261 # 17326] Warning -: [fsg_distro: delayed_job] Start command execution Non- Uny has returned exit code: W, [2010-10-03T21: 24: 15.049491 # 17326] Warning -: [fsg_distro: delayed_job] {: Stderr = & gt; "",: Exit_code = & gt; 1 ,: stdout = & gt; ""} I, [2010-10-03T21: 24: 15.049 947 # 17326] Info -: [fsg_distro: delayed_job] going from below =>  
  APP_ROOT = '/ srv / fsg_distro' RAILS_ROOT = '/ srv / fsg_distro / current' RAIL'_NIV = 'is starting production  
 
' RUBY_EXEC = '/ usr / bin / ruby' Bluepill.application ("fsg_distro" ,: log_file = & gt; "/srv/fsg_distro/shared/log/bluepill.log"). App | App.process ("delayed_job") process. Process.working_dir = RAILS_ROOT process.start_grace_time = 30.seconds process.stop_grace_time = 30.seconds process.restart_grace_time = 30.seconds process.start_command = "/ usr / bin / env RAILS_ENV = # {RAILS_ENV} # {RUBY_EXEC} # {RAILS_ROOT }} / Script / start with delay "process.stop_command =" / usr / bin / env RAILS_ENV = # {RAILS_ENV} # {RUBY_EXEC} # {RAILS_ROOT} / script / delayed_start stop "process.pid_file =" # {APP_ROOT} / Shared / Pids / delayed_job.pid "process.uid =" deployed "process.gid =" deployed "End End  

and my delayed job script looks like this:

  #! / Usr / bin / env ruby ​​ENV ['RAILS_ENV']] = 'Production' is required File.dirname (__ file__) + '/../config/environment' Requirement 'Delay / Command' is delayed: : Command.new (ARGV) .demonize  

If you are delayed_job (whatever you are) You will want generate a PID file for yourself, or to work late for it, once you have passed the

Hope to find

If you work late in the foreground, and you ask Bluupil to demo the process for you, then the Bluupil Pid file will be generated.

Both of you can not monitor a self-demonstration process and create a PID file for Bluupil. It's either one or the other.