Cron job runs twice in PM2 about croner HOT 3 CLOSED

There were a bug in croner where high load (on the system) would cause an early trigger. Javascript timeout "lost" time. I think it were fixed in 4.3.15, whereas pm2 use 4.1.92. It could either be that, or a bug in pm2.

In recent versions, it is impossible for croner to run early or trigger two runs the same second. I would recommend them to use 6.x.

PR available in Unitech/pm2#5317

Will leave this bug open and investigate further when there is time

from croner.

@Hexagon thank you for the answer! I will try somehow to use fresh croner. Seems like pm2 is not actively maintained :(

from croner.

@faustoFF You could try using https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides and point it to a recent version, latest 4.x should be compatible. Maybe even 5.x. If 5.7.0 works it would be optimal.

6.x will not work ootb, it has a different interface.

Let me know how it works out.

from croner.