-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
PM2 global error caught - Something went wrong. cron reached maximum iterations #5183
Comments
The cron library is more or less broken and abandoned. I would suggest you to have a look at github.com/hexagon/croner. Pay special attention to the section "Why another JavaScript cron implementation?" |
Published on 5.2.0 npm install pm2@latest -g
pm2 update |
This was referenced Jun 15, 2024
This was referenced Jul 5, 2024
This was referenced Jul 18, 2024
This was referenced Aug 21, 2024
This was referenced Sep 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
By time to time, PM2 crashes apparently because of a crash on the cron module. It looks like that the github page of the node-cron module is plenty of complaints about this error (https://github.com/kelektiv/node-cron/issues?page=2&q=cron+reached+maximum+iterations) but no fixes have been provided. Is it time to change the dependency to something else?
Here the error:
Here the configuration of pm2:
Here the pm2 report
The text was updated successfully, but these errors were encountered: