There is an installation of Galaxy on a server cluster instance. I am unable to login or create a new history. I'm not sure what could be causing this. Presumably some Python object was not created somewhere, causing some history operations to fail.
From main.log, I see this stack trace:
galaxy.web.framework ERROR 2014-08-04 15:32:24,952 Uncaught exception in exposed API method: Traceback (most recent call last): File "/home/galaxygalaxy-dist/lib/galaxy/web/framework/__init__.py", line 331, in decorator rval = func( self, trans, *args, **kwargs) File "/home/galaxy/galaxy-dist/lib/galaxy/webapps/galaxy/api/histories.py", line 110, in show history = trans.get_history( create=True ) File "/home/galaxy/galaxy-dist/lib/galaxy/web/framework/__init__.py", line 1017, in get_history history = self.new_history() File "/home/galaxy/galaxy-dist/lib/galaxy/web/framework/__init__.py", line 1073, in new_history self.galaxy_session.current_history = history AttributeError: 'NoneType' object has no attribute 'current_history'
From the web UI:
user
quota_percent |
null |
nice_total_disk_usage |
0 bytes |
total_disk_usage |
0 |
id |
null |
username |
(anonymous user) |
|
|
is_admin |
false |
sourceCurrentHistoryPanel()xhr
readyState |
4 |
||||||||||||
responseText |
{"err_msg": "Uncaught exception in exposed API method:", "err_code": 0} |
||||||||||||
responseJSON |
|
||||||||||||
status |
500 |
||||||||||||
statusText |
Internal Server Error |
||||||||||||
responseHeaders |
|
options historyIdcurrenthistory
I would appreciate if someone can give me some insight about how to fix this. Thanks!
What browser are you using? Any javascript errors in the web console?
And what does your server configuration look like? Are you talking directly to the galaxy server, or is there a proxy in the mix somewhere?
It looks like your session isn't being established or isn't persistent.
Checking the console in Chrome, I don't see any errors.
There is a proxy set up. From the universe.wsgi:
The dots are ellipses indicating other text in between.
To cut potential issues out of the loop, can you try connecting to the galaxy server directly (bypassing the proxy) with a browser and see if you can log in?
I have tried connected directly. Same problem it seems.