Hi Nate,
I was able to finally track down the login issue. It had to do with the following setting in my universe_wsgi.ini: * * *cookie_path = /galaxy*
Removing this out fixed the problem and I should be fine leaving it out out since I don't need to run more than one instance of Galaxy. I probably shouldn't have had this setting in the first place, though I'm not exactly sure what this caused the problem.
Anyways, thanks for all the help tracking these issues down.
-Matt
On Mon, May 16, 2011 at 5:26 PM, Matthew Conte mconte@umd.edu wrote:
Yep. On May 16, 2011 7:14 AM, "Nate Coraor" nate@bx.psu.edu wrote:
Matthew Conte wrote:
On Fri, May 13, 2011 at 11:18 AM, Nate Coraor nate@bx.psu.edu wrote:
That's correct, although it should've been fixed. Can you remove the contents of galaxy-dist/database/compiled_templates, clear cache, reload, and see if you still get the same results?
Thanks, --nate
I've removed the contents of that folder, cleared the browser cache, reloaded and still get the same results (nothing different in the log either).
I'm not sure if this will help, but maybe I should mention that when I
try
to log in I do get the following screen to flash for a brief second
before
automatically taking me back to the welcome screen:
[image: Screen shot 2011-05-13 at 1.44.25 PM.png]
I'm going to try to set up a test environment to replicate this shortly. Does this happen with both Apache and nginx?
--nate
Matthew Conte wrote:
Hi Nate,
I was able to finally track down the login issue. It had to do with the following setting in my universe_wsgi.ini:
*cookie_path = /galaxy*
Removing this out fixed the problem and I should be fine leaving it out out since I don't need to run more than one instance of Galaxy. I probably shouldn't have had this setting in the first place, though I'm not exactly sure what this caused the problem.
Anyways, thanks for all the help tracking these issues down.
Hi Matt,
I was about to get back to this now that the conference is over and I was also wondering if that option was related - weird though, I'm not sure why it should have an effect, but I'm glad you've figured out what's up. I guess there's a bug with the cookie path I'll need to check out.
--nate
-Matt
On Mon, May 16, 2011 at 5:26 PM, Matthew Conte mconte@umd.edu wrote:
Yep. On May 16, 2011 7:14 AM, "Nate Coraor" nate@bx.psu.edu wrote:
Matthew Conte wrote:
On Fri, May 13, 2011 at 11:18 AM, Nate Coraor nate@bx.psu.edu wrote:
That's correct, although it should've been fixed. Can you remove the contents of galaxy-dist/database/compiled_templates, clear cache, reload, and see if you still get the same results?
Thanks, --nate
I've removed the contents of that folder, cleared the browser cache, reloaded and still get the same results (nothing different in the log either).
I'm not sure if this will help, but maybe I should mention that when I
try
to log in I do get the following screen to flash for a brief second
before
automatically taking me back to the welcome screen:
[image: Screen shot 2011-05-13 at 1.44.25 PM.png]
I'm going to try to set up a test environment to replicate this shortly. Does this happen with both Apache and nginx?
--nate
Nate Coraor wrote:
Matthew Conte wrote:
Hi Nate,
I was able to finally track down the login issue. It had to do with the following setting in my universe_wsgi.ini:
*cookie_path = /galaxy*
Removing this out fixed the problem and I should be fine leaving it out out since I don't need to run more than one instance of Galaxy. I probably shouldn't have had this setting in the first place, though I'm not exactly sure what this caused the problem.
Anyways, thanks for all the help tracking these issues down.
Hi Matt,
I was about to get back to this now that the conference is over and I was also wondering if that option was related - weird though, I'm not sure why it should have an effect, but I'm glad you've figured out what's up. I guess there's a bug with the cookie path I'll need to check out.
Okay, in testing I can only get this to happen if the browser has two cookies - one with the correct proxied path set and another set using just '/'. This arises from something like a bug in the library Galaxy uses to handle the request (WebOb) and the fact that the cookie headers don't include the cookie path along with the contents, so we'd have to choose one cookie or the other to use as your current session (probably the newer of the two?).
Since this should really only happen in the case of a user getting a Galaxy cookie while running with cookie_path unset and then another once it's been set, it should be pretty rare and easily worked around by clearing cookies.
If you're still interested in testing this and find that clearing cookies still doesn't fix the issue, please let me know.
Thanks, --nate
--nate
-Matt
On Mon, May 16, 2011 at 5:26 PM, Matthew Conte mconte@umd.edu wrote:
Yep. On May 16, 2011 7:14 AM, "Nate Coraor" nate@bx.psu.edu wrote:
Matthew Conte wrote:
On Fri, May 13, 2011 at 11:18 AM, Nate Coraor nate@bx.psu.edu wrote:
That's correct, although it should've been fixed. Can you remove the contents of galaxy-dist/database/compiled_templates, clear cache, reload, and see if you still get the same results?
Thanks, --nate
I've removed the contents of that folder, cleared the browser cache, reloaded and still get the same results (nothing different in the log either).
I'm not sure if this will help, but maybe I should mention that when I
try
to log in I do get the following screen to flash for a brief second
before
automatically taking me back to the welcome screen:
[image: Screen shot 2011-05-13 at 1.44.25 PM.png]
I'm going to try to set up a test environment to replicate this shortly. Does this happen with both Apache and nginx?
--nate
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:
galaxy-dev@lists.galaxyproject.org
-
Matthew Conte -
Nate Coraor