Ruby on Rails | Screencasts | Download | Documentation | Weblog | Community | Source

Ticket #10093 (closed enhancement: fixed)

Opened 2 years ago

Last modified 2 years ago

cap deploy:stop brings "Couldn't find any pid file ... matching 'dispatch.spawner.pid"

Reported by: Toebee Assigned to: minam
Priority: low Milestone:
Component: Capistrano Version:
Severity: minor Keywords:
Cc:

Description

When I do cap deploy:start I get tmp/pids/dispatch.4076.pid.

cap deploy:restart works.

But cap deploy:stop brings

  • executing `deploy:stop'
  • executing "/home/example/whatever/current/script/process/reaper -a kill -r dispatch.spawner.pid" servers: foo.org? [foo.org] executing command
** [out
foo.org] Couldn't find any pid file in '/home/example/whatever/current/tmp/pids'
** [out
foo.org] matching 'dispatch.spawner.pid'
** [out
foo.org]
** [out
foo.org] (also looked for processes matching "/home/example/whatever/current/pub
** [out
foo.org] lic/dispatch.fcgi")
** [out
foo.org] command finished
  • executing "/home/example/whatever/current/script/process/reaper -a kill" servers: foo.org? [foo.org] executing command
** [out
foo.org] Killing 20314 command finished

$

Capistrano v2.1.0

Tobi

Change History

11/07/07 10:53:04 changed by Toebee

The code listing again:

  * executing `deploy:stop'
  * executing "/home/example/whatever/current/script/process/reaper -a kill -r dispatch.spawner.pid"
    servers: ["foo.org"]
    [foo.org] executing command
 ** [out :: foo.org] Couldn't find any pid file in
 '/home/example/whatever/current/tmp/pids'
 ** [out :: foo.org] matching 'dispatch.spawner.pid'
 ** [out :: foo.org]
 ** [out :: foo.org] (also looked for processes
 matching "/home/example/whatever/current/pub
 ** [out :: foo.org] lic/dispatch.fcgi")
 ** [out :: foo.org]
    command finished
  * executing "/home/example/whatever/current/script/process/reaper -a kill"
    servers: ["foo.org"]
    [foo.org] executing command
 ** [out :: foo.org] Killing 20314
    command finished
$

02/21/08 04:34:12 changed by minam

  • status changed from new to closed.
  • resolution set to fixed.

(In [8917]) don't try to kill the spawner pid if no spawner process exists (closes #10093)