I was running a single instance of galaxy on my own machine, playing with library_import and figuring why BAM files were getting errors on upload. (It is a path matter, when one drops into the subshell and the workaround is ln -s /usr/bin/samtools /home/galaxy/bin/samtools ) Anyway, I seemed to have it figured last eve so I shut down the notebook where galaxy was running (on RHEL6) and went home. This am when I started galaxy with sh run.sh I got some messages about egg,ini and replacing universe_wsgi. files from universe_wsgi.sample. files and nothing worked. My registration was gone. My admin_user was overwritten. I re-registered, and restored the file settings and restarted galaxy, but now no login sticks. It does not complain about a registered user, but it does not appear to hold the session--the user tab does not show me as logged in. Is there some different way it is handling cookies? Michael Moore
On Wed, Apr 25, 2012 at 12:56 PM, Michael Moore <michaelglennmoore@gmail.com> wrote:
My registration was gone. My admin_user was overwritten. I re-registered, and restored the file settings and restarted galaxy, but now no login sticks. It does not complain about a registered user, but it does not appear to hold the session--the user tab does not show me as logged in. Is there some different way it is handling cookies?
Hi Michael, I don't know exactly what happened to your local Galaxy install, universe_wsgi.ini shouldn't get overwritten after a simple restart not even after an update with 'hg pull -u'. In any case, for your login problem after re-registering, remove the cookies for the IP of your Galaxy server. This always works for me. Regards, Carlos
participants (2)
-
Carlos Borroto
-
Michael Moore