with CRON like pattern, job just stopped with no error after 25d
See original GitHub issueconst CronJob = require('cron').CronJob;
const cronJob1 = new CronJob('*/5 * * * * *', async function () {
const ret = await redis.lock('LOCK_REFRESH_WIDGET', 4);
if (ret) {
await refresh();
}
});
cronJob1.start();
_Originally posted by @lvgithub in https://github.com/kelektiv/node-cron/issues/387#issuecomment-439752249_
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
linux - Cron job mysteriously stopped running?
1. There should be something in your system log when the job was run. The other thing you could try is to add...
Read more >Cron job troubleshooting guide
Check that your cron job is running by finding the attempted execution in syslog · Begin by grepping for the command in /var/log/syslog...
Read more >Top Reasons Your Cron Job Isn't Running
Top reasons your cron job isn't running · 1. Schedule errors · 2. Environmental incompatibilities · 3. Depleted resources · 4. Overlapping jobs....
Read more >Scheduling Tasks With Cron Jobs - Code - Envato Tuts+
When you write a cron job in a web scripting language like PHP, you may want to make sure that nobody can execute...
Read more >How to Check if a Cron Job has Run (Crontab Log)
Using the crontab information provided in cPanel you can determine when a cron job was supposed to run. In some cases, cron jobs...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
thanks, I will try and come back to you
@pqvst awesome, thanks! i’m going to close this ticket. please let me know if you’re still running into this.