"active" is the last status detected. If the process is a single one and no other is checking, the status won't be updated (but you'll notice that last_heartbeat doesn't get updated). If there are two processes and one fails, the other one checks for the last_heartbeat(s) and prunes the record of the inactive worker.
That being said there' nothing to "do" unless activate DEBUG logging and see where it gets stuck. One major issue usually is using SQLite, that is not that much performant with concurrent writers. On Friday, August 8, 2014 3:38:54 PM UTC+2, peter wrote: > > I am using the scheduler on a linux system. A worker process runs for a > while and then has no more heartbeats. Yet it is still marked as active. > The scheduler process still appears to be running on linux. I have looked > through relevant logs and cannot see any issues. If I relaunch the linux > process, the heartbeats start again but only for a while. I have an > identical system on another vps and this does not have the problem. Does > anyone have any suggestions for anything I might check out. > > Web2py version 2.8.2 > > Thanks > Peter > -- 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.
