Agreed on the first point. Here the tasks are not getting assigned because I am calling the queue_task from the controller. I believe the controller function 'index' didn't not load as app cannot be opened in the browser.
And the second point, yes the web2py version is a bit old, I had a little fear if I update the app midway. Well I will update it tonight . On Wednesday, 11 September 2013 20:16:46 UTC+5:30, Niphlod wrote: > > so, the scheduler is working pretty fine: it just doesn't find any task to > process. > > PS: you are on a really old release (2.2.1). That's almost a year ago! > > On Wednesday, September 11, 2013 4:23:07 PM UTC+2, ajith c t wrote: >> >> ubuntu@ip-10-0-0-13:/srv/trustvouch-fe$ sudo python web2py.py -K app -D 0 >> 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) >> >> >> >> >> 2013-09-11 14:21:20,236 - DEBUG - web2py.scheduler - defining tables >> (migrate=True) >> 2013-09-11 14:21:20,242 - DEBUG - web2py.scheduler - looping... >> 2013-09-11 14:21:20,246 - DEBUG - web2py.scheduler - nothing to do >> 2013-09-11 14:21:20,246 - DEBUG - web2py.scheduler - sleeping... >> 2013-09-11 14:21:20,246 - DEBUG - web2py.scheduler - thread building own >> DAL object >> 2013-09-11 14:21:20,249 - DEBUG - web2py.scheduler - defining tables >> (migrate=False) >> 2013-09-11 14:21:20,254 - DEBUG - web2py.scheduler - freeing workers >> that have not sent heartbeat >> 2013-09-11 14:21:23,249 - DEBUG - web2py.scheduler - looping... >> 2013-09-11 14:21:23,254 - DEBUG - web2py.scheduler - nothing to do >> 2013-09-11 14:21:23,254 - DEBUG - web2py.scheduler - sleeping... >> 2013-09-11 14:21:23,263 - DEBUG - web2py.scheduler - ........recording >> heartbeat >> 2013-09-11 14:21:26,257 - DEBUG - web2py.scheduler - looping... >> 2013-09-11 14:21:26,261 - DEBUG - web2py.scheduler - nothing to do >> 2013-09-11 14:21:26,262 - DEBUG - web2py.scheduler - sleeping... >> 2013-09-11 14:21:26,270 - DEBUG - web2py.scheduler - ........recording >> heartbeat >> 2013-09-11 14:21:29,265 - DEBUG - web2py.scheduler - looping... >> 2013-09-11 14:21:29,269 - DEBUG - web2py.scheduler - nothing to do >> 2013-09-11 14:21:29,269 - DEBUG - web2py.scheduler - sleeping... >> 2013-09-11 14:21:29,277 - DEBUG - web2py.scheduler - ........recording >> heartbeat >> >> >> above the out put of the log, >> >> On Wednesday, 11 September 2013 19:48:06 UTC+5:30, Niphlod wrote: >>> >>> let's solve an issue at a time. If your scheduler can't process the >>> tasks that are in the queue when you launch it from the console, something >>> is wrong with it and there's nothing that upstart can "fix". >>> If you launch your scheduler from the console with >>> web2py.py -K yourappname -D 0 >>> what is the result ? >>> >> -- 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.
