On Wed, Jan 15, 2014 at 11:30 AM, Briand, Sheldon
<sheldon.bri...@ssc-spc.gc.ca> wrote:
> Hi John,
>
> Thanks for getting back to me.
>
> My use_remote_user is set to false.  Yes nginx is setup as you suggest.  My 
> proxy setup worked before I updated.  I have already tested talking to galaxy 
> directly and the problem remains.  I meant to mention that in my first 
> message.  I tried putting use_pbkdf2 in my configuration file and the galaxy 
> server will not start.
>
> I noticed there is activation code for user accounts in the new the 
> universe_wsgi.ini file.  Could this be buggy?

Have you enabled the activation stuff - is user_activation_on set in
universe_wsgi.ini?

What database are you using.

When you added "use_pbkdf2=False" to the configuration file - did you
add it to the app:main section?

-John

>
> Thanks,
> -Sheldon
>
> -----Original Message-----
> From: jmchil...@gmail.com [mailto:jmchil...@gmail.com] On Behalf Of John 
> Chilton
> Sent: Wednesday, January 15, 2014 11:50 AM
> To: Briand, Sheldon
> Subject: Re: [galaxy-dev] after update unable to login
>
> This is unfortunate, sorry about the problems.
>
> There were some changes to the authentication stuff as part of that update - 
> but this is the first report of problems I think. Just to understand your 
> setup - Galaxy is doing the authentication right - ( use_remote_user is not 
> set to true in your universe_wsgi.ini )?
>
> So likely your nginx is setup to proxy requests say from port 80 to
> 8080 or something like that? Did you configure this? The one thing I would 
> try is to talk to Galaxy directly by pointing your web browser at port 
> localhost:8080 or whatever (you may need to setup SSH tunnels if this is a 
> remote server and not your desktop). I would like to be sure this is a 
> problem with Galaxy and not the nginx configuration - this would confirm that.
>
> If it works to talk to Galaxy directly, somehow your proxy is misconfigured I 
> think - not sure how to resolve that but it would be good to know. Otherwise 
> the problem is with Galaxy's configuration - again not sure how to resolve 
> that but it would be good to know. In this second case, the next I would try 
> is setting use_pbkdf2 to False in universe_wsgi.ini restart and see if you an 
> login then - this shouldn't matter but this problem shouldn't be occurring at 
> all :(.
>
> Let me know if you make any progress.
>
> -John
>
>
> On Tue, Jan 14, 2014 at 12:20 PM, Briand, Sheldon 
> <sheldon.bri...@ssc-spc.gc.ca> wrote:
>> Hi,
>>
>>
>>
>> I've tried reinstalling from scratch in case there was a problem when
>> I updated the last time.  I am still having trouble logging in.  The
>> "broken pipe"  error message has nothing to do with the failed logins.
>>
>>
>>
>> The logins are successful as far as authentication goes ( I get no
>> error message, if I put in the wrong password I do get an error message ).
>> However, after login the user is redirected to the last page they were
>> on and does not appear to be logged in (no history, clicking on user
>> gives the login or register options).
>>
>>
>>
>> If I sent logins so that anonymous logins are not allowed I always get
>> sent back to the login page.
>>
>>
>>
>> I've looked through the archives for a similar problem and not found
>> anything relevant.  I've tried using the stable version of the latest
>> build as well as the development version.  No joy on either.
>>
>>
>>
>> Is there something I've missed?
>>
>>
>>
>> Thanks,
>>
>> -Sheldon
>>
>>
>>
>>
>>
>>
>>
>> From: Briand, Sheldon
>> Sent: Thursday, January 09, 2014 2:26 PM
>> To: 'galaxy-dev@lists.bx.psu.edu'
>> Subject: after update unable to login
>>
>>
>>
>> Hi,
>>
>>
>>
>> I had a working local install of galaxy.  I wanted to install gatk2
>> and wasn't able to install it.  I upgraded and I am now unable to log
>> in to galaxy.
>>
>>
>>
>> I should note that I am relatively new to galaxy.  I had a previously
>> logged in admin session (before the update).  So I am able to see that
>> galaxy (after the update) believes, by checking the manage users admin
>> page, I have newly logged in on another browser.  The session,
>> however, shows no indication that I am logged in other than not showing an 
>> error.  Usually I
>> end up back at the last page I was viewing before I logged in.   Clicking on
>> user doesn't show me as logged in, I have no history, and there is no
>> admin tab.
>>
>>
>>
>> I have a nginx proxy setup.
>>
>>
>>
>> Paster.log shows a "Broken pipe" error when I login from nginx.   I show no
>> error when I log in directly via the galaxy server.  The results are
>> the same.  I upgraded from database version 115 to version 117.
>>
>>
>>
>> Is there an easy fix?
>>
>>
>>
>> Thanks,
>>
>> -Sheldon
>>
>>
>>
>> Sheldon Briand
>>
>> NRC Research Computing Support Analyst
>>
>> Research Computing Support / Soutien Informartique a la Recherche
>>
>> Operations, Science Portfolio / Operations, Portefeuil des sciences
>>
>> SSC-NRC / SPC-CNRC
>>
>> Rm 329A, 1411 Oxford Street / Piece 329A, 1411 Rue Oxford
>>
>> Halifax, NS  B3H 3Z1
>>
>> 902 426-1677
>>
>> sheldon.bri...@ssc-spc.gc.ca
>>
>>
>>
>>
>> ___________________________________________________________
>> 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/
>>
>> To search Galaxy mailing lists use the unified search at:
>>   http://galaxyproject.org/search/mailinglists/

___________________________________________________________
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/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/

Reply via email to