[web2py] Re: ghost scheduler workers can never be deleted even the web2py-schduler is stopped.

BTW (for future readers): worker names are available as the worker_name, and are by default composed by a hostname#pid format. should be easy to spot where the scheduler is actually running :-P On Wednesday, April 29, 2015 at 6:51:08 PM UTC+2, Pengfei Yu wrote: > > Thanks Niphlod! > > It turns o

[web2py] Re: ghost scheduler workers can never be deleted even the web2py-schduler is stopped.

Thanks Niphlod! It turns out that we have an data base which is shared by two duplicated instances and the other workers are from the other instance. We've fixed that. On Saturday, April 25, 2015 at 8:51:04 AM UTC-4, Niphlod wrote: > > there's nothing that magically insert records on the sch

[web2py] Re: ghost scheduler workers can never be deleted even the web2py-schduler is stopped.

there's nothing that magically insert records on the scheduler_worker table. watch the last_heartbeat column and see if it changes. If it's changing, the workers are still running somewhere and accessing your database. On Friday, April 24, 2015 at 9:24:59 PM UTC+2, Pengfei Yu wrote: > > Hi I am