-
Notifications
You must be signed in to change notification settings - Fork 622
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Something went wrong. cron reached maximum iterations. #500
Comments
This happens when it takes longer than 5 seconds to find the next "start time" for the cron job. There is a pr up to show a "soft warning". But, this will only be a partial solution as the original code fixed an infinite loop issue. You can check out the pr #499 for more detail. There are other linked tickets that you can review, but it seems to mostly happen when the cpu spikes. Hopefully in the near future I'll be able to get a better solution in place. |
Thanks. I’m running on a Giantboard, 128 MB. Seems I have a memory leak, and swapd kicks in, stalling the system. Some tweaks have help marginally, but finding the leak is turning out to be a challenge.
… On Jun 1, 2020, at 10:08 PM, Nick Campbell ***@***.***> wrote:
This happens when it takes longer than 5 seconds to find the next "start time" for the cron job. There is a pr up to show a "soft warning". But, this will only be a partial solution as the original code fixed an infinite loop issue. You can check out the pr #499 <#499> for more detail.
Hopefully in the near future I'll be able to get a better solution in place.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#500 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AORWKQEIWJD54SMBUBP4FGDRURUL7ANCNFSM4NONPOVQ>.
|
Duplicate |
29 May 18:01:02 - [red] Uncaught Exception:
29 May 18:01:06 - Error: Something went wrong. cron reached maximum iterations.
Please open an issue (https://github.com/kelektiv/node-cron/issues/new) and provide the following string
Time Zone: "" - Cron String: 0 0 18 * * * - UTC offset: -05:00 - current Date: Fri May 29 2020 18:00:57 GMT-0500
at CronTime._getNextDateFrom (/usr/lib/node_modules/node-red/node_modules/cron/lib/cron.js:235:12)
at CronTime.sendAt (/usr/lib/node_modules/node-red/node_modules/cron/lib/cron.js:156:17)
at CronTime.getTimeout (/usr/lib/node_modules/node-red/node_modules/cron/lib/cron.js:175:29)
I am using Node-Red on a Giantboard (120 MB RAM).
The text was updated successfully, but these errors were encountered: