I'm using Postgresql. I do have debug logging enabled, as you can see in the initial post. Here's a bit more detail:
2014-08-18 07:14:05,079 - web2py.scheduler.zebra.local#34260 - DEBUG - ........recording heartbeat (RUNNING) 2014-08-18 07:14:08,087 - web2py.scheduler.zebra.local#34260 - DEBUG - ........recording heartbeat (RUNNING) 2014-08-18 07:14:08,574 - web2py.scheduler.zebra.local#34260 - DEBUG - new task report: COMPLETED 2014-08-18 07:14:08,575 - web2py.scheduler.zebra.local#34260 - DEBUG - result: null 2014-08-18 07:14:11,095 - web2py.scheduler.zebra.local#34260 - DEBUG - ........recording heartbeat (RUNNING) 2014-08-18 07:14:11,096 - web2py.scheduler.zebra.local#34260 - DEBUG - freeing workers that have not sent heartbeat 2014-08-18 07:14:14,101 - web2py.scheduler.zebra.local#34260 - DEBUG - ........recording heartbeat (RUNNING) 2014-08-18 07:14:17,103 - web2py.scheduler.zebra.local#34260 - DEBUG - ........recording heartbeat (RUNNING) 2014-08-18 07:14:20,107 - web2py.scheduler.zebra.local#34260 - DEBUG - ........recording heartbeat (RUNNING) 2014-08-18 07:14:23,109 - web2py.scheduler.zebra.local#34260 - DEBUG - ........recording heartbeat (RUNNING) ... 2014-08-18 07:14:46,725 - web2py.scheduler.zebra.local#34260 - DEBUG - task timeout 2014-08-18 07:14:46,726 - web2py.scheduler.zebra.local#34260 - DEBUG - deleting task report in db because of no result 2014-08-18 07:14:46,729 - web2py.scheduler.zebra.local#34260 - INFO - task completed (TIMEOUT) 2014-08-18 07:14:46,729 - web2py.scheduler.zebra.local#34260 - DEBUG - looping... Is it something to do with the result: null message? On Monday, August 18, 2014 5:15:34 AM UTC-5, Niphlod wrote: > > you're probably facing problems updating the status of the running task. > If your' eusing SQLite, this might happen because it suffers blocking for > concurrent writes. if you enable the DEBUG logging, you'll probably see > where it gets stuck. > > On Monday, August 18, 2014 3:01:15 AM UTC+2, Brad Miller wrote: >> >> As a follow up question. Is it safe for me to mark the task as COMPLETED >> manually by updating the schedular_task or schedular_run table? Its not >> clear to me which one. I thought about using stop_task() but that did not >> appear to work, plus it seems silly to have the task marked as failed when >> it clearly did not fail. >> >> Thanks, >> >> Brad >> >> >> On Friday, August 15, 2014 9:27:55 AM UTC-5, Brad Miller wrote: >>> >>> Hi, >>> >>> I've been using the scheduler quite successfully for a while now. But >>> lately I've been getting TIMEOUTS on tasks that are successfully running to >>> completion. I know this because: >>> >>> 1. I've added my own file mechanism to show that I made until the end, >>> plus I can see that the results of the scheduled task are correct. >>> 2. I've turned on logging and I can see: >>> >>> 2014-08-15 09:14:06,617 - web2py.scheduler.zebra.local#34260 - DEBUG - >>> ........recording heartbeat (RUNNING) >>> 2014-08-15 09:14:09,172 - web2py.scheduler.zebra.local#34231 - DEBUG - >>> defining tables (migrate=True) >>> 2014-08-15 09:14:09,631 - web2py.scheduler.zebra.local#34260 - DEBUG - >>> ........recording heartbeat (RUNNING) >>> 2014-08-15 09:14:12,151 - web2py.scheduler.zebra.local#34231 - DEBUG - >>> defining tables (migrate=True) >>> 2014-08-15 09:14:12,635 - web2py.scheduler.zebra.local#34260 - DEBUG - >>> ........recording heartbeat (RUNNING) >>> 2014-08-15 09:14:14,757 - web2py.scheduler.zebra.local#34260 - DEBUG - >>> new task report: COMPLETED >>> >>> However as I monitor the database tables the task staying in RUNNING >>> mode for the full five minutes until it then goes into TIMEOUT. >>> >>> This is driving me crazy. Is there some way I can debug this? I've >>> tried various (stable) versions of web2py and am getting the same result. >>> >>> Thanks, >>> >>> Brad >>> >>> >>> -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
