终端说delay_job开始,但是什么也没做 [英] Terminal says delayed_job starting, but not doing anything

查看:117
本文介绍了终端说delay_job开始,但是什么也没做的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个可以在本地计算机上完美运行的应用程序,现在正在部署它。我已经设置了VPS,并且几乎可以正常运行。我的问题来自无法启动delay_job。 SSHd到应用程序时,我执行 ruby​​ script / delayed_job start RAILS_ENV = production,并且返回 delayed_job:pid为11547的进程已启动。当我在htop中寻找过程时,找不到它。

I have an app that works perfectly on my local machine and am deploying it now. I have the VPS all set up and it pretty much works, as well. My problem comes from not being able to start delayed_job. I do the "ruby script/delayed_job start RAILS_ENV=production" while SSHd to the app and it returns "delayed_job: process with pid 11547 started." When I look for the process in htop, I can't find it.

所以我挖了一下,读到Monit可以使delay_job继续进行。我进行了设置,希望可以以这种方式启动delay_job。但是,没有delay_job.pid,所以我走不远。我最终在其中设置了nginx和mysql,并想完成对delay_job的设置。

So I dug around and read that Monit can keep delayed_job going. I set that up, hoping I could start up the delayed_job that way. There's no delayed_job.pid, though, so I didn't get far. I ended up setting up nginx and mysql in it, though, and would like to finish setting up delayed_job. The lack of delayed_job.pid gets in the way.

当我通过SSH进入应用程序并运行 rake jobs:work RAILS_ENV = production时,一切正常。因此,我很确定该应用程序本身还可以。

When I SSH into the app and run "rake jobs:work RAILS_ENV=production", everything works just fine. So I'm pretty sure the app itself is fine.

我正在使用Collectoridea的delay_job。谢谢您的帮助。

I'm using collectiveidea's delayed_job. Thanks for any help.

推荐答案

事实证明,守护程序gem存在问题。使用ghazel-daemons分支效果很好。现在开始设置Monit。

It turns out that there's a problem with the daemons gem. Using the ghazel-daemons fork works perfectly. Now onto setting up Monit.

这篇关于终端说delay_job开始,但是什么也没做的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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