Where are you running your app? If it's PythonAnywhere they regular restart backend systems so there's no guarantee on any task hanging around for very long. https://help.pythonanywhere.com/pages/LongRunningTasks/
Beyond that we had a lot of similar issues that we couldn't quite put our finger on and in the end decided to roll our own scheduler service - depends how mission critical / complex your requirements are I suppose. On Friday, 6 November 2015 02:20:43 UTC+1, Benson Myrtil wrote: > > Good morning, > > I am sure this is a noob question but I cant seem to find a solid answer. > I have started a worker nodes using the 'python web2py.py -K [app]' > command. Everything appears to work fine for a while. My scheduled task > need to run once a day but I am noticing that the worker node randomly > 'dies' after a couple of hours. > > Is there some setting I am missing to prevent the worker nodes from dying > even if they are idle for several hours? > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
