Open ruslansavenok opened 8 years ago
Same with capistranoe-resque 0.2.3.
Posible reason for resque:scheduler:restart
to fail:
Capistrano-resque stops the scheduler with
execute :kill, "-s #{fetch(:resque_kill_signal)} $(cat #{pid}); rm #{pid}"
(capistrano-resque.rake:144)
:resque_kill_signal
defaults to SIGQUIT
Since the return of kill
is not read, even if it fails, the PIDfile is removed and a new process will be started (with a new PIDfile).
When running
cap develop resque:scheduler:restart
, sometimes it doesnt kill active process from pid, instead it spawns new one. Server is running on ubuntu 14capistrano - 3.4.0 capistrano-resque - 0.2.2 resque - 1.25.2