whoa. Thank god I put some statistics in to help with debugging.......... It seems that the worker processes are handling one task and dieing in the middle of the process. Also, it seems that your task is never-ending. workers that haven't a task to be processed are running fine (empty_runs on 93164 and 93168 is 20, that means that they're quietly looping), so as long as they don't process any task they seem to be healthy. Every execution is done by a different worker, that seems to point towards the previous analysis of the worker dieing in the middle of processing the task. Worker processes are not respawned automatically by web2py, so it's likely you have in place some kind of supervisor that restarts them when they die. I'd make two things: 1) setting a timeout on the task, just to see if it's so long that it blocks somewhere (it may be leaking). 2) inspect logs of the worker processes to see where they get stuck.
I'd also stop all the workers, start one in the console with DEBUG logging, and see see what's going on "in real-time". > -- 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.
