Hi all,
I have a similar, maybe related problem. I'm running a configuration as
described at
http://wiki.g2.bx.psu.edu/Admin/Config/Performance/Web%20Application%20Scaling.
I have three webservers, one manager and two handlers. Everything is
behind an Apache and the rewrite rules are set accordingly.
When I try to access "Manage Jobs", I also get the error "This Galaxy
instance is not the job manager. If using multiple servers, please
directly access the job manager instance to manage jobs.". I have set
the rewrite rule for admin/jobs to point to the manager server. When I
access the manager directly from localhost I get the same error, while
all other servers (web and handler) throw a server error:
127.0.0.1 - - [24/May/2012:15:37:50 +0200] "GET /admin/jobs HTTP/1.1"
500 - "-" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20120424
Firefox/10.0.4"
Error - <type 'exceptions.AttributeError'>: 'NoopQueue' object has no
attribute 'job_lock'
URL: http://localhost:8080/admin/jobs
File
'/galaxy/galaxy_server/eggs/Paste-1.6-py2.7.egg/paste/exceptions/errormiddleware.py',
line 143 in __call__
app_iter = self.application(environ, start_response)
File
'/galaxy/galaxy_server/eggs/Paste-1.6-py2.7.egg/paste/recursive.py',
line 80 in __call__
return self.application(environ, start_response)
File
'/galaxy/galaxy_server/eggs/Paste-1.6-py2.7.egg/paste/httpexceptions.py', line
632 in __call__
return self.application(environ, start_response)
File '/galaxy/galaxy_server/lib/galaxy/web/framework/base.py', line 160
in __call__
body = method( trans, **kwargs )
File '/galaxy/galaxy_server/lib/galaxy/web/framework/__init__.py', line
184 in decorator
return func( self, trans, *args, **kwargs )
File '/galaxy/galaxy_server/lib/galaxy/web/base/controller.py', line
2428 in jobs
job_lock = trans.app.job_manager.job_queue.job_lock )
AttributeError: 'NoopQueue' object has no attribute 'job_lock'
Before the update everything worked fine (I also ran multiple servers then).
Best regards,
Sarah
On 05/16/2012 10:27 PM, Dave Lin wrote:
Dear Galaxy Team,
I've been getting the following error for some time when I try to
access the Manage Jobs Task.
"This Galaxy instance is not the job manager. If using multiple
servers, please directly access the job manager instance to manage jobs."
For debugging purposes, I'm only running the single master instance.
I'm using CloudMan/Amazon EC2.
I traced the code and suspect it might have something to do with an
Amazon IP Address/hostname discrepancy, but am not sure how to go
about fixing this.
On a related note, if I can't access this page, what is the best way
to clear/cancel jobs via the command line?
Thanks in advance,
Dave
Thanks,
Dave
___________________________________________________________
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/
