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 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 using web2py scheduler. I have a project saved in git and then I >> cloned this git repository to another new instance (server). In the new >> server, five scheduler workers (known from the ip address in the >> worker_name) from the old server are always there. When never I delete >> them, they will automatically generated soon. And it seems that they >> inherited the scheduler task program from the old server. After I updated >> the scheduler task program, it is not updated for these five ghost worker. >> Each time I initiate a new task, it will be assigned to these 5 workers >> first, and the updated task program will never be run. Could any one tell >> me how to git rid of these ghost workers. >> >> Thanks! >> > -- 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.
