When I start directly from the web2py folder, my load balancer gives me a 
bad gateway error. When I run the web2py shell , I see the scheduler tables 
are created. 

ubuntu@ip-10-0-0-13:/srv/tv-fe$ sudo python web2py.py -K app
web2py Web Framework
Created by Massimo Di Pierro, Copyright 2007-2013
Version 2.2.1 (2012-10-21 16:57:04) stable
Database drivers available: SQLite(sqlite3), MySQL(pymysql), 
PostgreSQL(pg8000), IMAP(imaplib)
starting single-scheduler for "app"...
/usr/local/lib/python2.7/dist-packages/riak-2.0.1.post5-py2.7.egg/riak/util.py:148:
 
UserWarning: ``solr`` is deprecated, use ``fulltext_search``, 
``fulltext_add`` and ``fulltext_delete`` directly
  value = self.fget(obj)



The scheduler_worker has record

<Row {'status': 'ACTIVE', 'first_heartbeat': datetime.datetime(2013, 9, 11, 
13, 45, 18), 'is_ticker': False, 'worker_name': 'ip-10-0-0-13#13064', 
'group_names': ['main'], 'last_heartbeat': datetime.datetime(2013, 9, 11, 
13, 45, 45), 'id': 1}>


But other tables are empty as expected for me.

My apps workflow is as follows, I dont understand if that is creating the 
problem,

I have a load balancer at a public ip, which has the nginx that acts as a 
reverse proxy for the  frontend server. The web2py folder is in this server 
and the models folder contains a scheduler.py file in which the tasks are 
defined and the scheduler class is called. Now in the controller 
default.py, index function calls the scheduler.queue_task. 

Since I started it from the web2py folder and it resulted in a bad gateway, 
the index function could not be called so the tasks is not scheduled.

But when I am using with upstart, there is no bad gateway error, everything 
goes fine except that the tasks in the  scheduler_task is not assigned a 
worker.


On Wednesday, 11 September 2013 19:03:19 UTC+5:30, Niphlod wrote:
>
> and when you start it without using upstart it works or not ?
>
> On Wednesday, September 11, 2013 2:22:32 PM UTC+2, ajith c t wrote:
>>
>> Sorry missed the issue, the issue is the task just doesnt get called up. 
>> I believe the scheduler_task will have the worker that picked up the task 
>> in the assigned_worker_name field. In my case it remains empty
>>
>> On Wednesday, 11 September 2013 17:45:11 UTC+5:30, Niphlod wrote:
>>>
>>> what you posted doesn't indicate any issues. The task is there and the 
>>> worker too.
>>> What are you experiencing instead ?
>>>
>>>

-- 
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/groups/opt_out.

Reply via email to