I'm sorry, the master app is called "webmedios", so the call is ok. The log
shows "web2py.scheduler.medios" because I renamed the folder where web2py
is installed, I renamed it to "medios". So the log is ok and I think the
code too. Sorry for the confusion, my bad :P
Even though, I don't know why tasks aren't being picked up. Is there
anything else I can check?
I'm using Version 2.10.3-stable+timestamp.2015.04.02.21.42.07
El martes, 12 de mayo de 2015, 17:16:07 (UTC-3), Niphlod escribió:
>
> something is not adding up. if your app is called medios...and the log
> shows DEBUG:web2py.scheduler.medios ... why are you trying to start it
> with "webmedios" ?!?!?!
>
> On Tuesday, May 12, 2015 at 10:05:35 PM UTC+2, Lisandro wrote:
>>
>> Thanks Niphlod. I double checked, and the tasks are there.
>>
>> The main app is called "medios" and has this in its model file:
>>
>> db = DAL(\
>> 'postgres://%s:%s@%s/%s' %(DB_USER, DB_USER_PASSWORD, DB_HOST, DB_NAME
>> ), \
>> lazy_tables=True)
>>
>> from gluon.scheduler import Scheduler
>> scheduler = Scheduler(db, max_empty_runs=5)
>>
>> The I start the worker like this:
>> python /var/www/medios/web2py.py -K webmedios -D 0
>>
>> I checked the scheduler_task table of the configured db and the tasks are
>> there.
>> I tryied removing all content of scheduler tables, and then queuing the
>> tasks again. But still the same output log.
>>
>> Maybe something wrong in the task data. This is on of the rows fo
>>
>> Id: 93
>> Application Name: demo
>> Task Name: always
>> Group Name: main
>> Status: QUEUED
>> Function Name: always
>> Uuid: d2017a0a-c688-45f3-b112-cb1b2366dcce
>> Args: []
>> Vars: {}
>> Enabled:
>> Start Time: 2015-05-12 15:55:06
>> Next Run Time: 2015-05-12 15:55:06
>> Stop Time: None
>> Repeats: 0 0=unlimited
>> Retry Failed: -1 -1=unlimited
>> Period: 600 seconds
>> Prevent Drift: False
>> Timeout: 30 seconds
>> Sync Output: 0
>> Times Run: 0
>> Times Failed: 0
>> Assigned Worker Name:
>>
>> I can see that the workers are created on the scheduler_worker table, but
>> tasks are never picked up.
>> I'm in production, using uwsgi + nginx. Already restarted uwsgi
>> application.
>>
>> El martes, 12 de mayo de 2015, 16:50:43 (UTC-3), Niphlod escribió:
>>>
>>> seems that there aren't any tasks in the database the scheduler is
>>> looking in. Sure that there are no misconfigurations ?
>>>
>>> BTW: there's nothing wrong with your approach. A worker needs a "-K"
>>> argument only to inherit initialization options from that app: it's
>>> perfectly capable of processing tasks coming from different apps (of course
>>> they must exist in the server where the worker is running)
>>>
>>
--
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.
