on 05-30-2017 2:15 PM
Hi All,
We have scheduled one of the cronjob to run as every 15 mins , some time after restarting the server the scheduler is not updating automatically.
Can you please help me to fix this issue ?
We are also facing the same issue. We have ran update on production and after that one of the cronjob is not calculating the next activation time. Trigger is showing "No next execution time - null" . if any one has resolved the same issue kindly let me know. Thanks in advance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all!
Same issue here. We've a lot of cronjobs started by a trigger with a free interval. Sometimes the trigger do not start the job and do not update the next activation time. From this moment on the next activation times is in the past and the job won't start ever again. Most of the times the solution is to create a new trigger, but we had cases where we had to clone the whole job. There are more of these failures after a restart. The maxAcceptableDelay is -1.
Are there any solutions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When you say
the scheduler is not updating automatically
what component do you mean? Or you just don't see your cronjob being executed after restart? What is parameter value maxAcceptableDelay for the trigger ? Try to set the value to -1 and retest your restart case
Sometimes the triggers fail to calculate the next activation time.
How do you see that trigger fails? What do you check to verify the "failure"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all!
We have a similar issue. Sometimes the triggers fail to calculate the next activation time. In these cases the activation time is in the past, so the cronjobs which depend on these triggers won't start ever again automatically. We have tried to refresh the trigger (by modifying an attribute of it and modifying that back, just to resave the entity) to calculate its next activation time, but it doesn't matter anymore, because in these situations the cronjobs won't stt all.
(We are using the version 5.7.)
Any help would be really appreciated!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Robin, any new informations regarding your issue?
Regards Torsten
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.