Hi Zbigniew and Niphlod.
I have same/similar traceback when the task will timeout, in my case in 2h:
File "/home/www-data/web2py/gluon/scheduler.py", line 720, in
signal.signal(signal.SIGTERM, lambda signum, stack_frame: sys.exit(1))
SystemExit: 1
scheduler_run.stop_time is scheduler.start_
W dniu sobota, 17 grudnia 2016 16:07:53 UTC+1 użytkownik Zbigniew
Pomianowski napisał:
>
> I totally agree that debuging such things can be difficult. I just wonder
> if there are some mechanisms that can kill tasks before they are finished.
> 100h process let be honest - it is not a common case
I totally agree that debuging such things can be difficult. I just wonder
if there are some mechanisms that can kill tasks before they are finished.
100h process let be honest - it is not a common case. Honestly speaking i
am not pretty sure how frequent this problem can be. I did not manage to
that piece of code is in place to let the worker being terminated by a
sigterm, i.e a ctrl+c, that is useful for development purposes. it *should*
have nothing to do with long running tasks, but I'm really honest saying I
never had a single task alive for more than an hour. Frankly I don't know
4 matches
Mail list logo
