inspect the log to see why another worker gets started. Each worker started can result AT MOST as two processes, the worker itself and the process that actually executes the task.
On Friday, June 12, 2015 at 10:36:35 PM UTC+2, Michael Gheith wrote: > > I have an application that uses the scheduler. It runs really good, > however I noticed odd behavior which I don't think is normal. > > When I launch a worker thread (just one) with the following everything > works great: > python web2py.py -K myapp > > A few days later I will come back to the node that the application is > running on, and will run the following to see my web2py processes: > pgrep -fl web2py > > and I will get something like the following: > > 11013 python web2py.py -K myapp > > 11069 python web2py.py -K myapp > > 11521 python web2py.py -K myapp > > 14466 python web2py.py -K myapp > > 14490 python web2py.py -K myapp > > 15190 python web2py.py -K myapp > > 16210 python web2py.py -K myapp > > 17019 python web2py.py -K myapp > > > Why am I getting more than one of these processes? I should just have > one, right? Is this a bug, or normal behavior? Please advise, 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
