This sys.exit(1) error was for all the workers of all my applications in
the same web2py installation. I've set know for all scheduler tasks the
'Prevent drift' option and it seems to works.
Il giorno giovedì 2 marzo 2017 21:16:04 UTC+1, Gael Princivalle ha scritto:
>
> Hello.
>
> I'm still have
Hello.
I'm still have hundred of similar errors on different scheduler functions.
If they are due to an error in the models how can I have a complete
traceback of this error for understanding where is it exactly, and which
one is it?
.
In shell.py the code is:
if import_models:
try
Ok probably a timing out due to the https call that has not replied in less
than 60 sec (the timeout of the task).
I've set now retry_failed to -1.
Thanks.
--
Gael Princivalle
2017-01-31 8:45 GMT+01:00 Niphlod :
> or it got a SIGTERM, or it was timing out.
>
>
> On Monday, J
>Is that the traceback from the associated record in the scheduler_run
table?
Yes
--
Gael Princivalle
2017-01-30 22:16 GMT+01:00 Anthony :
> Looks like maybe an error somewhere in your model files. Is that the
> traceback from the associated record in the scheduler_run table?
or it got a SIGTERM, or it was timing out.
On Monday, January 30, 2017 at 10:16:49 PM UTC+1, Anthony wrote:
>
> Looks like maybe an error somewhere in your model files. Is that the
> traceback from the associated record in the scheduler_run table?
>
> Anthony
>
> On Monday, January 30, 2017 at 8
Looks like maybe an error somewhere in your model files. Is that the
traceback from the associated record in the scheduler_run table?
Anthony
On Monday, January 30, 2017 at 8:02:29 AM UTC-5, Gael Princivalle wrote:
>
> Hello.
>
> I've got a scheduler function that run each 30 seconds for sending
6 matches
Mail list logo
