My setup is on Windows with the scheduler running as a service via nssm. I have it set to run every 86400 seconds (24hrs) with infinite number of runs and retries. The timeout is something like 2 or 3 minutes. I am also using the "cron like" option so that it always runs at exactly the same time of day. I wonder if that cron like seeing might have something to do with it like under some failure condition the number of times run field doesn't get updated so the next run time is the current time instead of getting bumped x seconds forward? Alex are you also using the cron like option?
On Saturday, February 20, 2016 at my 12:43:42 PM UTC-6, Alex wrote: > > Good to know someone else is experiencing this as well. I think there is > some web2py bug in the scheduler since there is nothing special about my > setup (apache on linux). For now I set retry_failed to 0 to avoid that > problem but I'll test it with -1 in a few weeks when I've got more time. Do > you have the values of this task from the scheduler_task table? maybe it > helps to find out what the problem is. > > Alex > > -- 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.
