you could attach the log to the message, so the thread doesn't get long:P I see 2 rounds only COMPLETED, then a huge gap
> 2012-12-16 21:39:30,330 - web2py.scheduler - INFO - task completed > (COMPLETED) > 2012-12-16 23:12:23,296 - web2py.scheduler - DEBUG - new scheduler_run > record > 2012-12-16 23:12:23,298 - web2py.scheduler - INFO - new task 1 "search for > files" ss_server/appadmin.searchForFiles > 2012-12-16 23:12:23,298 - web2py.scheduler - DEBUG - new task allocated: > ss_server/appadmin.searchForFiles > 2012-12-16 23:12:23,299 - web2py.scheduler - DEBUG - task starting > 2012-12-16 23:12:23,303 - web2py.scheduler - DEBUG - task started > 2012-12-16 23:12:23,531 - web2py.scheduler - DEBUG - new task report: > COMPLETED > 2012-12-16 23:12:23,531 - web2py.scheduler - DEBUG - result: "success" > 2012-12-16 23:12:23,573 - web2py.scheduler - DEBUG - partial output: > "serach for files > /usr/local/ss_server/web2py_ss_server > processing file: > S-1014.D-20121214121351.L-WIKILONG.I-000000000000000000055032,.P-2.jpg > IO Error > processing file: > S-1014.D-20121214135116.L-KONGS.I-000000000000000000055055,.P-1.jpg > IO Error > processing file: > S-1019.D-20121214122954.L-WIKILONG.I-xxxxxxxxxxxxxxxxxxxxTEST,.P-8.jpg > IO Error > processing file: > S-1021.D-20121214125548.L-WIKILONG.I-100000000000000000055006,.P-1.jpg > IO Error > " > 2012-12-16 23:12:23,573 - web2py.scheduler - DEBUG - task completed or > failed > 2012-12-16 23:12:23,574 - web2py.scheduler - DEBUG - recording task > report in db (COMPLETED) > 2012-12-16 23:12:23,580 - web2py.scheduler - INFO - task completed > (COMPLETED) > HUGE GAP here > 2012-12-17 03:13:26,360 - web2py.scheduler - DEBUG - ........recording > heartbeat > 2012-12-17 03:28:46,026 - web2py.scheduler - DEBUG - ........recording > heartbeat > 2012-12-17 03:28:49,068 - web2py.scheduler - DEBUG - ........recording > heartbeat > > then practically nothing. Can you tell me how the task in the scheduler_task table is at this time ? --
