延迟的工作不会开始使用Capistrano [英] Delayed job wont start using Capistrano

查看:59
本文介绍了延迟的工作不会开始使用Capistrano的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我无法使用Capistrano配方开始延迟的工作流程。这是我遇到的错误。

I cannot start delayed job process using a capistrano recipe. Here's the error I am getting.

/usr/local/lib/ruby/gems/1.9.1/gems/delayed_job-2.1.1/lib/delayed/command.rb:62:in `mkdir': File exists - /my_app/server/releases/20101120001612/tmp/pids (Errno::EEXIST)

这是capistrano代码(注意-:我已经尝试了两个启动/重启命令)

Here's the capistrano code (NOTE-: I have tried both start/restart commands)

after "deploy:restart", "delayed_job:start"
task :start, :roles => :app do          
  run "cd #{current_path}; RAILS_ENV=#{rails_env} script/delayed_job -n 2 start"
end

来自部署日志的更多详细信息错误-

More detail errors from deployment logs -

executing command
 [err :: my_server] /usr/local/lib/ruby/gems/1.9.1/gems/delayed_job-2.1.1/lib/delayed/command.rb:62:in `mkdir': File exists - /my_app/server/releases/20101120001612/tmp/pids (Errno::EEXIST)
 [err :: my_server] from /usr/local/lib/ruby/gems/1.9.1/gems/delayed_job-2.1.1/lib/delayed/command.rb:62:in `daemonize'
 [err :: my_server] from script/delayed_job:5:in `<main>'
    command finished
failed: "sh -c 'cd /my_app/server/current; RAILS_ENV=production script/delayed_job -n 3 restart'" on myserevr

这是Rails 3应用( v3.0.3

This is a Rails 3 app (v3.0.3)

推荐答案

这是如何解决此问题,我使用 --pid-dir传递了一个明确的pids dir参数。不知道这是否完美,但是否可行。

This is how I fixed the issue, I passed an explicit pids dir parameter using "--pid-dir". Not sure if this is perfect, but it worked.

task :restart, :roles => :app do
  run "cd #{current_path}; RAILS_ENV=#{rails_env} script/delayed_job -n #{dj_proc_count} --pid-dir=#{app_root}/shared/dj_pids restart"
end

这篇关于延迟的工作不会开始使用Capistrano的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆