本文介绍了Cron Job无法使用每当每当gem在prod Linux服务器上运行的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
在本地一切正常，我设置了一个时间驱动的作业，该作业以不同的时间间隔调用某些类方法（根据某些因素发送电子邮件）：
Everything works fine locally, I set up a time-driven job which calls certain class methods at different intervals (sends emails based on certain factors):
set :output, "&>>/tmp/cron_debug.log"
every 2.days, :at => '4:00 am' do
runner "Listing.listing_weekly_activity_reminder"
end
every 2.days, :at => '5:00 am' do
runner "Listing.listing_biweekly_activity_reminder"
end
every 2.days, :at => '6:00 am' do
runner "Listing.listing_last_activity_reminder"
end
every 1.day, :at => '7:00 am' do
runner "Listing.process_unanswered_messages"
end
我使用进行部署，如
Capfile：
require 'whenever/capistrano'
现在ssh'进入我的产品服务器，并按照答案中概述的相同步骤进行操作。
Now I ssh'ed into my prod server and followed the same steps outlined in THIS answer.
crontab -l ：
crontab -l:
# Begin Whenever generated tasks for: /data/nestie.co/releases/20160112014954/config/schedule.rb
0 4 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31 * * /bin/bash -l -c 'cd /data/nestie.co/releases/20160112014954 && bin/rails runner -e production '\''Listing.listing_weekly_activity_reminder'\'' >> &>>/tmp/cron_debug.log 2>&1'
0 5 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31 * * /bin/bash -l -c 'cd /data/nestie.co/releases/20160112014954 && bin/rails runner -e production '\''Listing.listing_biweekly_activity_reminder'\'' >> &>>/tmp/cron_debug.log 2>&1'
0 6 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31 * * /bin/bash -l -c 'cd /data/nestie.co/releases/20160112014954 && bin/rails runner -e production '\''Listing.listing_last_activity_reminder'\'' >> &>>/tmp/cron_debug.log 2>&1'
0 7 * * * /bin/bash -l -c 'cd /data/nestie.co/releases/20160112014954 && bin/rails runner -e production '\''Listing.process_unanswered_messages'\'' >> &>>/tmp/cron_debug.log 2>&1'
# End Whenever generated tasks for: /data/nestie.co/releases/20160112014954/config/schedule.rb
更新
的输出 grep CRON / var / log / syslog ：
Jan 12 06:35:01 localhost CRON[10670]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 06:45:01 localhost CRON[10913]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 06:55:01 localhost CRON[11156]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 07:00:01 localhost CRON[11279]: (deploy) CMD (/bin/bash -l -c 'cd /data/nestie.co/releases/20160112014954 && bin/rails runner -e production '\''Listing.process_unanswered_messages'\'' >> &>>/tmp/cron_debug.log 2>&1')
Jan 12 07:00:02 localhost CRON[11278]: (CRON) info (No MTA installed, discarding output)
Jan 12 07:17:01 localhost CRON[11758]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 12 07:25:01 localhost CRON[11953]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 07:35:01 localhost CRON[12196]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Dec 24 15:05:01 localhost CRON[12438]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 07:45:01 localhost CRON[12439]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 08:17:01 localhost CRON[13219]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 24 15:45:01 localhost CRON[13413]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 08:25:01 localhost CRON[13414]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Dec 24 15:55:01 localhost CRON[13656]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 08:35:01 localhost CRON[13657]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 08:45:01 localhost CRON[13900]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 08:55:01 localhost CRON[14143]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 09:05:01 localhost CRON[14527]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 09:15:01 localhost CRON[14770]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 09:17:01 localhost CRON[14821]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 12 09:25:01 localhost CRON[15016]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 09:35:01 localhost CRON[15259]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 09:45:01 localhost CRON[15502]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 09:55:01 localhost CRON[15745]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 10:05:01 localhost CRON[15993]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 10:15:01 localhost CRON[16236]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 10:17:01 localhost CRON[16287]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 12 10:25:01 localhost CRON[16482]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 10:35:01 localhost CRON[16725]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 10:45:01 localhost CRON[16968]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 10:55:01 localhost CRON[17211]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 11:05:01 localhost CRON[17454]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 11:15:01 localhost CRON[17697]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 11:17:01 localhost CRON[17748]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 12 11:25:01 localhost CRON[17943]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 11:35:01 localhost CRON[18186]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 11:45:01 localhost CRON[18429]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 11:55:01 localhost CRON[18672]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 12:05:01 localhost CRON[18915]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 12:15:01 localhost CRON[19158]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 12:17:01 localhost CRON[19209]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 12 12:25:01 localhost CRON[19404]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 12:35:01 localhost CRON[19647]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 12:45:01 localhost CRON[19890]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 12:55:01 localhost CRON[20133]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 13:35:01 localhost CRON[21108]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 13:45:01 localhost CRON[21351]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 13:55:01 localhost CRON[21594]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 14:05:01 localhost CRON[21837]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 14:15:01 localhost CRON[22080]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 14:17:01 localhost CRON[22131]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 12 14:25:01 localhost CRON[22326]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 14:35:01 localhost CRON[22610]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 14:45:01 localhost CRON[22853]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 14:55:01 localhost CRON[23096]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 15:05:01 localhost CRON[23339]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 15:15:01 localhost CRON[23582]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 15:17:01 localhost CRON[23633]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 12 15:25:01 localhost CRON[23828]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 15:35:01 localhost CRON[24071]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 15:45:01 localhost CRON[24314]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 15:55:01 localhost CRON[24557]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 16:05:01 localhost CRON[24805]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 16:15:01 localhost CRON[25048]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 16:17:01 localhost CRON[25099]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 12 16:25:01 localhost CRON[25294]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 16:35:01 localhost CRON[25537]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 16:45:01 localhost CRON[25781]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 16:55:01 localhost CRON[26026]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 17:05:01 localhost CRON[26269]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 17:15:01 localhost CRON[26512]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 17:17:01 localhost CRON[26563]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 12 17:25:01 localhost CRON[26758]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 17:35:01 localhost CRON[27001]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 17:45:01 localhost CRON[27244]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 17:55:01 localhost CRON[27487]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 18:05:01 localhost CRON[27730]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 18:15:01 localhost CRON[27973]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 18:17:01 localhost CRON[28024]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 12 18:25:01 localhost CRON[28219]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 18:35:01 localhost CRON[28668]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 18:55:01 localhost CRON[29183]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 19:15:01 localhost CRON[29670]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 19:17:01 localhost CRON[29721]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 12 19:25:01 localhost CRON[29916]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 19:35:01 localhost CRON[30159]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 19:45:01 localhost CRON[30402]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 19:55:01 localhost CRON[30671]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 20:05:01 localhost CRON[30914]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 20:15:01 localhost CRON[31157]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 20:17:01 localhost CRON[31208]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 12 20:25:01 localhost CRON[31643]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 20:35:01 localhost CRON[31887]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 20:45:01 localhost CRON[32131]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 20:55:01 localhost CRON[32375]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 21:05:01 localhost CRON[32618]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 21:15:01 localhost CRON[394]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 21:17:01 localhost CRON[446]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 12 21:25:01 localhost CRON[646]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 21:35:01 localhost CRON[898]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 21:45:01 localhost CRON[1141]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 21:55:01 localhost CRON[1389]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 22:05:01 localhost CRON[1651]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 22:15:01 localhost CRON[1894]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 22:17:01 localhost CRON[1945]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 12 22:25:01 localhost CRON[2281]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 22:55:01 localhost CRON[3040]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 23:15:01 localhost CRON[3554]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 4 17:25:01 localhost CRON[3607]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 23:17:01 localhost CRON[3607]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 12 23:25:01 localhost CRON[3802]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 12 23:59:01 localhost CRON[4633]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 60 2)
Jan 13 00:05:01 localhost CRON[4780]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 13 00:15:01 localhost CRON[5385]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 13 00:17:01 localhost CRON[5437]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 13 00:25:01 localhost CRON[5747]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 13 00:35:01 localhost CRON[6105]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 13 00:45:01 localhost CRON[6354]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 13 00:55:01 localhost CRON[6597]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 13 01:10:44 localhost cron[7009]: (CRON) DEATH (can't open or create /var/run/crond.pid: Permission denied)
Jan 13 01:10:56 localhost cron[7016]: (CRON) DEATH (can't lock /var/run/crond.pid, otherpid may be 3604: Resource temporarily unavailable)
Dec 26 07:25:01 localhost CRON[7026]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 13 01:11:36 localhost cron[7042]: (CRON) DEATH (can't open or create /var/run/crond.pid: Permission denied)
Jan 13 01:15:01 localhost CRON[7152]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 13 01:17:01 localhost CRON[7203]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 13 01:25:01 localhost CRON[7399]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 13 01:35:01 localhost CRON[7841]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 13 01:45:01 localhost CRON[8084]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 13 01:55:01 localhost CRON[8327]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 13 02:05:01 localhost CRON[8570]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 13 02:15:01 localhost CRON[8814]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 13 02:17:01 localhost CRON[8865]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 13 02:25:01 localhost CRON[9060]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
deploy@localhost:~$ sudo grep CRON /var/log/syslog
经过2天的挖掘，我还是一无所知...！
After 2 days of digging around I am still clueless...!
推荐答案
查看您的日志似乎运行crons的用户在权限方面存在一些问题：
Looking at your logs seems that the user that runs the crons has some issues with the rights/permissions:
Jan 13 01:10:44 localhost cron[7009]: (CRON) DEATH (can't open or create /var/run/crond.pid: Permission denied)
Jan 13 01:10:56 localhost cron[7016]: (CRON) DEATH (can't lock /var/run/crond.pid, otherpid may be 3604: Resource temporarily unavailable)
尝试遵循此解决方案以查看是否有帮助：
Try to follow this solution to see if this help: https://serverfault.com/questions/274434/cron-permission-denied-on-everything
更改执行权和用户权限可能可以解决此问题。
Changing the execution-rights and the user-permission could probably solve this.
这篇关于Cron Job无法使用每当每当gem在prod Linux服务器上运行的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！