cron job stops after certain hours.

[mek-omkar]

var job = new CronJob({
cronTime: '/1 * * * * *',
onTick:function() {
console.log(new Date, 'tick triggered');
},
onComplete: function(){/*/},
start: true,
runOnInit: true
});
job.start();

this job hanged & not seeing any logs after certain hours of execution. i am using nodejs 6.1.0 & cron 1.1.0

is cron supports every second jobs && if we not mentioned timezone which time zone takes for the job?

Thanks

[frabbit]

I can confirm this bug, it was a pain to debug, because i thought the problem was on my side.

[TJNevis]

I had the same issue...for me, it runs for a few days just fine - I have an hourly cron - and 2 days ago it stopped with no errors in the node log.

[KKKSzili]

I can confirm as well, i have cronjob running each second, but hangs after a while. The issue for me is critical because i am switching off water pump (when i do not have enough water in my well).
Using on raspberry pi with node v4.2.1 and cron 1.1.0 .

//Implementation
new CronJob('* * * * * *', function() {
     //My code here
},null,true,'Europe/Budapest',null,true);

Any help would be apreciated.
Thank you!

[jeanmatthieud]

Same problem here. I did not find any reason for that to happen in my code (every error is logged with sentry, and nothing particular happen)

[colmaengus]

I have seen this problem also. We have an every minute cron job that runs for days and days and then just stops. I'm tracking the duration between ticks and its normally 60 seconds. The last tick before it stopped was 147 seconds. Maybe this has something to do with the root cause ?

[mek-omkar]

yes i too suspecting it @colmaengus

[Hithim]

Hello guy's.
I've also caught this bug, it's really hard to reproduce it, for me it happens when there is intense CPU and memory allocation.
I've figured out for now that it stops task here: https://github.com/ncb000gt/node-cron/blob/master/lib/cron.js#L453 .
So for some reason timeout become a negative value, I've tested with */1 * * * * * pattern.

[colmaengus]

We are seeing this quite a lot now. Adding some extra logs it looks to be when node is running so slowly that the next tick time comes around while you are trying to figure out what that next time should be.
start of getTimeout generated "now" as 12:45:01 at 12:45:08.329
exit of _getNextDateFrom logged next tick to be 12:46:00 at 12:45:52.372
exit of sendAt logged next tick to be 12:46:00 at 12:46:00.399

Apart from the discrepancy of some seconds in the logs it would appear that _getNextDateFrom took so long to run that the next time to tick had come around already. The cron job was set to run every minute so there should have only been max 60 iterations through the while loop so I don't know what would cause the extreme slowdown. Apart from the node.js process in general being starved of cpu cycles.

[2016-08-18 12:45:08.329] [INFO] scheduler - getTimeout: 2016-08-18T12:45:01+01:00 [2016-08-18 12:45:52.372] [INFO] scheduler - _getNextDateFrom: 2016-08-18T12:46:00+01:00 [2016-08-18 12:46:00.399] [INFO] scheduler - sendAt: 2016-08-18T12:46:00+01:00 [2016-08-18 12:46:01.032] [INFO] scheduler - timeout:-1

[akhare22sandeep]

We are also facing same issue . Our job runs every second and it works perfectly for a day or max 2 days but after that we don't see any logs , connections to DB are also lost . it just hangs .... Restarting the job again works fine. till now i was thinking its code issue but other people are also facing the same issue. Please let us know if there is work around for this or otherwise we will have to change the module. Help is appreciated

[ncb000gt]

This issue is the same as #231 - I'm looking into this now.

Sorry for the delayed response. I've had no time to look into my open source projects. Thanks for digging into it - I'll share anything I find here.

[anthonywebb]

Keep us posted, thanks!

[soundslocke]

Glad to see some more info being uncovered. This has been going on a while, see #141. A fix was attempted with #147.

[medisoft]

Is this fixed in 1.3? With 1.1 I still having the problem.

[Shayko94]

Unfortunately error is still there. Cron just stops after certain hours without any error message :(