Rails/Delayed_Job：重新启动延迟的作业仍然会带来过时的错误
我在发送的电子邮件中出现了elasto_job错误（未找到“user”值），
我从邮件程序视图中删除了用户字段，重新启动了乘客实例（touch tmp/restart.txt），重新启动了delayed_job工作人员（script/delayed_job）重新启动）并假设一切都会顺利进行。
但是 - 当我向延迟作业发送新邮件进程时，我仍然收到相同的错误消息。 （重申一下，这不是数据库中保留的现有错误消息 - 当我发送新邮件时，会出现相同的错误）
因此，似乎延迟的作业并没有像我希望的那样“重新启动”让它重新启动。有什么想法如何冲洗掉需要冲洗的东西吗？
I had a delayed_job error in an email I was sending ('user' value not found)
I removed the user field from the mailer view, restarted the passenger instance (touch tmp/restart.txt), restarted the delayed_job worker (script/delayed_job restart) and assumed everything would be good to go.
But - I'm still getting the same error message when I send a new mail process to delayed job. (Just to reiterate, this is not the existing error messages staying in the database - when I send a new mail, the same error comes up)
So, it seems delayed job isn't "restarting" quite as much as I'd like it to restart. Any ideas how I can flush out whatever needs flushing?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
由于延迟作业对守护进程宝石的依赖，让工作人员正确重新启动长期以来一直是一个问题。您可以在这里阅读所有相关内容：
https://github.com/collectiveidea/delayed_job/issues/3
对我有用的是使用 ghazel-daemons gem，正如线程中讨论的那样。
Getting workers to properly restart has long been an issue because of Delayed Job's reliance on the Daemons gem. You can read all about it here:
https://github.com/collectiveidea/delayed_job/issues/3
What's worked for me is to use the ghazel-daemons gem, as discussed in the thread.