Olen Vance Sluder Jr wrote: > Problem solved: I found this stack trace in the job runner's log: > > Traceback (most recent call last): > File "./scripts/paster.py", line 34, in <module> > command.run() > File > "/home/galaxy/galaxy-dist/eggs/PasteScript-1.7.3-py2.6.egg/paste/script/command.py", > line 84, in run > invoke(command, command_name, options, args[1:]) > File > "/home/galaxy/galaxy-dist/eggs/PasteScript-1.7.3-py2.6.egg/paste/script/command.py", > line 123, in invoke > exit_code = runner.run(args) > File > "/home/galaxy/galaxy-dist/eggs/PasteScript-1.7.3-py2.6.egg/paste/script/command.py", > line 218, in run > result = self.command() > File > "/home/galaxy/galaxy-dist/eggs/PasteScript-1.7.3-py2.6.egg/paste/script/serve.py", > line 303, in command > serve() > File > "/home/galaxy/galaxy-dist/eggs/PasteScript-1.7.3-py2.6.egg/paste/script/serve.py", > line 287, in serve > server(app) > File > "/home/galaxy/galaxy-dist/eggs/PasteDeploy-1.3.3-py2.6.egg/paste/deploy/loadwsgi.py", > line 151, in server_wrapper > **context.local_conf) > File > "/home/galaxy/galaxy-dist/eggs/PasteDeploy-1.3.3-py2.6.egg/paste/deploy/util/fixtypeerror.py", > line 57, in fix_call > val = callable(*args, **kw) > File > "/home/galaxy/galaxy-dist/eggs/Paste-1.6-py2.6.egg/paste/httpserver.py", > line 1314, in server_runner > serve(wsgi_app, **kwargs) > File > "/home/galaxy/galaxy-dist/eggs/Paste-1.6-py2.6.egg/paste/httpserver.py", > line 1264, in serve > threadpool_options=threadpool_options) > File > "/home/galaxy/galaxy-dist/eggs/Paste-1.6-py2.6.egg/paste/httpserver.py", > line 1118, in __init__ > **threadpool_options) > File > "/home/galaxy/galaxy-dist/eggs/Paste-1.6-py2.6.egg/paste/httpserver.py", > line 1024, in __init__ > **threadpool_options) > File > "/home/galaxy/galaxy-dist/eggs/Paste-1.6-py2.6.egg/paste/httpserver.py", > line 588, in __init__ > % (spawn_if_under, nworkers)) > AssertionError: spawn_if_under (5) should be less than nworkers (3) > > Per the Scaling and Load Balancing instructions [1], I had used the > following stanza for the job runner: > > [server:runner0] > use = egg:Paste#http > port = 8079 > #host = 127.0.0.1 > use_threadpool = true > threadpool_workers = 3 > > The value for threadpool_workers (3) conflicted with the default value > for local_job_queue_workers (5). When I increased the value of > threadpool_workers to 5, the runner's web interface came right up.
Hi Olen, Thanks for finding this! I've increased the value in the documentation to 5. --nate > > -- > Olen > > [1] > <https://bitbucket.org/galaxy/galaxy-central/wiki/Config/WebApplicationScaling> > > > On Mon, May 23, 2011 at 08:53, Olen Vance Sluder Jr <o...@acm.org> wrote: > > I have had good success in setting up a load balanced configuration > > with nginx except that I get the following error when accessing Admin > > -> Manage jobs: > > > > "This Galaxy instance is not configured to run jobs. If using multiple > > servers, please directly access the job running instance to manage > > jobs." > > > > When I access the runner instance directly at > > <http://localhost:8079/admin/jobs>, the browser just hangs with no > > response. A quick search of the wiki and the dev mailing list archive > > didn't turn up a solution, so any help would be appreciated. > > > > Thanks, > > Olen > > > ___________________________________________________________ > Please keep all replies on the list by using "reply all" > in your mail client. To manage your subscriptions to this > and other Galaxy lists, please use the interface at: > > http://lists.bx.psu.edu/ ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
