there's a method for it, get_workers(). according to your heartbeat interval, you can inspect for any worker that has a last_heartbeat too much in the past to see if it's running or not.
On Wednesday, March 9, 2016 at 12:06:50 PM UTC+1, Niphlod wrote: > > BTW: exactly as a webapp is suppossed to be kept alive from the os, the > same applies to the scheduler. That being said the controller that queue > tasks can see if any scheduler is alive inspecting the scheduler_worker > table. > > On Wednesday, March 9, 2016 at 11:42:25 AM UTC+1, Alfonso Serra wrote: >> >> Thanks Nico ill give it a try. >> >> On Wednesday, 9 March 2016 09:46:55 UTC, Nico de Groot wrote: >>> >>> Or use something like Monit (on Linux) to check if scheduler is still >>> running, restarting it if it's not. >>> >>> Nico de Groot >>> >> -- 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.
