So I have a task queued at 00:02:07. I have a worker for that group with last_heartbeat 00:07:55. Task is still QUEUED. Worker is ACTIVE. I have TWO is_ticker workers (usually it's one).
Scheduler is up for days, it usually works. Two days ago I was resetting databases so I dropped most of the tables, including scheduler tables. They got recreated after one minute (when I deleted *.table files, I use migrations) so probably in the meantime scheduler tried to read/write table that doesn't exist. I didn't restart scheduler after that. And now it's just hanging around minding its own business, not caring about my queued tasks. Everything works after restart. I am aware that my actions might have caused weird scheduler behavior. I wrote this email because it might help, nothing else. I would be less surprised if scheduler just stopped. But I guess it tried to recover from all the issues as it usually does, but somehow failed even if it acts completely ok (has heartbeat, schedules tasks). Scheduler still rocks. Marin -- 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/groups/opt_out.
