Re: "You are not logged in (HTTP 401, API Error 103)"

[Christian Hammond]

Ahh, that would do it, indeed. Sorry, I didn't check for that.

Christian

On Tue, Jan 16, 2018 at 11:14 AM, Vince Thyng  wrote:

> I think this all came down to not having 'WSGIPassAuthorization On' in my
> apache config.
>
> Vince
>
>
> On Tuesday, January 16, 2018 at 8:56:54 AM UTC-8, Vince Thyng wrote:
>>
>> Hello Christian,
>>
>>I was hoping that would be it, but I get the same problem.  I am
>> pretty sure my apache config is the problem.  I replaced my apache
>> customizations with the /var/www/reviewboard/conf/apache-wsgi.conf file
>> and it wrote the session to the .rbtools-cookies file.  Still errored, but
>> it was about ssl which isn't included in that basic file.  So I think I am
>> on the right track.
>>
>> Thank you very much for your help!
>>
>> Vince
>>
>>
>> On Monday, January 15, 2018 at 7:58:40 PM UTC-8, Christian Hammond wrote:
>>>
>>> Hi Vince,
>>>
>>> The debug log shows an immediate failure after providing a
>>> login/password, and it's not the one I'd expect if there was an issue with
>>> the credentials (you'd see "The username or password was not correct."),
>>> which makes me wonder if there's an issue with the credentials even
>>> reaching the server.
>>>
>>> I've seen this happen when going through an outbound HTTP(S) proxy for a
>>> company. If the company has one set up at all, and your system is
>>> configured to go through it, then it's likely going to interfere with the
>>> requests. Just to sanity-check, can you try passing --no-proxy to RBTools
>>> in your test?
>>>
>>> LDAP errors will show up as warnings/errors, without the need to enable
>>> debug logging. You should see a debug message for "Attempting to
>>> authenticate user ..."
>>>
>>> If you aren't seeing anything from LDAP, then it sounds like it's not
>>> going through LDAP. Can you confirm LDAP is showing up as the auth backend
>>> in Authentication Settings?
>>>
>>> Christian
>>>
>>> On Mon, Jan 15, 2018 at 3:34 PM, Vince Thyng  wrote:
>>>

 Confirmed, the domain matches exactly.

 We have restarted apache many times while troubleshooting this, but
 tried a restart again just now.  We wanted to try `sudo python -m ipdb
 $(which rb-site) manage /var/www/reviewboard runserver 0.0.0.0:80`,
 but ran in to trouble with https not being available.

 Sorry, that .rbtools-cookies file post was confusing.  It shows our
 production server in there as otherserver.com (which I can still post
 to just fine even after removing the session for it from .rbtools-cookies),
 and this new one that will replace it as localserver.com.  I think
 what is noteable about my testing is that when I remove the cookies file,
 it is not getting populated again, yet if I put a session in there manually
 that I can see in the database, it works.

 Logins via webui work, while new sessions via rbt do not.

 We are using apache 2.4.6 without a proxy in front, on centos 7.3

 I think it is a pretty basic config, but I removed the 80->443 redirect
 and tested again just now in case that has introduced a problem.  Still no
 love.

 
   ServerName reviewboard.localserver.com

   ## Vhost docroot
   DocumentRoot "/var/www/reviewboard/"
   ## Alias declarations for resources outside the DocumentRoot
   Alias /static "/var/www/reviewboard/htdocs/static"

   ## Directories, there should at least be a declaration for
 /var/www/reviewboard/

   
 Options -Indexes +FollowSymLinks
 AllowOverride None
 Require all granted
   

   ## Logging
   ErrorLog "/var/log/httpd/reviewboard.localserver.com_error_ssl.log"
   ServerSignature Off
   CustomLog "/var/log/httpd/reviewboard.localserver.com_access_ssl.log"
 combined

   ## SSL directives
   SSLEngine on
   SSLCertificateFile  "/etc/pki/tls/certs/_.west.isilon.com.crt"
   SSLCertificateKeyFile   "/etc/pki/tls/private/_.west.isilon.com.key"
   SSLCertificateChainFile "/etc/pki/tls/certs/_.west.isi
 lon.com.chain.crt"
   SSLCACertificatePath"/etc/pki/tls/certs"
   WSGIScriptAlias / "/var/www/reviewboard/htdocs/reviewboard.wsgi"
 


 Something else I have noticed is that even with reviewboard in debug
 mode (set in System Settings->Logging log level = DEBUG, I don't see
 anything in the reviewboard.log file except
 2018-01-15 20:05:00,809 - INFO -  - root - Reloading logging settings
 Is there a way to get it to report ldap failures there?

 Vince


 On Monday, January 15, 2018 at 2:59:23 PM UTC-8, Christian Hammond
 wrote:
>
> Hi Vince,
>
> Is Review Board configured to use the same domain in General Settings
> as you have specified in .reviewboardrc? Can you confirm that for me, and
> also confirm that restarting Apache doesn't fix anything? I'm wondering

Re: "You are not logged in (HTTP 401, API Error 103)"

[Vince Thyng]

I think this all came down to not having 'WSGIPassAuthorization On' in my 
apache config.

Vince

On Tuesday, January 16, 2018 at 8:56:54 AM UTC-8, Vince Thyng wrote:
>
> Hello Christian,
>
>I was hoping that would be it, but I get the same problem.  I am pretty 
> sure my apache config is the problem.  I replaced my apache customizations 
> with the /var/www/reviewboard/conf/apache-wsgi.conf file and it wrote the 
> session to the .rbtools-cookies file.  Still errored, but it was about ssl 
> which isn't included in that basic file.  So I think I am on the right 
> track.
>
> Thank you very much for your help!
>
> Vince
>
>
> On Monday, January 15, 2018 at 7:58:40 PM UTC-8, Christian Hammond wrote:
>>
>> Hi Vince,
>>
>> The debug log shows an immediate failure after providing a 
>> login/password, and it's not the one I'd expect if there was an issue with 
>> the credentials (you'd see "The username or password was not correct."), 
>> which makes me wonder if there's an issue with the credentials even 
>> reaching the server.
>>
>> I've seen this happen when going through an outbound HTTP(S) proxy for a 
>> company. If the company has one set up at all, and your system is 
>> configured to go through it, then it's likely going to interfere with the 
>> requests. Just to sanity-check, can you try passing --no-proxy to RBTools 
>> in your test?
>>
>> LDAP errors will show up as warnings/errors, without the need to enable 
>> debug logging. You should see a debug message for "Attempting to 
>> authenticate user ..."
>>
>> If you aren't seeing anything from LDAP, then it sounds like it's not 
>> going through LDAP. Can you confirm LDAP is showing up as the auth backend 
>> in Authentication Settings?
>>
>> Christian
>>
>> On Mon, Jan 15, 2018 at 3:34 PM, Vince Thyng  wrote:
>>
>>>
>>> Confirmed, the domain matches exactly.
>>>
>>> We have restarted apache many times while troubleshooting this, but 
>>> tried a restart again just now.  We wanted to try `sudo python -m ipdb 
>>> $(which rb-site) manage /var/www/reviewboard runserver 0.0.0.0:80`, but ran 
>>> in to trouble with https not being available.
>>>
>>> Sorry, that .rbtools-cookies file post was confusing.  It shows our 
>>> production server in there as otherserver.com (which I can still post 
>>> to just fine even after removing the session for it from .rbtools-cookies), 
>>> and this new one that will replace it as localserver.com.  I think what 
>>> is noteable about my testing is that when I remove the cookies file, it is 
>>> not getting populated again, yet if I put a session in there manually that 
>>> I can see in the database, it works.
>>>
>>> Logins via webui work, while new sessions via rbt do not.
>>>
>>> We are using apache 2.4.6 without a proxy in front, on centos 7.3
>>>
>>> I think it is a pretty basic config, but I removed the 80->443 redirect 
>>> and tested again just now in case that has introduced a problem.  Still no 
>>> love.
>>>
>>> 
>>>   ServerName reviewboard.localserver.com
>>>
>>>   ## Vhost docroot
>>>   DocumentRoot "/var/www/reviewboard/"
>>>   ## Alias declarations for resources outside the DocumentRoot
>>>   Alias /static "/var/www/reviewboard/htdocs/static"
>>>
>>>   ## Directories, there should at least be a declaration for 
>>> /var/www/reviewboard/
>>>
>>>   
>>> Options -Indexes +FollowSymLinks
>>> AllowOverride None
>>> Require all granted
>>>   
>>>
>>>   ## Logging
>>>   ErrorLog "/var/log/httpd/reviewboard.localserver.com_error_ssl.log"
>>>   ServerSignature Off
>>>   CustomLog "/var/log/httpd/reviewboard.localserver.com_access_ssl.log" 
>>> combined
>>>
>>>   ## SSL directives
>>>   SSLEngine on
>>>   SSLCertificateFile  "/etc/pki/tls/certs/_.west.isilon.com.crt"
>>>   SSLCertificateKeyFile   "/etc/pki/tls/private/_.west.isilon.com.key"
>>>   SSLCertificateChainFile 
>>> "/etc/pki/tls/certs/_.west.isilon.com.chain.crt"
>>>   SSLCACertificatePath"/etc/pki/tls/certs"
>>>   WSGIScriptAlias / "/var/www/reviewboard/htdocs/reviewboard.wsgi"
>>> 
>>>
>>>
>>> Something else I have noticed is that even with reviewboard in debug 
>>> mode (set in System Settings->Logging log level = DEBUG, I don't see 
>>> anything in the reviewboard.log file except 
>>> 2018-01-15 20:05:00,809 - INFO -  - root - Reloading logging settings
>>> Is there a way to get it to report ldap failures there?
>>>
>>> Vince
>>>
>>>
>>> On Monday, January 15, 2018 at 2:59:23 PM UTC-8, Christian Hammond wrote:

 Hi Vince,

 Is Review Board configured to use the same domain in General Settings 
 as you have specified in .reviewboardrc? Can you confirm that for me, and 
 also confirm that restarting Apache doesn't fix anything? I'm wondering 
 because it sounds like the cookie is being generated for the wrong domain, 
 which would mean that upon initial authentication, you're getting a cookie 
 and then trying to use it again for the wrong server. Since the RBTools 
 

Re: "You are not logged in (HTTP 401, API Error 103)"

[Vince Thyng]

Hello Christian,

   I was hoping that would be it, but I get the same problem.  I am pretty 
sure my apache config is the problem.  I replaced my apache customizations 
with the /var/www/reviewboard/conf/apache-wsgi.conf file and it wrote the 
session to the .rbtools-cookies file.  Still errored, but it was about ssl 
which isn't included in that basic file.  So I think I am on the right 
track.

Thank you very much for your help!

Vince


On Monday, January 15, 2018 at 7:58:40 PM UTC-8, Christian Hammond wrote:
>
> Hi Vince,
>
> The debug log shows an immediate failure after providing a login/password, 
> and it's not the one I'd expect if there was an issue with the credentials 
> (you'd see "The username or password was not correct."), which makes me 
> wonder if there's an issue with the credentials even reaching the server.
>
> I've seen this happen when going through an outbound HTTP(S) proxy for a 
> company. If the company has one set up at all, and your system is 
> configured to go through it, then it's likely going to interfere with the 
> requests. Just to sanity-check, can you try passing --no-proxy to RBTools 
> in your test?
>
> LDAP errors will show up as warnings/errors, without the need to enable 
> debug logging. You should see a debug message for "Attempting to 
> authenticate user ..."
>
> If you aren't seeing anything from LDAP, then it sounds like it's not 
> going through LDAP. Can you confirm LDAP is showing up as the auth backend 
> in Authentication Settings?
>
> Christian
>
> On Mon, Jan 15, 2018 at 3:34 PM, Vince Thyng  > wrote:
>
>>
>> Confirmed, the domain matches exactly.
>>
>> We have restarted apache many times while troubleshooting this, but tried 
>> a restart again just now.  We wanted to try `sudo python -m ipdb $(which 
>> rb-site) manage /var/www/reviewboard runserver 0.0.0.0:80`, but ran in to 
>> trouble with https not being available.
>>
>> Sorry, that .rbtools-cookies file post was confusing.  It shows our 
>> production server in there as otherserver.com (which I can still post to 
>> just fine even after removing the session for it from .rbtools-cookies), 
>> and this new one that will replace it as localserver.com.  I think what 
>> is noteable about my testing is that when I remove the cookies file, it is 
>> not getting populated again, yet if I put a session in there manually that 
>> I can see in the database, it works.
>>
>> Logins via webui work, while new sessions via rbt do not.
>>
>> We are using apache 2.4.6 without a proxy in front, on centos 7.3
>>
>> I think it is a pretty basic config, but I removed the 80->443 redirect 
>> and tested again just now in case that has introduced a problem.  Still no 
>> love.
>>
>> 
>>   ServerName reviewboard.localserver.com
>>
>>   ## Vhost docroot
>>   DocumentRoot "/var/www/reviewboard/"
>>   ## Alias declarations for resources outside the DocumentRoot
>>   Alias /static "/var/www/reviewboard/htdocs/static"
>>
>>   ## Directories, there should at least be a declaration for 
>> /var/www/reviewboard/
>>
>>   
>> Options -Indexes +FollowSymLinks
>> AllowOverride None
>> Require all granted
>>   
>>
>>   ## Logging
>>   ErrorLog "/var/log/httpd/reviewboard.localserver.com_error_ssl.log"
>>   ServerSignature Off
>>   CustomLog "/var/log/httpd/reviewboard.localserver.com_access_ssl.log" 
>> combined
>>
>>   ## SSL directives
>>   SSLEngine on
>>   SSLCertificateFile  "/etc/pki/tls/certs/_.west.isilon.com.crt"
>>   SSLCertificateKeyFile   "/etc/pki/tls/private/_.west.isilon.com.key"
>>   SSLCertificateChainFile "/etc/pki/tls/certs/_.west.isilon.com.chain.crt"
>>   SSLCACertificatePath"/etc/pki/tls/certs"
>>   WSGIScriptAlias / "/var/www/reviewboard/htdocs/reviewboard.wsgi"
>> 
>>
>>
>> Something else I have noticed is that even with reviewboard in debug mode 
>> (set in System Settings->Logging log level = DEBUG, I don't see anything in 
>> the reviewboard.log file except 
>> 2018-01-15 20:05:00,809 - INFO -  - root - Reloading logging settings
>> Is there a way to get it to report ldap failures there?
>>
>> Vince
>>
>>
>> On Monday, January 15, 2018 at 2:59:23 PM UTC-8, Christian Hammond wrote:
>>>
>>> Hi Vince,
>>>
>>> Is Review Board configured to use the same domain in General Settings as 
>>> you have specified in .reviewboardrc? Can you confirm that for me, and also 
>>> confirm that restarting Apache doesn't fix anything? I'm wondering because 
>>> it sounds like the cookie is being generated for the wrong domain, which 
>>> would mean that upon initial authentication, you're getting a cookie and 
>>> then trying to use it again for the wrong server. Since the RBTools debug 
>>> output has been modified to mask the domain, I can't verify any of this 
>>> myself.
>>>
>>> What is your web server configuration like? Is Apache handling all 
>>> requests itself, or are you going through Nginx or another proxy?
>>>
>>> Christian
>>>
>>> On Mon, Jan 15, 2018 at 2:51 PM, Vince 

Re: "You are not logged in (HTTP 401, API Error 103)"

[Christian Hammond]

Hi Vince,

The debug log shows an immediate failure after providing a login/password,
and it's not the one I'd expect if there was an issue with the credentials
(you'd see "The username or password was not correct."), which makes me
wonder if there's an issue with the credentials even reaching the server.

I've seen this happen when going through an outbound HTTP(S) proxy for a
company. If the company has one set up at all, and your system is
configured to go through it, then it's likely going to interfere with the
requests. Just to sanity-check, can you try passing --no-proxy to RBTools
in your test?

LDAP errors will show up as warnings/errors, without the need to enable
debug logging. You should see a debug message for "Attempting to
authenticate user ..."

If you aren't seeing anything from LDAP, then it sounds like it's not going
through LDAP. Can you confirm LDAP is showing up as the auth backend in
Authentication Settings?

Christian

On Mon, Jan 15, 2018 at 3:34 PM, Vince Thyng  wrote:

>
> Confirmed, the domain matches exactly.
>
> We have restarted apache many times while troubleshooting this, but tried
> a restart again just now.  We wanted to try `sudo python -m ipdb $(which
> rb-site) manage /var/www/reviewboard runserver 0.0.0.0:80`, but ran in to
> trouble with https not being available.
>
> Sorry, that .rbtools-cookies file post was confusing.  It shows our
> production server in there as otherserver.com (which I can still post to
> just fine even after removing the session for it from .rbtools-cookies),
> and this new one that will replace it as localserver.com.  I think what
> is noteable about my testing is that when I remove the cookies file, it is
> not getting populated again, yet if I put a session in there manually that
> I can see in the database, it works.
>
> Logins via webui work, while new sessions via rbt do not.
>
> We are using apache 2.4.6 without a proxy in front, on centos 7.3
>
> I think it is a pretty basic config, but I removed the 80->443 redirect
> and tested again just now in case that has introduced a problem.  Still no
> love.
>
> 
>   ServerName reviewboard.localserver.com
>
>   ## Vhost docroot
>   DocumentRoot "/var/www/reviewboard/"
>   ## Alias declarations for resources outside the DocumentRoot
>   Alias /static "/var/www/reviewboard/htdocs/static"
>
>   ## Directories, there should at least be a declaration for
> /var/www/reviewboard/
>
>   
> Options -Indexes +FollowSymLinks
> AllowOverride None
> Require all granted
>   
>
>   ## Logging
>   ErrorLog "/var/log/httpd/reviewboard.localserver.com_error_ssl.log"
>   ServerSignature Off
>   CustomLog "/var/log/httpd/reviewboard.localserver.com_access_ssl.log"
> combined
>
>   ## SSL directives
>   SSLEngine on
>   SSLCertificateFile  "/etc/pki/tls/certs/_.west.isilon.com.crt"
>   SSLCertificateKeyFile   "/etc/pki/tls/private/_.west.isilon.com.key"
>   SSLCertificateChainFile "/etc/pki/tls/certs/_.west.isilon.com.chain.crt"
>   SSLCACertificatePath"/etc/pki/tls/certs"
>   WSGIScriptAlias / "/var/www/reviewboard/htdocs/reviewboard.wsgi"
> 
>
>
> Something else I have noticed is that even with reviewboard in debug mode
> (set in System Settings->Logging log level = DEBUG, I don't see anything in
> the reviewboard.log file except
> 2018-01-15 20:05:00,809 - INFO -  - root - Reloading logging settings
> Is there a way to get it to report ldap failures there?
>
> Vince
>
>
> On Monday, January 15, 2018 at 2:59:23 PM UTC-8, Christian Hammond wrote:
>>
>> Hi Vince,
>>
>> Is Review Board configured to use the same domain in General Settings as
>> you have specified in .reviewboardrc? Can you confirm that for me, and also
>> confirm that restarting Apache doesn't fix anything? I'm wondering because
>> it sounds like the cookie is being generated for the wrong domain, which
>> would mean that upon initial authentication, you're getting a cookie and
>> then trying to use it again for the wrong server. Since the RBTools debug
>> output has been modified to mask the domain, I can't verify any of this
>> myself.
>>
>> What is your web server configuration like? Is Apache handling all
>> requests itself, or are you going through Nginx or another proxy?
>>
>> Christian
>>
>> On Mon, Jan 15, 2018 at 2:51 PM, Vince Thyng  wrote:
>>
>>> Adding to my previous post, we are seeing django_session table records
>>> getting created when the webui is used, and I wasn able to use a sessionid
>>> created there with rbt by putting it in the .rbtools-cookies file, however
>>> no session is getting created when we get these failures over rbt.  We seem
>>> to be narrowing in on the problem, but now need to understand how
>>> authentication is being handled differently via rbt / the api compared to
>>> the webui.
>>>
>>> Vince
>>>
>>> On Tuesday, January 6, 2015 at 2:59:26 PM UTC-8, Julian Mehnle wrote:

 Hi all,

 I'm having trouble using rbt on the command line. No 

Re: "You are not logged in (HTTP 401, API Error 103)"

[Vince Thyng]

Confirmed, the domain matches exactly.

We have restarted apache many times while troubleshooting this, but tried a 
restart again just now.  We wanted to try `sudo python -m ipdb $(which 
rb-site) manage /var/www/reviewboard runserver 0.0.0.0:80`, but ran in to 
trouble with https not being available.

Sorry, that .rbtools-cookies file post was confusing.  It shows our 
production server in there as otherserver.com (which I can still post to 
just fine even after removing the session for it from .rbtools-cookies), 
and this new one that will replace it as localserver.com.  I think what is 
noteable about my testing is that when I remove the cookies file, it is not 
getting populated again, yet if I put a session in there manually that I 
can see in the database, it works.

Logins via webui work, while new sessions via rbt do not.

We are using apache 2.4.6 without a proxy in front, on centos 7.3

I think it is a pretty basic config, but I removed the 80->443 redirect and 
tested again just now in case that has introduced a problem.  Still no love.


  ServerName reviewboard.localserver.com

  ## Vhost docroot
  DocumentRoot "/var/www/reviewboard/"
  ## Alias declarations for resources outside the DocumentRoot
  Alias /static "/var/www/reviewboard/htdocs/static"

  ## Directories, there should at least be a declaration for 
/var/www/reviewboard/

  
Options -Indexes +FollowSymLinks
AllowOverride None
Require all granted
  

  ## Logging
  ErrorLog "/var/log/httpd/reviewboard.localserver.com_error_ssl.log"
  ServerSignature Off
  CustomLog "/var/log/httpd/reviewboard.localserver.com_access_ssl.log" 
combined

  ## SSL directives
  SSLEngine on
  SSLCertificateFile  "/etc/pki/tls/certs/_.west.isilon.com.crt"
  SSLCertificateKeyFile   "/etc/pki/tls/private/_.west.isilon.com.key"
  SSLCertificateChainFile "/etc/pki/tls/certs/_.west.isilon.com.chain.crt"
  SSLCACertificatePath"/etc/pki/tls/certs"
  WSGIScriptAlias / "/var/www/reviewboard/htdocs/reviewboard.wsgi"



Something else I have noticed is that even with reviewboard in debug mode 
(set in System Settings->Logging log level = DEBUG, I don't see anything in 
the reviewboard.log file except 
2018-01-15 20:05:00,809 - INFO -  - root - Reloading logging settings
Is there a way to get it to report ldap failures there?

Vince


On Monday, January 15, 2018 at 2:59:23 PM UTC-8, Christian Hammond wrote:
>
> Hi Vince,
>
> Is Review Board configured to use the same domain in General Settings as 
> you have specified in .reviewboardrc? Can you confirm that for me, and also 
> confirm that restarting Apache doesn't fix anything? I'm wondering because 
> it sounds like the cookie is being generated for the wrong domain, which 
> would mean that upon initial authentication, you're getting a cookie and 
> then trying to use it again for the wrong server. Since the RBTools debug 
> output has been modified to mask the domain, I can't verify any of this 
> myself.
>
> What is your web server configuration like? Is Apache handling all 
> requests itself, or are you going through Nginx or another proxy?
>
> Christian
>
> On Mon, Jan 15, 2018 at 2:51 PM, Vince Thyng  > wrote:
>
>> Adding to my previous post, we are seeing django_session table records 
>> getting created when the webui is used, and I wasn able to use a sessionid 
>> created there with rbt by putting it in the .rbtools-cookies file, however 
>> no session is getting created when we get these failures over rbt.  We seem 
>> to be narrowing in on the problem, but now need to understand how 
>> authentication is being handled differently via rbt / the api compared to 
>> the webui.
>>
>> Vince
>>
>> On Tuesday, January 6, 2015 at 2:59:26 PM UTC-8, Julian Mehnle wrote:
>>>
>>> Hi all, 
>>>
>>> I'm having trouble using rbt on the command line. No matter what I do, 
>>> anything that requires interaction with the Review Board server gives me a 
>>> "You are not logged in (HTTP 401, API Error 103)": 
>>>
>>> > joule:~/tmp/rbtools.orig> rbt --version 
>>> > RBTools 0.6.3 
>>> > joule:~/tmp/rbtools.orig> git log --stat master ^origin/master | more 
>>> > commit 86dc0ab71c20a599c33efa7ea694c12281fe8ef6 
>>> > Author: Julian Mehnle  
>>> > Date:   Tue Jan 6 22:45:19 2015 + 
>>> > 
>>> > When raising CommandError, include lower-level exception. 
>>> > 
>>> >  rbtools/commands/__init__.py | 2 +- 
>>> >  1 file changed, 1 insertion(+), 1 deletion(-) 
>>> > joule:~/tmp/rbtools.orig> rbt post --debug -g 
>>> > >>> RBTools 0.6.3 
>>> > >>> Python 2.7.9 (default, Dec 13 2014, 15:13:49) 
>>> > [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)] 
>>> > >>> Running on Darwin-14.0.0-x86_64-i386-64bit 
>>> > >>> Home = /Users/julian 
>>> > >>> Current directory = /Users/julian/tmp/rbtools.orig 
>>> > >>> Checking for a Subversion repository... 
>>> > >>> Running: svn info --non-interactive 
>>> > >>> Command exited with rc 1: ['svn', 'info', '--non-interactive'] 

Re: "You are not logged in (HTTP 401, API Error 103)"

[Christian Hammond]

Hi Vince,

Is Review Board configured to use the same domain in General Settings as
you have specified in .reviewboardrc? Can you confirm that for me, and also
confirm that restarting Apache doesn't fix anything? I'm wondering because
it sounds like the cookie is being generated for the wrong domain, which
would mean that upon initial authentication, you're getting a cookie and
then trying to use it again for the wrong server. Since the RBTools debug
output has been modified to mask the domain, I can't verify any of this
myself.

What is your web server configuration like? Is Apache handling all requests
itself, or are you going through Nginx or another proxy?

Christian

On Mon, Jan 15, 2018 at 2:51 PM, Vince Thyng  wrote:

> Adding to my previous post, we are seeing django_session table records
> getting created when the webui is used, and I wasn able to use a sessionid
> created there with rbt by putting it in the .rbtools-cookies file, however
> no session is getting created when we get these failures over rbt.  We seem
> to be narrowing in on the problem, but now need to understand how
> authentication is being handled differently via rbt / the api compared to
> the webui.
>
> Vince
>
> On Tuesday, January 6, 2015 at 2:59:26 PM UTC-8, Julian Mehnle wrote:
>>
>> Hi all,
>>
>> I'm having trouble using rbt on the command line. No matter what I do,
>> anything that requires interaction with the Review Board server gives me a
>> "You are not logged in (HTTP 401, API Error 103)":
>>
>> > joule:~/tmp/rbtools.orig> rbt --version
>> > RBTools 0.6.3
>> > joule:~/tmp/rbtools.orig> git log --stat master ^origin/master | more
>> > commit 86dc0ab71c20a599c33efa7ea694c12281fe8ef6
>> > Author: Julian Mehnle 
>> > Date:   Tue Jan 6 22:45:19 2015 +
>> >
>> > When raising CommandError, include lower-level exception.
>> >
>> >  rbtools/commands/__init__.py | 2 +-
>> >  1 file changed, 1 insertion(+), 1 deletion(-)
>> > joule:~/tmp/rbtools.orig> rbt post --debug -g
>> > >>> RBTools 0.6.3
>> > >>> Python 2.7.9 (default, Dec 13 2014, 15:13:49)
>> > [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)]
>> > >>> Running on Darwin-14.0.0-x86_64-i386-64bit
>> > >>> Home = /Users/julian
>> > >>> Current directory = /Users/julian/tmp/rbtools.orig
>> > >>> Checking for a Subversion repository...
>> > >>> Running: svn info --non-interactive
>> > >>> Command exited with rc 1: ['svn', 'info', '--non-interactive']
>> > svn: E155007: '/Users/julian/tmp/rbtools.orig' is not a working copy
>> > ---
>> > >>> Checking for a Git repository...
>> > >>> Running: git rev-parse --git-dir
>> > >>> Running: git config core.bare
>> > >>> Running: git rev-parse --show-toplevel
>> > >>> Running: git symbolic-ref -q HEAD
>> > >>> Running: git config --get branch.master.merge
>> > >>> Running: git config --get branch.master.remote
>> > >>> Running: git config --get remote.origin.url
>> > >>> repository info: Path: git://github.com/reviewboard/rbtools.git,
>> Base path: , Supports changesets: False
>> > >>> Making HTTP GET request to https://reviews.reviewboard.org/api/
>> > >>> Running: git rev-parse refs/heads/master
>> > >>> Running: git merge-base 86dc0ab71c20a599c33efa7ea694c12281fe8ef6
>> origin/master
>> > >>> Running: git rev-parse bcb7629c0be773b6f347a5006224825b8726c479
>> > >>> Running: git status --porcelain --untracked-files=no
>> > >>> Running: git diff --no-color --full-index --ignore-submodules
>> bcb7629c0be773b6f347a5006224825b8726c479..86dc0ab71c20a599c33efa7ea694c12281fe8ef6
>> -M --no-ext-diff
>> > >>> Running: git log --reverse --pretty=format:%s%n%n%b
>> ^bcb7629c0be773b6f347a5006224825b8726c479 
>> 86dc0ab71c20a599c33efa7ea694c12281fe8ef6
>>
>> > >>> Making HTTP GET request to https://reviews.reviewboard.or
>> g/api/review-requests/
>> > >>> Making HTTP POST request to https://reviews.reviewboard.or
>> g/api/review-requests/
>> > >>> Got API Error 103 (HTTP code 401): You are not logged in
>> > >>> Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not
>> logged in', u'code': 103}}
>> > Traceback (most recent call last):
>> >   File "/usr/local/bin/rbt", line 9, in 
>> > load_entry_point('RBTools==0.6.3', 'console_scripts', 'rbt')()
>> >   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.
>> 7/lib/python2.7/site-packages/RBTools-0.6.3-py2.7.egg/rbtools/commands/main.py",
>> line 134, in main
>> > command.run_from_argv([RB_MAIN, command_name] + args)
>> >   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.
>> 7/lib/python2.7/site-packages/RBTools-0.6.3-py2.7.egg/rbtools/commands/__init__.py",
>> line 416, in run_from_argv
>> > exit_code = self.main(*args) or 0
>> >   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.
>> 7/lib/python2.7/site-packages/RBTools-0.6.3-py2.7.egg/rbtools/commands/post.py",
>> line 791, in main
>> > submit_as=self.options.submit_as)
>> >   File 

Re: "You are not logged in (HTTP 401, API Error 103)"

[Vince Thyng]

Adding to my previous post, we are seeing django_session table records 
getting created when the webui is used, and I wasn able to use a sessionid 
created there with rbt by putting it in the .rbtools-cookies file, however 
no session is getting created when we get these failures over rbt.  We seem 
to be narrowing in on the problem, but now need to understand how 
authentication is being handled differently via rbt / the api compared to 
the webui.

Vince

On Tuesday, January 6, 2015 at 2:59:26 PM UTC-8, Julian Mehnle wrote:
>
> Hi all, 
>
> I'm having trouble using rbt on the command line. No matter what I do, 
> anything that requires interaction with the Review Board server gives me a 
> "You are not logged in (HTTP 401, API Error 103)": 
>
> > joule:~/tmp/rbtools.orig> rbt --version 
> > RBTools 0.6.3 
> > joule:~/tmp/rbtools.orig> git log --stat master ^origin/master | more 
> > commit 86dc0ab71c20a599c33efa7ea694c12281fe8ef6 
> > Author: Julian Mehnle  
> > Date:   Tue Jan 6 22:45:19 2015 + 
> > 
> > When raising CommandError, include lower-level exception. 
> > 
> >  rbtools/commands/__init__.py | 2 +- 
> >  1 file changed, 1 insertion(+), 1 deletion(-) 
> > joule:~/tmp/rbtools.orig> rbt post --debug -g 
> > >>> RBTools 0.6.3 
> > >>> Python 2.7.9 (default, Dec 13 2014, 15:13:49) 
> > [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)] 
> > >>> Running on Darwin-14.0.0-x86_64-i386-64bit 
> > >>> Home = /Users/julian 
> > >>> Current directory = /Users/julian/tmp/rbtools.orig 
> > >>> Checking for a Subversion repository... 
> > >>> Running: svn info --non-interactive 
> > >>> Command exited with rc 1: ['svn', 'info', '--non-interactive'] 
> > svn: E155007: '/Users/julian/tmp/rbtools.orig' is not a working copy 
> > --- 
> > >>> Checking for a Git repository... 
> > >>> Running: git rev-parse --git-dir 
> > >>> Running: git config core.bare 
> > >>> Running: git rev-parse --show-toplevel 
> > >>> Running: git symbolic-ref -q HEAD 
> > >>> Running: git config --get branch.master.merge 
> > >>> Running: git config --get branch.master.remote 
> > >>> Running: git config --get remote.origin.url 
> > >>> repository info: Path: git://github.com/reviewboard/rbtools.git, 
> Base path: , Supports changesets: False 
> > >>> Making HTTP GET request to https://reviews.reviewboard.org/api/ 
> > >>> Running: git rev-parse refs/heads/master 
> > >>> Running: git merge-base 86dc0ab71c20a599c33efa7ea694c12281fe8ef6 
> origin/master 
> > >>> Running: git rev-parse bcb7629c0be773b6f347a5006224825b8726c479 
> > >>> Running: git status --porcelain --untracked-files=no 
> > >>> Running: git diff --no-color --full-index --ignore-submodules 
> bcb7629c0be773b6f347a5006224825b8726c479..86dc0ab71c20a599c33efa7ea694c12281fe8ef6
>  
> -M --no-ext-diff 
> > >>> Running: git log --reverse --pretty=format:%s%n%n%b 
> ^bcb7629c0be773b6f347a5006224825b8726c479 
> 86dc0ab71c20a599c33efa7ea694c12281fe8ef6 
> > >>> Making HTTP GET request to 
> https://reviews.reviewboard.org/api/review-requests/ 
> > >>> Making HTTP POST request to 
> https://reviews.reviewboard.org/api/review-requests/ 
> > >>> Got API Error 103 (HTTP code 401): You are not logged in 
> > >>> Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged 
> in', u'code': 103}} 
> > Traceback (most recent call last): 
> >   File "/usr/local/bin/rbt", line 9, in  
> > load_entry_point('RBTools==0.6.3', 'console_scripts', 'rbt')() 
> >   File 
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/RBTools-0.6.3-py2.7.egg/rbtools/commands/main.py",
>  
> line 134, in main 
> > command.run_from_argv([RB_MAIN, command_name] + args) 
> >   File 
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/RBTools-0.6.3-py2.7.egg/rbtools/commands/__init__.py",
>  
> line 416, in run_from_argv 
> > exit_code = self.main(*args) or 0 
> >   File 
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/RBTools-0.6.3-py2.7.egg/rbtools/commands/post.py",
>  
> line 791, in main 
> > submit_as=self.options.submit_as) 
> >   File 
> "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/RBTools-0.6.3-py2.7.egg/rbtools/commands/post.py",
>  
> line 507, in post_request 
> > raise CommandError("Error creating review request: %s" % e) 
> > rbtools.commands.CommandError: Error creating review request: You are 
> not logged in (HTTP 401, API Error 103) 
>
>
> I've tried removing ~/.rbtools-cookies, as well as specifying --username 
> and --password on the command line, to no avail. I've tried both posting to 
> https://reviews.reviewboard.org and my company's internal Review Board 
> server (running RB 1.7.19. I'm running Python 2.7.9 on Mac OS X 10.10.1. 
>
> I'm not sure what triggered this. How should I go about debugging this? 
>
> -Julian 
>
>

-- 
Supercharge your Review Board with Power 

Re: "You are not logged in (HTTP 401, API Error 103)"

[Vince Thyng]

We are having this same issue on a new server I bought up to migrate data 
to.  Here is a log of me removing the .rbtools-cookies file, showing the 
failure upon entering credentials, no .rbtools-cookies file is created, 
putting the file back, and it works.  I had this problem until today when I 
added 'import pdb; pdb.set_trace()' to the rbtools/api/request.py file 
in make_request().  It still failed at first and then stepping through one 
time worked.  This only fixed the problem for my account though.  My 
co-worker helping me test it is still failing.  I suspect rbt is failing to 
get a rbsessionid to set.  I tried reproducing my success by moving the 
.rbtools-cookies file away and now it just creates an empty file when I 
attempt another rbt post.  So I still need help here.


13:25 $ mv ~/.rbtools-cookies ~/shared/
(python27) ✔ ~/w/netboot [rb2 L|✔] 
13:32 $ rbt post -u --debug
>>> RBTools 0.7.10
>>> Python 2.7.12 (default, Nov 19 2016, 06:48:10) 
[GCC 5.4.0 20160609]
>>> Running on Linux-4.10.0-37-generic-x86_64-with-Ubuntu-16.04-xenial
>>> Home = /home/vthyng
>>> Current directory = /home/vthyng/w/netboot
>>> Command line: rbt post -u --debug
>>> Running: tf vc help
>>> Checking for a Subversion repository...
>>> Unable to execute "svn help": skipping SVN
>>> Checking for a Git repository...
>>> Running: git rev-parse --git-dir
>>> Running: git config core.bare
>>> Running: git rev-parse --show-toplevel
>>> Running: git symbolic-ref -q HEAD
>>> Running: git config --get branch.rb2.merge
>>> Command exited with rc 1: ['git', 'config', '--get', 
u'branch.rb2.merge']
---
>>> Running: git config --get branch.rb2.remote
>>> Command exited with rc 1: ['git', 'config', '--get', 
u'branch.rb2.remote']
---
>>> Running: git config --get remote.origin.url
>>> repository info: Path: g...@github.localserver.com:vthyng/netboot.git, 
Base path: , Supports changesets: False
>>> Making HTTP GET request to http://reviewboard.localserver.com/api/

Please log in to the Review Board server at reviewboard.localserver.com.
Username: vthyng
Password: 
>>> Got API Error 103 (HTTP code 401): You are not logged in
>>> Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged 
in', u'code': 103}}
Traceback (most recent call last):
  File "/home/vthyng/e/python27/bin/rbt", line 11, in 
sys.exit(main())
  File 
"/home/vthyng/e/python27/local/lib/python2.7/site-packages/rbtools/commands/main.py",
 
line 133, in main
command.run_from_argv([RB_MAIN, command_name] + args)
  File 
"/home/vthyng/e/python27/local/lib/python2.7/site-packages/rbtools/commands/__init__.py",
 
line 663, in run_from_argv
exit_code = self.main(*args) or 0
  File 
"/home/vthyng/e/python27/local/lib/python2.7/site-packages/rbtools/commands/post.py",
 
line 701, in main
api_client, api_root = self.get_api(server_url)
  File 
"/home/vthyng/e/python27/local/lib/python2.7/site-packages/rbtools/commands/__init__.py",
 
line 850, in get_api
raise CommandError('Unexpected API Error: %s' % e)
rbtools.commands.CommandError: Unexpected API Error: You are not logged in 
(HTTP 401, API Error 103)
(python27) ✘-1 ~/w/netboot [rb2 L|✔] 
13:32 $ cat ~/.rbtools-cookies 
(python27) ✔ ~/w/netboot [rb2 L|✔] 
(python27) ✘-1 ~/w/netboot [rb2 L|✔] 
13:33 $ mv ~/shared/.rbtools-cookies ~/
(python27) ✔ ~/w/netboot [rb2 L|✔] 
13:33 $ rbt post -u --debug
>>> RBTools 0.7.10
>>> Python 2.7.12 (default, Nov 19 2016, 06:48:10) 
[GCC 5.4.0 20160609]
>>> Running on Linux-4.10.0-37-generic-x86_64-with-Ubuntu-16.04-xenial
>>> Home = /home/vthyng
>>> Current directory = /home/vthyng/w/netboot
>>> Command line: rbt post -u --debug
>>> Running: tf vc help
>>> Checking for a Subversion repository...
>>> Unable to execute "svn help": skipping SVN
>>> Checking for a Git repository...
>>> Running: git rev-parse --git-dir
>>> Running: git config core.bare
>>> Running: git rev-parse --show-toplevel
>>> Running: git symbolic-ref -q HEAD
>>> Running: git config --get branch.rb2.merge
>>> Command exited with rc 1: ['git', 'config', '--get', 
u'branch.rb2.merge']
---
>>> Running: git config --get branch.rb2.remote
>>> Command exited with rc 1: ['git', 'config', '--get', 
u'branch.rb2.remote']
---
>>> Running: git config --get remote.origin.url
>>> repository info: Path: g...@github.localserver.com:vthyng/netboot.git, 
Base path: , Supports changesets: False
>>> Making HTTP GET request to http://reviewboard.localserver.com/api/
>>> Running: git rev-parse refs/heads/rb2
>>> Running: git merge-base 67f0abe6e9dd0c332543b9dd6714ceb807169d2b 
origin/master
>>> Running: git rev-parse 587b8912f63c47969c8b0ad9150c963427802925
>>> Running: git status --porcelain --untracked-files=no 
--ignore-submodules=dirty
>>> Running: git rev-parse --git-dir
>>> Running: git version
>>> Running: git -c core.quotepath=false -c diff.noprefix=false diff 
--no-color --full-index --ignore-submodules -M --no-ext-diff 
587b8912f63c47969c8b0ad9150c963427802925..67f0abe6e9dd0c332543b9dd6714ceb807169d2b

Re: "You are not logged in (HTTP 401, API Error 103)"

[Christian Hammond]

;>> Connection:
>>>>>>>> > keep-alive Cache-Control: max-age=0 Accept:
>>>>>>>> > text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
>>>>>>>>
>>>>>>>> > User-Agent: Mozilla/5.0 (Windows NT 5.2) AppleWebKit/537.36
>>>>>>>> (KHTML,
>>>>>>>> > like Gecko) Chrome/40.0.2214.91 Safari/537.36 Accept-Encoding:
>>>>>>>> gzip,
>>>>>>>> > deflate, sdch Accept-Language: en-US,en;q=0.8 Cookie:
>>>>>>>> > csrftoken=R2Xe4tSc3pt0xVoAK8ROQ0FyG8DnUFd8;
>>>>>>>> > rbsessionid=nuigvg158krygm0zul6i2xwwb344g15a
>>>>>>>> >
>>>>>>>> > Response Headers
>>>>>>>> >
>>>>>>>> > HTTP/1.1 404 NOT FOUND Date: Tue, 10 Feb 2015 13:12:19 GMT
>>>>>>>> Server:
>>>>>>>> > Apache Content-Length: 139 Content-Language: en
>>>>>>>> > X-Content-Type-Options: nosniff Expires: Tue, 10 Feb 2015
>>>>>>>> 13:12:19 GMT
>>>>>>>> > Vary: Cookie,Accept-Language Last-Modified: Tue, 10 Feb 2015
>>>>>>>> 13:12:19
>>>>>>>> > GMT Cache-Control: max-age=0 X-Frame-Options: SAMEORIGIN
>>>>>>>> Keep-Alive:
>>>>>>>> > timeout=15, max=100 Connection: Keep-Alive Content-Type:
>>>>>>>> > application/xml
>>>>>>>> >
>>>>>>>> > 
>>>>>>>> > 
>>>>>>>> >  fail
>>>>>>>> >  
>>>>>>>> >   Object does not exist
>>>>>>>> >   100
>>>>>>>> >  
>>>>>>>> > 
>>>>>>>> > ===
>>>>>>>> >
>>>>>>>> >
>>>>>>>> > conf/apache-wsgi.conf
>>>>>>>> > ===
>>>>>>>> > 
>>>>>>>> > ServerName reviewboard.lcgentoo.local
>>>>>>>> > DocumentRoot "/var/www/reviewboard.lcgentoo.local/htdocs"
>>>>>>>> >
>>>>>>>> > # Error handlers
>>>>>>>> > ErrorDocument 500 /errordocs/500.html
>>>>>>>> >
>>>>>>>> > WSGIPassAuthorization On
>>>>>>>> > WSGIScriptAlias "/"
>>>>>>>> > "/var/www/reviewboard.lcgentoo.local/htdocs/reviewboard.wsgi/"
>>>>>>>> >
>>>>>>>> > 
>>>>>>>> > AllowOverride All
>>>>>>>> > Options -Indexes +FollowSymLinks
>>>>>>>> > Allow from all
>>>>>>>> > 
>>>>>>>> >
>>>>>>>> > # Prevent the server from processing or allowing the
>>>>>>>> rendering of
>>>>>>>> > # certain file types.
>>>>>>>> > 
>>>>>>>> > SetHandler None
>>>>>>>> > Options None
>>>>>>>> >
>>>>>>>> > AddType text/plain .html .htm .shtml .php .php3 .php4
>>>>>>>> .php5 .phps .asp
>>>>>>>> > AddType text/plain .pl .py .fcgi .cgi .phtml .phtm .pht
>>>>>>>> .jsp .sh .rb
>>>>>>>> >
>>>>>>>> > 
>>>>>>>> > php_flag engine off
>>>>>>>> > 
>>>>>>>> > 
>>>>>>>> >
>>>>>>>> > # Alias static media requests to filesystem
>>>>>>>> > Alias /media "/var/www/reviewboard.lcgentoo.local/htdocs/media"
>>>>>>>>
>>>>>>>> > Alias /static "/var/www/reviewboard.lcgentoo.local/htdocs/static"
>>>>>>>>
>>>>>>>> > Alias /errordocs 
>>>>>>>> > "/var/www/reviewboard.lcgentoo.local/htdocs/errordocs"
&g

Re: "You are not logged in (HTTP 401, API Error 103)"

['Chris Westin' via reviewboard]

tent-Type: 
>>>>>>> > application/xml 
>>>>>>> > 
>>>>>>> >  
>>>>>>> >  
>>>>>>> >  fail 
>>>>>>> >   
>>>>>>> >   Object does not exist 
>>>>>>> >   100 
>>>>>>> >   
>>>>>>> >  
>>>>>>> > === 
>>>>>>> > 
>>>>>>> > 
>>>>>>> > conf/apache-wsgi.conf 
>>>>>>> > === 
>>>>>>> >  
>>>>>>> > ServerName reviewboard.lcgentoo.local 
>>>>>>> > DocumentRoot "/var/www/reviewboard.lcgentoo.local/htdocs" 
>>>>>>> > 
>>>>>>> > # Error handlers 
>>>>>>> > ErrorDocument 500 /errordocs/500.html 
>>>>>>> > 
>>>>>>> > WSGIPassAuthorization On 
>>>>>>> > WSGIScriptAlias "/" 
>>>>>>> > "/var/www/reviewboard.lcgentoo.local/htdocs/reviewboard.wsgi/" 
>>>>>>> > 
>>>>>>> >  
>>>>>>> > AllowOverride All 
>>>>>>> > Options -Indexes +FollowSymLinks 
>>>>>>> > Allow from all 
>>>>>>> >  
>>>>>>> > 
>>>>>>> > # Prevent the server from processing or allowing the rendering 
>>>>>>> of 
>>>>>>> > # certain file types. 
>>>>>>> >  
>>>>>>> > SetHandler None 
>>>>>>> > Options None 
>>>>>>> > 
>>>>>>> > AddType text/plain .html .htm .shtml .php .php3 .php4 
>>>>>>> .php5 .phps .asp 
>>>>>>> > AddType text/plain .pl .py .fcgi .cgi .phtml .phtm .pht 
>>>>>>> .jsp .sh .rb 
>>>>>>> > 
>>>>>>> >  
>>>>>>> > php_flag engine off 
>>>>>>> >  
>>>>>>> >  
>>>>>>> > 
>>>>>>> > # Alias static media requests to filesystem 
>>>>>>> > Alias /media 
>>>>>>> "/var/www/reviewboard.lcgentoo.local/htdocs/media" 
>>>>>>> > Alias /static 
>>>>>>> "/var/www/reviewboard.lcgentoo.local/htdocs/static" 
>>>>>>> > Alias /errordocs 
>>>>>>> "/var/www/reviewboard.lcgentoo.local/htdocs/errordocs" 
>>>>>>> > Alias /favicon.ico 
>>>>>>> > 
>>>>>>> "/var/www/reviewboard.lcgentoo.local/htdocs/static/rb/images/favicon.png"
>>>>>>>  
>>>>>>> >  
>>>>>>> > === 
>>>>>>> > 
>>>>>>> > htdocs/reviewboard.wsgi 
>>>>>>> > === 
>>>>>>> > import __main__ 
>>>>>>> > __main__.__requires__ = ['ReviewBoard'] 
>>>>>>> > import pkg_resources 
>>>>>>> > 
>>>>>>> > import os 
>>>>>>> > import sys 
>>>>>>> > 
>>>>>>> > os.environ['DJANGO_SETTINGS_MODULE'] = "reviewboard.settings" 
>>>>>>> > os.environ['PYTHON_EGG_CACHE'] = 
>>>>>>> > "/var/www/reviewboard.lcgentoo.local/tmp/egg_cache" 
>>>>>>> > os.environ['HOME'] = "/var/www/reviewboard.lcgentoo.local/data" 
>>>>>>> > os.environ['PYTHONPATH'] = 
>>>>>>> '/var/www/reviewboard.lcgentoo.local/conf:' 
>>>>>>> > + os.environ.get('PYTHONPATH', '') 
>>>>>>> > 
>>>>>>> > sys.path = ['/var/www/reviewboard.lcgentoo.local/conf'] + sys.path 
>>>>>>> > 
>>>>>>> > import django.core.handlers.wsgi 
>>>>>>> > application = django.core.handlers.wsgi.WSGIHandler() 
>>>>>>> > 

Re: "You are not logged in (HTTP 401, API Error 103)"

[Christian Hammond]

t;>>>>> >
>>>>>> >
>>>>>> > conf/apache-wsgi.conf
>>>>>> > ===
>>>>>> > 
>>>>>> > ServerName reviewboard.lcgentoo.local
>>>>>> > DocumentRoot "/var/www/reviewboard.lcgentoo.local/htdocs"
>>>>>> >
>>>>>> > # Error handlers
>>>>>> > ErrorDocument 500 /errordocs/500.html
>>>>>> >
>>>>>> > WSGIPassAuthorization On
>>>>>> > WSGIScriptAlias "/"
>>>>>> > "/var/www/reviewboard.lcgentoo.local/htdocs/reviewboard.wsgi/"
>>>>>> >
>>>>>> > 
>>>>>> > AllowOverride All
>>>>>> > Options -Indexes +FollowSymLinks
>>>>>> > Allow from all
>>>>>> > 
>>>>>> >
>>>>>> > # Prevent the server from processing or allowing the rendering
>>>>>> of
>>>>>> > # certain file types.
>>>>>> > 
>>>>>> > SetHandler None
>>>>>> > Options None
>>>>>> >
>>>>>> > AddType text/plain .html .htm .shtml .php .php3 .php4 .php5
>>>>>> .phps .asp
>>>>>> > AddType text/plain .pl .py .fcgi .cgi .phtml .phtm .pht
>>>>>> .jsp .sh .rb
>>>>>> >
>>>>>> > 
>>>>>> > php_flag engine off
>>>>>> > 
>>>>>> > 
>>>>>> >
>>>>>> > # Alias static media requests to filesystem
>>>>>> > Alias /media "/var/www/reviewboard.lcgentoo.local/htdocs/media"
>>>>>>
>>>>>> > Alias /static "/var/www/reviewboard.lcgentoo.local/htdocs/static"
>>>>>>
>>>>>> > Alias /errordocs 
>>>>>> > "/var/www/reviewboard.lcgentoo.local/htdocs/errordocs"
>>>>>>
>>>>>> > Alias /favicon.ico
>>>>>> > "/var/www/reviewboard.lcgentoo.local/htdocs/static/rb/images/favicon.png"
>>>>>>
>>>>>> > 
>>>>>> > ===
>>>>>> >
>>>>>> > htdocs/reviewboard.wsgi
>>>>>> > ===
>>>>>> > import __main__
>>>>>> > __main__.__requires__ = ['ReviewBoard']
>>>>>> > import pkg_resources
>>>>>> >
>>>>>> > import os
>>>>>> > import sys
>>>>>> >
>>>>>> > os.environ['DJANGO_SETTINGS_MODULE'] = "reviewboard.settings"
>>>>>> > os.environ['PYTHON_EGG_CACHE'] =
>>>>>> > "/var/www/reviewboard.lcgentoo.local/tmp/egg_cache"
>>>>>> > os.environ['HOME'] = "/var/www/reviewboard.lcgentoo.local/data"
>>>>>> > os.environ['PYTHONPATH'] = '/var/www/reviewboard.lcgentoo.local/conf:'
>>>>>>
>>>>>> > + os.environ.get('PYTHONPATH', '')
>>>>>> >
>>>>>> > sys.path = ['/var/www/reviewboard.lcgentoo.local/conf'] + sys.path
>>>>>> >
>>>>>> > import django.core.handlers.wsgi
>>>>>> > application = django.core.handlers.wsgi.WSGIHandler()
>>>>>> > ===
>>>>>> >
>>>>>> > /etc/apache2/vhosts.d/local.lcgentoo.reviewboard.vhost.conf
>>>>>> > ===
>>>>>> > 
>>>>>> > 
>>>>>> > ServerName reviewboard.lcgentoo.local
>>>>>> > DocumentRoot "/var/www/reviewboard.lcgentoo.local/htdocs"
>>>>>> >
>>>>>> > SetEnv HOME /var/www/reviewboard.lcgentoo.local/data
>>>>>> >
>>>>>> > # Error handlers
>>>>>> > ErrorDocument 500 /errordocs/500.html
>>>>>> >
>>>>>> > # Serve django pages
>>>>>> > WSGIScriptAlias /
>>

Re: "You are not logged in (HTTP 401, API Error 103)"

['Chris Westin' via reviewboard]

>>> > 
>>>>> > AddType text/plain .html .htm .shtml .php .php3 .php4 .php5 
>>>>> .phps .asp 
>>>>> > AddType text/plain .pl .py .fcgi .cgi .phtml .phtm .pht .jsp 
>>>>> .sh .rb 
>>>>> > 
>>>>> >  
>>>>> > php_flag engine off 
>>>>> >  
>>>>> >  
>>>>> > 
>>>>> > # Alias static media requests to filesystem 
>>>>> > Alias /media "/var/www/reviewboard.lcgentoo.local/htdocs/media" 
>>>>> > Alias /static 
>>>>> "/var/www/reviewboard.lcgentoo.local/htdocs/static" 
>>>>> > Alias /errordocs 
>>>>> "/var/www/reviewboard.lcgentoo.local/htdocs/errordocs" 
>>>>> > Alias /favicon.ico 
>>>>> > 
>>>>> "/var/www/reviewboard.lcgentoo.local/htdocs/static/rb/images/favicon.png" 
>>>>> >  
>>>>> > === 
>>>>> > 
>>>>> > htdocs/reviewboard.wsgi 
>>>>> > === 
>>>>> > import __main__ 
>>>>> > __main__.__requires__ = ['ReviewBoard'] 
>>>>> > import pkg_resources 
>>>>> > 
>>>>> > import os 
>>>>> > import sys 
>>>>> > 
>>>>> > os.environ['DJANGO_SETTINGS_MODULE'] = "reviewboard.settings" 
>>>>> > os.environ['PYTHON_EGG_CACHE'] = 
>>>>> > "/var/www/reviewboard.lcgentoo.local/tmp/egg_cache" 
>>>>> > os.environ['HOME'] = "/var/www/reviewboard.lcgentoo.local/data" 
>>>>> > os.environ['PYTHONPATH'] = 
>>>>> '/var/www/reviewboard.lcgentoo.local/conf:' 
>>>>> > + os.environ.get('PYTHONPATH', '') 
>>>>> > 
>>>>> > sys.path = ['/var/www/reviewboard.lcgentoo.local/conf'] + sys.path 
>>>>> > 
>>>>> > import django.core.handlers.wsgi 
>>>>> > application = django.core.handlers.wsgi.WSGIHandler() 
>>>>> > === 
>>>>> > 
>>>>> > /etc/apache2/vhosts.d/local.lcgentoo.reviewboard.vhost.conf 
>>>>> > === 
>>>>> >  
>>>>> >  
>>>>> > ServerName reviewboard.lcgentoo.local 
>>>>> > DocumentRoot "/var/www/reviewboard.lcgentoo.local/htdocs" 
>>>>> > 
>>>>> > SetEnv HOME /var/www/reviewboard.lcgentoo.local/data 
>>>>> > 
>>>>> > # Error handlers 
>>>>> > ErrorDocument 500 /errordocs/500.html 
>>>>> > 
>>>>> > # Serve django pages 
>>>>> > WSGIScriptAlias / 
>>>>> > /var/www/reviewboard.lcgentoo.local/htdocs/reviewboard.wsgi 
>>>>> >  
>>>>> > #SetHandler wsgi-script 
>>>>> > #Options +ExecCGI 
>>>>> > #PythonPath 
>>>>> > "['/var/www/reviewboard.lcgentoo.local/conf'] + sys.path" 
>>>>> > #SetEnv DJANGO_SETTINGS_MODULE reviewboard.settings 
>>>>> > #SetEnv PYTHON_EGG_CACHE 
>>>>> > "/var/www/reviewboard.lcgentoo.local/tmp/egg_cache" 
>>>>> > #SetHandler mod_python 
>>>>> > #PythonHandler django.core.handlers.modpython 
>>>>> > #PythonAutoReload Off 
>>>>> > #PythonDebug Off 
>>>>> > # Used to run multiple mod_python sites in the same 
>>>>> apache 
>>>>> > #PythonInterpreter 
>>>>> reviewboard_reviewboard_lcgentoo_local 
>>>>> >  
>>>>> > 
>>>>> > # Serve static media without running it through mod_python 
>>>>> > # (overrides the above) 
>>>>> >  
>>>>> > SetHandler None 
>>>>> >  
>>>>> > 
>>>>> > Alias /static 
>>>>> "/var/www/reviewboard.lcgentoo.local/htdocs/stati

Re: "You are not logged in (HTTP 401, API Error 103)"

[Christian Hammond]

;> > # Error handlers
>>>> > ErrorDocument 500 /errordocs/500.html
>>>> >
>>>> > WSGIPassAuthorization On
>>>> > WSGIScriptAlias "/"
>>>> > "/var/www/reviewboard.lcgentoo.local/htdocs/reviewboard.wsgi/"
>>>> >
>>>> > 
>>>> > AllowOverride All
>>>> > Options -Indexes +FollowSymLinks
>>>> > Allow from all
>>>> > 
>>>> >
>>>> > # Prevent the server from processing or allowing the rendering of
>>>> > # certain file types.
>>>> > 
>>>> > SetHandler None
>>>> > Options None
>>>> >
>>>> > AddType text/plain .html .htm .shtml .php .php3 .php4 .php5
>>>> .phps .asp
>>>> > AddType text/plain .pl .py .fcgi .cgi .phtml .phtm .pht .jsp
>>>> .sh .rb
>>>> >
>>>> > 
>>>> > php_flag engine off
>>>> > 
>>>> > 
>>>> >
>>>> > # Alias static media requests to filesystem
>>>> > Alias /media "/var/www/reviewboard.lcgentoo.local/htdocs/media"
>>>> > Alias /static "/var/www/reviewboard.lcgentoo.local/htdocs/static"
>>>>
>>>> > Alias /errordocs 
>>>> > "/var/www/reviewboard.lcgentoo.local/htdocs/errordocs"
>>>>
>>>> > Alias /favicon.ico
>>>> > "/var/www/reviewboard.lcgentoo.local/htdocs/static/rb/images/favicon.png"
>>>>
>>>> > 
>>>> > ===
>>>> >
>>>> > htdocs/reviewboard.wsgi
>>>> > ===
>>>> > import __main__
>>>> > __main__.__requires__ = ['ReviewBoard']
>>>> > import pkg_resources
>>>> >
>>>> > import os
>>>> > import sys
>>>> >
>>>> > os.environ['DJANGO_SETTINGS_MODULE'] = "reviewboard.settings"
>>>> > os.environ['PYTHON_EGG_CACHE'] =
>>>> > "/var/www/reviewboard.lcgentoo.local/tmp/egg_cache"
>>>> > os.environ['HOME'] = "/var/www/reviewboard.lcgentoo.local/data"
>>>> > os.environ['PYTHONPATH'] = '/var/www/reviewboard.lcgentoo.local/conf:'
>>>>
>>>> > + os.environ.get('PYTHONPATH', '')
>>>> >
>>>> > sys.path = ['/var/www/reviewboard.lcgentoo.local/conf'] + sys.path
>>>> >
>>>> > import django.core.handlers.wsgi
>>>> > application = django.core.handlers.wsgi.WSGIHandler()
>>>> > ===
>>>> >
>>>> > /etc/apache2/vhosts.d/local.lcgentoo.reviewboard.vhost.conf
>>>> > ===
>>>> > 
>>>> > 
>>>> > ServerName reviewboard.lcgentoo.local
>>>> > DocumentRoot "/var/www/reviewboard.lcgentoo.local/htdocs"
>>>> >
>>>> > SetEnv HOME /var/www/reviewboard.lcgentoo.local/data
>>>> >
>>>> > # Error handlers
>>>> > ErrorDocument 500 /errordocs/500.html
>>>> >
>>>> > # Serve django pages
>>>> > WSGIScriptAlias /
>>>> > /var/www/reviewboard.lcgentoo.local/htdocs/reviewboard.wsgi
>>>> > 
>>>> > #SetHandler wsgi-script
>>>> > #Options +ExecCGI
>>>> > #PythonPath
>>>> > "['/var/www/reviewboard.lcgentoo.local/conf'] + sys.path"
>>>> > #SetEnv DJANGO_SETTINGS_MODULE reviewboard.settings
>>>> > #SetEnv PYTHON_EGG_CACHE
>>>> > "/var/www/reviewboard.lcgentoo.local/tmp/egg_cache"
>>>> > #SetHandler mod_python
>>>> > #PythonHandler django.core.handlers.modpython
>>>> > #PythonAutoReload Off
>>>> > #PythonDebug Off
>>>> > # Used to run multiple mod_python sites in the same
>>>> apache
>>>> > #PythonInterpreter reviewboard_reviewboard_lcgentoo_local
>>>

Re: "You are not logged in (HTTP 401, API Error 103)"

['Chris Westin' via reviewboard]

t;>> > AddType text/plain .pl .py .fcgi .cgi .phtml .phtm .pht .jsp 
>>> .sh .rb 
>>> > 
>>> >  
>>> > php_flag engine off 
>>> >  
>>> >  
>>> > 
>>> > # Alias static media requests to filesystem 
>>> > Alias /media "/var/www/reviewboard.lcgentoo.local/htdocs/media" 
>>> > Alias /static "/var/www/reviewboard.lcgentoo.local/htdocs/static" 
>>> > Alias /errordocs 
>>> "/var/www/reviewboard.lcgentoo.local/htdocs/errordocs" 
>>> > Alias /favicon.ico 
>>> > 
>>> "/var/www/reviewboard.lcgentoo.local/htdocs/static/rb/images/favicon.png" 
>>> >  
>>> > === 
>>> > 
>>> > htdocs/reviewboard.wsgi 
>>> > === 
>>> > import __main__ 
>>> > __main__.__requires__ = ['ReviewBoard'] 
>>> > import pkg_resources 
>>> > 
>>> > import os 
>>> > import sys 
>>> > 
>>> > os.environ['DJANGO_SETTINGS_MODULE'] = "reviewboard.settings" 
>>> > os.environ['PYTHON_EGG_CACHE'] = 
>>> > "/var/www/reviewboard.lcgentoo.local/tmp/egg_cache" 
>>> > os.environ['HOME'] = "/var/www/reviewboard.lcgentoo.local/data" 
>>> > os.environ['PYTHONPATH'] = '/var/www/reviewboard.lcgentoo.local/conf:' 
>>> > + os.environ.get('PYTHONPATH', '') 
>>> > 
>>> > sys.path = ['/var/www/reviewboard.lcgentoo.local/conf'] + sys.path 
>>> > 
>>> > import django.core.handlers.wsgi 
>>> > application = django.core.handlers.wsgi.WSGIHandler() 
>>> > === 
>>> > 
>>> > /etc/apache2/vhosts.d/local.lcgentoo.reviewboard.vhost.conf 
>>> > === 
>>> >  
>>> >  
>>> > ServerName reviewboard.lcgentoo.local 
>>> > DocumentRoot "/var/www/reviewboard.lcgentoo.local/htdocs" 
>>> > 
>>> > SetEnv HOME /var/www/reviewboard.lcgentoo.local/data 
>>> > 
>>> > # Error handlers 
>>> > ErrorDocument 500 /errordocs/500.html 
>>> > 
>>> > # Serve django pages 
>>> > WSGIScriptAlias / 
>>> > /var/www/reviewboard.lcgentoo.local/htdocs/reviewboard.wsgi 
>>> >  
>>> > #SetHandler wsgi-script 
>>> > #Options +ExecCGI 
>>> > #PythonPath 
>>> > "['/var/www/reviewboard.lcgentoo.local/conf'] + sys.path" 
>>> > #SetEnv DJANGO_SETTINGS_MODULE reviewboard.settings 
>>> > #SetEnv PYTHON_EGG_CACHE 
>>> > "/var/www/reviewboard.lcgentoo.local/tmp/egg_cache" 
>>> > #SetHandler mod_python 
>>> > #PythonHandler django.core.handlers.modpython 
>>> > #PythonAutoReload Off 
>>> > #PythonDebug Off 
>>> > # Used to run multiple mod_python sites in the same 
>>> apache 
>>> > #PythonInterpreter 
>>> reviewboard_reviewboard_lcgentoo_local 
>>> >  
>>> > 
>>> > # Serve static media without running it through mod_python 
>>> > # (overrides the above) 
>>> >  
>>> > SetHandler None 
>>> >  
>>> > 
>>> > Alias /static 
>>> "/var/www/reviewboard.lcgentoo.local/htdocs/static" 
>>> >  
>>> > SetHandler None 
>>> >  
>>> >  
>>> > SetHandler None 
>>> >  
>>> > 
>>> >  
>>> > AllowOverride All 
>>> > Allow from all 
>>> >  
>>> > 
>>> > # Alias static media requests to filesystem 
>>> > Alias /media 
>>> "/var/www/reviewboard.lcgentoo.local/htdocs/media" 
>>> > Alias /errordocs 
>>> "/var/www/reviewboard.lcgentoo.local/htdocs/errordocs" 
>>> >  
>>> > 
>>> >  
>>> > === 
>

Re: "You are not logged in (HTTP 401, API Error 103)"

[Christian Hammond]

port sys
>> >
>> > os.environ['DJANGO_SETTINGS_MODULE'] = "reviewboard.settings"
>> > os.environ['PYTHON_EGG_CACHE'] =
>> > "/var/www/reviewboard.lcgentoo.local/tmp/egg_cache"
>> > os.environ['HOME'] = "/var/www/reviewboard.lcgentoo.local/data"
>> > os.environ['PYTHONPATH'] = '/var/www/reviewboard.lcgentoo.local/conf:'
>> > + os.environ.get('PYTHONPATH', '')
>> >
>> > sys.path = ['/var/www/reviewboard.lcgentoo.local/conf'] + sys.path
>> >
>> > import django.core.handlers.wsgi
>> > application = django.core.handlers.wsgi.WSGIHandler()
>> > ===
>> >
>> > /etc/apache2/vhosts.d/local.lcgentoo.reviewboard.vhost.conf
>> > ===
>> > 
>> > 
>> > ServerName reviewboard.lcgentoo.local
>> > DocumentRoot "/var/www/reviewboard.lcgentoo.local/htdocs"
>> >
>> > SetEnv HOME /var/www/reviewboard.lcgentoo.local/data
>> >
>> > # Error handlers
>> > ErrorDocument 500 /errordocs/500.html
>> >
>> > # Serve django pages
>> > WSGIScriptAlias /
>> > /var/www/reviewboard.lcgentoo.local/htdocs/reviewboard.wsgi
>> > 
>> > #SetHandler wsgi-script
>> > #        Options +ExecCGI
>> > #PythonPath
>> > "['/var/www/reviewboard.lcgentoo.local/conf'] + sys.path"
>> > #SetEnv DJANGO_SETTINGS_MODULE reviewboard.settings
>> > #SetEnv PYTHON_EGG_CACHE
>> > "/var/www/reviewboard.lcgentoo.local/tmp/egg_cache"
>> > #SetHandler mod_python
>> > #PythonHandler django.core.handlers.modpython
>> > #PythonAutoReload Off
>> > #PythonDebug Off
>> > # Used to run multiple mod_python sites in the same
>> apache
>> > #PythonInterpreter reviewboard_reviewboard_lcgentoo_local
>>
>> > 
>> >
>> > # Serve static media without running it through mod_python
>> > # (overrides the above)
>> > 
>> > SetHandler None
>> > 
>> >
>> > Alias /static "/var/www/reviewboard.lcgentoo.local/htdocs/static"
>>
>> > 
>> > SetHandler None
>> > 
>> > 
>> > SetHandler None
>> > 
>> >
>> > 
>> > AllowOverride All
>> > Allow from all
>> > 
>> >
>> > # Alias static media requests to filesystem
>> > Alias /media "/var/www/reviewboard.lcgentoo.local/htdocs/media"
>>
>> > Alias /errordocs 
>> > "/var/www/reviewboard.lcgentoo.local/htdocs/errordocs"
>>
>> > 
>> >
>> > 
>> > ===
>> >
>> > On Fri, Jan 9, 2015 at 7:30 AM, Christian Hammond
>> > <chri...@beanbaginc.com> wrote:
>> >> Hi Julian,
>> >>
>> >> Best bet would be to sprinkle some print statements throughout
>> rbtools/api/request.py. Particularly in ReviewBoardHTTPBasicAuthHandler,
>> ReviewBoardHTTPPasswordMgr, and PresetHTTPAuthHandler. See what's getting
>> triggered, what headers are being used, etc. Would take some investigation,
>> though... Wish I had a repro case :/
>> >>
>> >> Christian
>> >>
>> >> --
>> >> Christian Hammond - chri...@beanbaginc.com
>> >> Review Board - https://www.reviewboard.org
>> >> Beanbag, Inc. - https://www.beanbaginc.com
>> >>
>> >> -Original Message-
>> >> From: Julian Mehnle <jul...@mehnle.net>
>> >> Reply: revie...@googlegroups.com <revie...@googlegroups.com>>
>> >> Date: January 8, 2015 at 10:14:32 PM
>> >> To: revie...@googlegroups.com <revie...@googlegroups.com>>
>> >> Subject:  Re: "You are not logged in (HTTP 401, API Error 103)"
>> >>
>> >>> Christian,
>> >>>
>> >>> I wrote:
>> >>>
>> >>> > Christian Hammond wrote:
>> >>> >
>> >>> >> Did you used to use the old post-review tool? If so, can you see
>> if there's a .post-review-cookies.txt
>> >>> hanging around?
>> >>> >
>> >>> > That file doesn't exist in my home directory
>> (~/.post-review-cookies.txt).
>> >>> >
>> >>> >> It's a peculiar problem, I'll grant you that. Haven't seen this
>> before... It really
>> >>> should be prompting for a username/password if it doesn't have a
>> cookie.
>> >>> >
>> >>> > I googled for the error and it seems someone else ran into this
>> back in 2013, with no apparent
>> >>> resolution:
>> >>> >
>> >>> > https://groups.google.com/forum/#!msg/reviewboard/LbgYbA-
>> tQn4/tXxI7_v09rMJ
>> >>> >
>> >>> > I'm familiar with Python, so I can help debugging this if you give
>> me some guidance on
>> >>> where to start.
>> >>>
>> >>> Anything I can do to debug this?
>> >>>
>> >>> -Julian
>> >>>
>> >>> --
>> >>> Get the Review Board Power Pack at http://www.reviewboard.org/pow
>> erpack/
>> >>> ---
>> >>> Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
>> >>> ---
>> >>> Happy user? Let us know at http://www.reviewboard.org/users/
>> >>> ---
>> >>> You received this message because you are subscribed to the Google
>> Groups "reviewboard"
>> >>> group.
>> >>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to reviewboard...@googlegroups.com.
>> >>> For more options, visit https://groups.google.com/d/optout.
>> >>>
>> >>
>> >> --
>> >> Get the Review Board Power Pack at http://www.reviewboard.org/pow
>> erpack/
>> >> ---
>> >> Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
>> >> ---
>> >> Happy user? Let us know at http://www.reviewboard.org/users/
>> >> ---
>> >> You received this message because you are subscribed to the Google
>> Groups "reviewboard" group.
>> >> To unsubscribe from this group and stop receiving emails from it, send
>> an email to reviewboard...@googlegroups.com.
>> >> For more options, visit https://groups.google.com/d/optout.
>>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://www.reviewboard.org/users/
> ---
> You received this message because you are subscribed to the Google Groups
> "reviewboard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard+unsubscr...@googlegroups.com
> <javascript:_e(%7B%7D,'cvml','reviewboard%2bunsubscr...@googlegroups.com');>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
-- 
Christian Hammond
President/CEO of Beanbag <https://www.beanbaginc.com/>
Makers of Review Board <https://www.reviewboard.org/>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: "You are not logged in (HTTP 401, API Error 103)"

['Chris Westin' via reviewboard]

ewboard.lcgentoo.local 
> > DocumentRoot "/var/www/reviewboard.lcgentoo.local/htdocs" 
> > 
> > SetEnv HOME /var/www/reviewboard.lcgentoo.local/data 
> > 
> > # Error handlers 
> > ErrorDocument 500 /errordocs/500.html 
> > 
> > # Serve django pages 
> > WSGIScriptAlias / 
> > /var/www/reviewboard.lcgentoo.local/htdocs/reviewboard.wsgi 
> >  
> > #SetHandler wsgi-script 
> > #Options +ExecCGI 
> > #PythonPath 
> > "['/var/www/reviewboard.lcgentoo.local/conf'] + sys.path" 
> > #SetEnv DJANGO_SETTINGS_MODULE reviewboard.settings 
> > #SetEnv PYTHON_EGG_CACHE 
> > "/var/www/reviewboard.lcgentoo.local/tmp/egg_cache" 
> > #SetHandler mod_python 
> > #PythonHandler django.core.handlers.modpython 
> > #PythonAutoReload Off 
> > #PythonDebug Off 
> > # Used to run multiple mod_python sites in the same 
> apache 
> > #PythonInterpreter 
> reviewboard_reviewboard_lcgentoo_local 
> >  
> > 
> > # Serve static media without running it through mod_python 
> > # (overrides the above) 
> >  
> > SetHandler None 
> >  
> > 
> > Alias /static 
> "/var/www/reviewboard.lcgentoo.local/htdocs/static" 
> >  
> > SetHandler None 
> >  
> >  
> > SetHandler None 
> >  
> > 
> >  
> > AllowOverride All 
> > Allow from all 
> >  
> > 
> > # Alias static media requests to filesystem 
> > Alias /media "/var/www/reviewboard.lcgentoo.local/htdocs/media" 
> > Alias /errordocs 
> "/var/www/reviewboard.lcgentoo.local/htdocs/errordocs" 
> >  
> > 
> >  
> > === 
> > 
> > On Fri, Jan 9, 2015 at 7:30 AM, Christian Hammond 
> > <chri...@beanbaginc.com > wrote: 
> >> Hi Julian, 
> >> 
> >> Best bet would be to sprinkle some print statements throughout 
> rbtools/api/request.py. Particularly in ReviewBoardHTTPBasicAuthHandler, 
> ReviewBoardHTTPPasswordMgr, and PresetHTTPAuthHandler. See what's getting 
> triggered, what headers are being used, etc. Would take some investigation, 
> though... Wish I had a repro case :/ 
> >> 
> >> Christian 
> >> 
> >> -- 
> >> Christian Hammond - chri...@beanbaginc.com  
> >> Review Board - https://www.reviewboard.org 
> >> Beanbag, Inc. - https://www.beanbaginc.com 
> >> 
> >> -Original Message- 
> >> From: Julian Mehnle <jul...@mehnle.net > 
> >> Reply: revie...@googlegroups.com  <
> revie...@googlegroups.com >> 
> >> Date: January 8, 2015 at 10:14:32 PM 
> >> To: revie...@googlegroups.com  <revie...@googlegroups.com 
> >> 
> >> Subject:  Re: "You are not logged in (HTTP 401, API Error 103)" 
> >> 
> >>> Christian, 
> >>> 
> >>> I wrote: 
> >>> 
> >>> > Christian Hammond wrote: 
> >>> > 
> >>> >> Did you used to use the old post-review tool? If so, can you see if 
> there's a .post-review-cookies.txt 
> >>> hanging around? 
> >>> > 
> >>> > That file doesn't exist in my home directory 
> (~/.post-review-cookies.txt). 
> >>> > 
> >>> >> It's a peculiar problem, I'll grant you that. Haven't seen this 
> before... It really 
> >>> should be prompting for a username/password if it doesn't have a 
> cookie. 
> >>> > 
> >>> > I googled for the error and it seems someone else ran into this back 
> in 2013, with no apparent 
> >>> resolution: 
> >>> > 
> >>> > 
> https://groups.google.com/forum/#!msg/reviewboard/LbgYbA-tQn4/tXxI7_v09rMJ 
> >>> > 
> >>> > I'm familiar with Python, so I can help debugging this if you give 
> me some guidance on 
> >>> where to start. 
> >>> 
> >>> Anything I can do to debug this? 
> >>> 
> >>> -Julian 
> >>> 
> >>> -- 
> >>> Get the Review Board Power Pack at 
> http://www.reviewboard.org/powerpack/ 
> >>> --- 
> >>> Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ 
> >>> --- 
> >>> Happy user? Let us know at http://www.reviewboard.org/users/ 
> >>> --- 
> >>> You received this message because you are subscribed to the Google 
> Groups "reviewboard" 
> >>> group. 
> >>> To unsubscribe from this group and stop receiving emails from it, send 
> an email to reviewboard...@googlegroups.com . 
> >>> For more options, visit https://groups.google.com/d/optout. 
> >>> 
> >> 
> >> -- 
> >> Get the Review Board Power Pack at 
> http://www.reviewboard.org/powerpack/ 
> >> --- 
> >> Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ 
> >> --- 
> >> Happy user? Let us know at http://www.reviewboard.org/users/ 
> >> --- 
> >> You received this message because you are subscribed to the Google 
> Groups "reviewboard" group. 
> >> To unsubscribe from this group and stop receiving emails from it, send 
> an email to reviewboard...@googlegroups.com . 
> >> For more options, visit https://groups.google.com/d/optout. 
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: You are not logged in (HTTP 401, API Error 103)

[Gauthier Segay]

://www.beanbaginc.com

 -Original Message-
 From: Julian Mehnle jul...@mehnle.net
 Reply: reviewboard@googlegroups.com reviewboard@googlegroups.com
 Date: January 8, 2015 at 10:14:32 PM
 To: reviewboard@googlegroups.com reviewboard@googlegroups.com
 Subject:  Re: You are not logged in (HTTP 401, API Error 103)

 Christian,

 I wrote:

  Christian Hammond wrote:
 
  Did you used to use the old post-review tool? If so, can you see if 
  there's a .post-review-cookies.txt
 hanging around?
 
  That file doesn't exist in my home directory (~/.post-review-cookies.txt).
 
  It's a peculiar problem, I'll grant you that. Haven't seen this 
  before... It really
 should be prompting for a username/password if it doesn't have a cookie.
 
  I googled for the error and it seems someone else ran into this back in 
  2013, with no apparent
 resolution:
 
  https://groups.google.com/forum/#!msg/reviewboard/LbgYbA-tQn4/tXxI7_v09rMJ
 
  I'm familiar with Python, so I can help debugging this if you give me 
  some guidance on
 where to start.

 Anything I can do to debug this?

 -Julian

 --
 Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
 ---
 Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
 ---
 Happy user? Let us know at http://www.reviewboard.org/users/
 ---
 You received this message because you are subscribed to the Google Groups 
 reviewboard
 group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to reviewboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


 --
 Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
 ---
 Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
 ---
 Happy user? Let us know at http://www.reviewboard.org/users/
 ---
 You received this message because you are subscribed to the Google Groups 
 reviewboard group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to reviewboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: You are not logged in (HTTP 401, API Error 103)

[Julian Mehnle]

Christian,

I wrote:

 Christian Hammond wrote:
 
 Did you used to use the old post-review tool? If so, can you see if there's 
 a .post-review-cookies.txt hanging around?
 
 That file doesn't exist in my home directory (~/.post-review-cookies.txt).
 
 It's a peculiar problem, I'll grant you that. Haven't seen this before... It 
 really should be prompting for a username/password if it doesn't have a 
 cookie.
 
 I googled for the error and it seems someone else ran into this back in 2013, 
 with no apparent resolution:
 
 https://groups.google.com/forum/#!msg/reviewboard/LbgYbA-tQn4/tXxI7_v09rMJ
 
 I'm familiar with Python, so I can help debugging this if you give me some 
 guidance on where to start.

Anything I can do to debug this?

-Julian

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: You are not logged in (HTTP 401, API Error 103)

[Christian Hammond]

Hi Julian,

Best bet would be to sprinkle some print statements throughout 
rbtools/api/request.py. Particularly in ReviewBoardHTTPBasicAuthHandler, 
ReviewBoardHTTPPasswordMgr, and PresetHTTPAuthHandler. See what's getting 
triggered, what headers are being used, etc. Would take some investigation, 
though... Wish I had a repro case :/

Christian

--  
Christian Hammond - christ...@beanbaginc.com  
Review Board - https://www.reviewboard.org  
Beanbag, Inc. - https://www.beanbaginc.com

-Original Message-
From: Julian Mehnle jul...@mehnle.net
Reply: reviewboard@googlegroups.com reviewboard@googlegroups.com
Date: January 8, 2015 at 10:14:32 PM
To: reviewboard@googlegroups.com reviewboard@googlegroups.com
Subject:  Re: You are not logged in (HTTP 401, API Error 103)

 Christian,
  
 I wrote:
  
  Christian Hammond wrote:
 
  Did you used to use the old post-review tool? If so, can you see if 
  there's a .post-review-cookies.txt  
 hanging around?
 
  That file doesn't exist in my home directory (~/.post-review-cookies.txt).
 
  It's a peculiar problem, I'll grant you that. Haven't seen this before... 
  It really  
 should be prompting for a username/password if it doesn't have a cookie.
 
  I googled for the error and it seems someone else ran into this back in 
  2013, with no apparent  
 resolution:
 
  https://groups.google.com/forum/#!msg/reviewboard/LbgYbA-tQn4/tXxI7_v09rMJ  
 
  I'm familiar with Python, so I can help debugging this if you give me some 
  guidance on  
 where to start.
  
 Anything I can do to debug this?
  
 -Julian
  
 --
 Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
 ---
 Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
 ---
 Happy user? Let us know at http://www.reviewboard.org/users/
 ---
 You received this message because you are subscribed to the Google Groups 
 reviewboard  
 group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to reviewboard+unsubscr...@googlegroups.com.  
 For more options, visit https://groups.google.com/d/optout.
  

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: You are not logged in (HTTP 401, API Error 103)

[Julian Mehnle]

Christian Hammond christ...@beanbaginc.com wrote:

 You're not able to post to either our server or your internal one?

Unable to post to either. Exact same error message.

 Are you posting using the official upstream build of RBTools, or one from 
 your source tree? I just want to rule out any issues there.

Using the official one, version 0.6.3.

 Are you behind any kind of proxy server that could potentially be interfering?
 
 If you delete the .rbtools-cookies file and run rbt post, does it prompt you 
 for credentials, or does it just try without them?

No proxy. If I delete .rbtools-cookies and run `rbt post`, it does *not* prompt 
for credentials (I understand it *should*), but it just fails. Afterwards 
there's a new .rbtools-cookies file that looks like this:

 -8-
 # Netscape HTTP Cookie File
 # http://curl.haxx.se/rfc/cookie_spec.html
 # This is a generated file!  Do not edit.
 
 -8-

-Julian

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: You are not logged in (HTTP 401, API Error 103)

[Christian Hammond]

Did you used to use the old post-review tool? If so, can you see if there's a 
.post-review-cookies.txt hanging around?

I'm not sure that's actually the problem in this case, but I just want to rule 
it out.

It's a peculiar problem, I'll grant you that. Haven't seen this before... It 
really should be prompting for a username/password if it doesn't have a cookie.

Christian

--  
Christian Hammond - christ...@beanbaginc.com  
Review Board - https://www.reviewboard.org  
Beanbag, Inc. - https://www.beanbaginc.com

-Original Message-
From: Julian Mehnle jul...@mehnle.net
Reply: reviewboard@googlegroups.com reviewboard@googlegroups.com
Date: January 6, 2015 at 3:22:53 PM
To: reviewboard@googlegroups.com reviewboard@googlegroups.com
Subject:  Re: You are not logged in (HTTP 401, API Error 103)

 Christian Hammond wrote:
  
  You're not able to post to either our server or your internal one?
  
 Unable to post to either. Exact same error message.
  
  Are you posting using the official upstream build of RBTools, or one from 
  your source  
 tree? I just want to rule out any issues there.
  
 Using the official one, version 0.6.3.
  
  Are you behind any kind of proxy server that could potentially be 
  interfering?
 
  If you delete the .rbtools-cookies file and run rbt post, does it prompt 
  you for credentials,  
 or does it just try without them?
  
 No proxy. If I delete .rbtools-cookies and run `rbt post`, it does *not* 
 prompt for credentials  
 (I understand it *should*), but it just fails. Afterwards there's a new 
 .rbtools-cookies  
 file that looks like this:
  
  -8-
  # Netscape HTTP Cookie File
  # http://curl.haxx.se/rfc/cookie_spec.html
  # This is a generated file! Do not edit.
 
  -8-
  
 -Julian
  
 --
 Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
 ---
 Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
 ---
 Happy user? Let us know at http://www.reviewboard.org/users/
 ---
 You received this message because you are subscribed to the Google Groups 
 reviewboard  
 group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to reviewboard+unsubscr...@googlegroups.com.  
 For more options, visit https://groups.google.com/d/optout.
  

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: You are not logged in (HTTP 401, API Error 103)

[Julian Mehnle]

Christian Hammond wrote:

 Did you used to use the old post-review tool? If so, can you see if there's a 
 .post-review-cookies.txt hanging around?

That file doesn't exist in my home directory (~/.post-review-cookies.txt).

 It's a peculiar problem, I'll grant you that. Haven't seen this before... It 
 really should be prompting for a username/password if it doesn't have a 
 cookie.

I googled for the error and it seems someone else ran into this back in 2013, 
with no apparent resolution:

https://groups.google.com/forum/#!msg/reviewboard/LbgYbA-tQn4/tXxI7_v09rMJ

I'm familiar with Python, so I can help debugging this if you give me some 
guidance on where to start.

Thanks,

-Julian

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: You are not logged in (HTTP 401, API Error 103)

[Christian Hammond]

Hey Julian,

You're not able to post to either our server or your internal one?

Are you posting using the official upstream build of RBTools, or one from your 
source tree? I just want to rule out any issues there.

Are you behind any kind of proxy server that could potentially be interfering?

If you delete the .rbtools-cookies file and run rbt post, does it prompt you 
for credentials, or does it just try without them?

Christian

--  
Christian Hammond - christ...@beanbaginc.com  
Review Board - https://www.reviewboard.org  
Beanbag, Inc. - https://www.beanbaginc.com

-Original Message-
From: Julian Mehnle jul...@mehnle.net
Reply: reviewboard@googlegroups.com reviewboard@googlegroups.com
Date: January 6, 2015 at 2:59:25 PM
To: reviewboard@googlegroups.com reviewboard@googlegroups.com
Subject:  You are not logged in (HTTP 401, API Error 103)

 Hi all,
  
 I'm having trouble using rbt on the command line. No matter what I do, 
 anything that requires  
 interaction with the Review Board server gives me a You are not logged in 
 (HTTP 401, API  
 Error 103):
  
  joule:~/tmp/rbtools.orig rbt --version
  RBTools 0.6.3
  joule:~/tmp/rbtools.orig git log --stat master ^origin/master | more
  commit 86dc0ab71c20a599c33efa7ea694c12281fe8ef6
  Author: Julian Mehnle  
  Date: Tue Jan 6 22:45:19 2015 +
 
  When raising CommandError, include lower-level exception.
 
  rbtools/commands/__init__.py | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
  joule:~/tmp/rbtools.orig rbt post --debug -g
   RBTools 0.6.3
   Python 2.7.9 (default, Dec 13 2014, 15:13:49)
  [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.56)]
   Running on Darwin-14.0.0-x86_64-i386-64bit
   Home = /Users/julian
   Current directory = /Users/julian/tmp/rbtools.orig
   Checking for a Subversion repository...
   Running: svn info --non-interactive
   Command exited with rc 1: ['svn', 'info', '--non-interactive']
  svn: E155007: '/Users/julian/tmp/rbtools.orig' is not a working copy
  ---
   Checking for a Git repository...
   Running: git rev-parse --git-dir
   Running: git config core.bare
   Running: git rev-parse --show-toplevel
   Running: git symbolic-ref -q HEAD
   Running: git config --get branch.master.merge
   Running: git config --get branch.master.remote
   Running: git config --get remote.origin.url
   repository info: Path: git://github.com/reviewboard/rbtools.git, Base 
   path:  
 , Supports changesets: False
   Making HTTP GET request to https://reviews.reviewboard.org/api/
   Running: git rev-parse refs/heads/master
   Running: git merge-base 86dc0ab71c20a599c33efa7ea694c12281fe8ef6 
   origin/master  
   Running: git rev-parse bcb7629c0be773b6f347a5006224825b8726c479
   Running: git status --porcelain --untracked-files=no
   Running: git diff --no-color --full-index --ignore-submodules 
   bcb7629c0be773b6f347a5006224825b8726c479..86dc0ab71c20a599c33efa7ea694c12281fe8ef6
 
 -M --no-ext-diff
   Running: git log --reverse --pretty=format:%s%n%n%b 
   ^bcb7629c0be773b6f347a5006224825b8726c479  
 86dc0ab71c20a599c33efa7ea694c12281fe8ef6
   Making HTTP GET request to 
   https://reviews.reviewboard.org/api/review-requests/  
   Making HTTP POST request to 
   https://reviews.reviewboard.org/api/review-requests/  
   Got API Error 103 (HTTP code 401): You are not logged in
   Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged 
   in', u'code':  
 103}}
  Traceback (most recent call last):
  File /usr/local/bin/rbt, line 9, in  
  load_entry_point('RBTools==0.6.3', 'console_scripts', 'rbt')()
  File 
  /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/RBTools-0.6.3-py2.7.egg/rbtools/commands/main.py,

 line 134, in main
  command.run_from_argv([RB_MAIN, command_name] + args)
  File 
  /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/RBTools-0.6.3-py2.7.egg/rbtools/commands/__init__.py,

 line 416, in run_from_argv
  exit_code = self.main(*args) or 0
  File 
  /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/RBTools-0.6.3-py2.7.egg/rbtools/commands/post.py,

 line 791, in main
  submit_as=self.options.submit_as)
  File 
  /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/RBTools-0.6.3-py2.7.egg/rbtools/commands/post.py,

 line 507, in post_request
  raise CommandError(Error creating review request: %s % e)
  rbtools.commands.CommandError: Error creating review request: You are not 
  logged  
 in (HTTP 401, API Error 103)
  
  
 I've tried removing ~/.rbtools-cookies, as well as specifying --username and 
 --password  
 on the command line, to no avail. I've tried both posting to 
 https://reviews.reviewboard.org  
 and my company's internal Review Board server (running RB 1.7.19. I'm running 
 Python  
 2.7.9 on Mac OS X 10.10.1.
  
 I'm not sure what triggered this. How should I go about debugging this?
  
 -Julian
  
 --
 Get 

Re: You are not logged in

[fishgills]

Hey, just a bump since I added the log. Sorry to be annoying!


On Tuesday, February 26, 2013 12:13:29 PM UTC-8, Charlie Davis wrote:

 Hey all...

 I've been a RB user for quite some time and recently upgraded my RB to 
 1.7.whatever-the-newest-is.

 I haven't been able to post a review though and here's my command line 
 output:

 Charlies-MacBook-Pro:~ cdavis$ post-review --debug 30628
  RBTools 0.4.3
  Python 2.7.2 (default, Jun 20 2012, 16:23:33) 
 [GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)]
  Running on Darwin-12.2.0-x86_64-i386-64bit

 lots of stuff here...

  HTTP POSTing to 
 http://reviewboard.hq.cashview.com/api/review-requests/: {'changenum': 
 '30628', 'repository': u'perforce.hq.cashview.com:1666'}
 == HTTP Authentication Required
 Enter authorization information for Web API at 
 reviewboard.hq.cashview.com
 Username: cdavis
 Password: 
  Got API Error 103 (HTTP code 401): You are not logged in
  Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged 
 in', u'code': 103}}
  Attempting to create review request on perforce.hq.cashview.com:1666for 
  30628
  HTTP POSTing to 
 http://reviewboard.hq.cashview.com/api/review-requests/: {'changenum': 
 '30628', 'repository': u'perforce.hq.cashview.com:1666'}
  Got API Error 103 (HTTP code 401): You are not logged in
  Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged 
 in', u'code': 103}}
  Attempting to create review request on perforce.hq.cashview.com:1666for 
  30628
  HTTP POSTing to 
 http://reviewboard.hq.cashview.com/api/review-requests/: {'changenum': 
 '30628', 'repository': u'perforce.hq.cashview.com:1666'}
  Got API Error 103 (HTTP code 401): You are not logged in
  Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged 
 in', u'code': 103}}
  Attempting to create review request on perforce.hq.cashview.com:1666for 
  30628
  HTTP POSTing to 
 http://reviewboard.hq.cashview.com/api/review-requests/: {'changenum': 
 '30628', 'repository': u'perforce.hq.cashview.com:1666'}
  Got API Error 103 (HTTP code 401): You are not logged in
  Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged 
 in', u'code': 103}}
 Error creating review request: You are not logged in (HTTP 401, API Error 
 103)

 And the contents of .post-review-cookies.txt:

 Charlies-MacBook-Pro:~ cdavis$ cat .post-review-cookies.txt 
 # Netscape HTTP Cookie File
 # http://www.netscape.com/newsref/std/cookie_spec.html
 # This is a generated file!  Do not edit.

 Charlies-MacBook-Pro:~ cdavis$ 


 If I delete this file and try again, it still dies.

 Any ideas?


 I'm able to log into the actual RB site just fine and see all my old 
 reviews and what not.

 -Charlie



-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: You are not logged in

[Christian Hammond]

Hey,

Sorry, I didn't see your log before.

So one of a few things looks to be happening:

1) Your credentials aren't being accepted or aren't what you think they are.
2) The cookie isn't being set for the proper domain (you can look at your 
~/.post-review-cookies.txt to see)
2) You may have something in-between the client and Review Board that's for 
some reason stripping/breaking cookies.

If this were a bug in RBTools, it'd probably be showing up a lot more, so I 
think it's a config issue. Hopefully the above checklist can help narrow that 
down.

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com

On Feb 27, 2013, at 11:25 AM, Charlie Davis fishgi...@fishgills.net wrote:

 -

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: You are not logged in

[Charlie Davis]

For sure. Here you go!



display-1:~ cdavis$ post-review --debug 30663
 RBTools 0.4.3
 Python 2.7.2 (default, Jun 20 2012, 16:23:33) 
[GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)]
 Running on Darwin-12.2.0-x86_64-i386-64bit
 Home = /Users/cdavis
 Current Directory = /Users/cdavis
 Checking the repository type. Errors shown below are mostly harmless.
DEBUG:root:Checking for a Bazaar repository...
DEBUG:root:Checking for a CVS repository...
DEBUG:root:Checking for a ClearCase repository...
DEBUG:root:Checking for a Git repository...
DEBUG:root:Checking for a Mercurial repository...
DEBUG:root:Checking for a Perforce repository...
DEBUG:root:Running: p4 info
DEBUG:root:Running: diff --version
DEBUG:root:repository info: Path: ['build.hq.cashview.com:1666', 
'15.10.1.10.in-addr.arpa:1666', 'perforce.hq.cashview.com:1666'], Base 
path: None, Supports changesets: True
 Finished checking the repository type.
DEBUG:root:Running: p4 counters
 HTTP GETting api/info/
INFO:root:Generating diff for changenum 30663
DEBUG:root:Running: p4 describe -s 30663
DEBUG:root:Processing edit of //app/1010/htdocs/css/base/ui.css
DEBUG:root:Writing //app/1010/htdocs/css/base/ui.css#36 to 
/var/folders/93/6yfcq0fx5_55mpr7rdh0cc98gn/T/tmpXcj_RS
DEBUG:root:Running: p4 print -o 
/var/folders/93/6yfcq0fx5_55mpr7rdh0cc98gn/T/tmpXcj_RS -q 
//app/1010/htdocs/css/base/ui.css#36
DEBUG:root:Running: diff -urNp 
/var/folders/93/6yfcq0fx5_55mpr7rdh0cc98gn/T/tmpXcj_RS 
/Users/cdavis/Documents/BDC/App/1010-Root/Charlies_1010/app/1010/htdocs/css/base/ui.css
DEBUG:root:Command exited with rc 1: ['diff', '-urNp', 
'/var/folders/93/6yfcq0fx5_55mpr7rdh0cc98gn/T/tmpXcj_RS', 
'/Users/cdavis/Documents/BDC/App/1010-Root/Charlies_1010/app/1010/htdocs/css/base/ui.css']
--- /var/folders/93/6yfcq0fx5_55mpr7rdh0cc98gn/T/tmpXcj_RS 2013-02-27 
11:22:32.0 -0800
+++ 
/Users/cdavis/Documents/BDC/App/1010-Root/Charlies_1010/app/1010/htdocs/css/base/ui.css
 2013-02-27 
10:58:47.0 -0800
@@ -651,7 +651,7 @@ div#inboxDDUpload.threecol div.zde {
  margin-top: 30px;
 }
 div#inboxDDUpload div.fileselect { 
- width: 295px;
+ width: 300px;
  margin-right: 80px;
 }
 
---
DEBUG:root:Processing edit of //app/1010/htdocs/css/partners/pnc/main.css
DEBUG:root:Writing //app/1010/htdocs/css/partners/pnc/main.css#7 to 
/var/folders/93/6yfcq0fx5_55mpr7rdh0cc98gn/T/tmpXcj_RS
DEBUG:root:Running: p4 print -o 
/var/folders/93/6yfcq0fx5_55mpr7rdh0cc98gn/T/tmpXcj_RS -q 
//app/1010/htdocs/css/partners/pnc/main.css#7
DEBUG:root:Running: diff -urNp 
/var/folders/93/6yfcq0fx5_55mpr7rdh0cc98gn/T/tmpXcj_RS 
/Users/cdavis/Documents/BDC/App/1010-Root/Charlies_1010/app/1010/htdocs/css/partners/pnc/main.css
DEBUG:root:Command exited with rc 1: ['diff', '-urNp', 
'/var/folders/93/6yfcq0fx5_55mpr7rdh0cc98gn/T/tmpXcj_RS', 
'/Users/cdavis/Documents/BDC/App/1010-Root/Charlies_1010/app/1010/htdocs/css/partners/pnc/main.css']
--- /var/folders/93/6yfcq0fx5_55mpr7rdh0cc98gn/T/tmpXcj_RS 2013-02-27 
11:22:32.0 -0800
+++ 
/Users/cdavis/Documents/BDC/App/1010-Root/Charlies_1010/app/1010/htdocs/css/partners/pnc/main.css
 2013-02-27 
11:12:43.0 -0800
@@ -186,9 +186,10 @@ div.mouseOverTip {
  font-style: normal;
 }
 div#inboxDDUpload div.fileselect input[type=file] {
- width: 192px;
+ width: 243px;
 }
 div#inboxDDUpload div.target  {
+ left: 377px;
 }
 div#inboxDDUpload div.ddinstruct {
 }
@@ -234,4 +235,16 @@ div#modal_overlay {
 }
 div#modal_overlay div.title, div#modal_overlay div.control {
  background-image: url(/css/partners/pnc/modal-sprite-clear.png);
+}
+.link, a:link, a:visited, a {
+ color: #3399cc;
+}
+
+div#inboxDDUpload div.fileselect {
+ margin-right: 78px;
+ width: 350px;
+}
+
+div#inboxDDUpload div.ddinstruct {
+ margin-left: 0px;
 }
\ No newline at end of file
---
 HTTP GETting api/
 HTTP GETting http://reviewboard.hq.cashview.com/api/info/
 Using the new web API
 HTTP GETting http://reviewboard.hq.cashview.com/api/repositories/
 Repositories on Server: [{u'path': u'perforce.hq.cashview.com:1666', 
u'tool': u'Perforce', u'id': 1, u'links': {u'info': {u'href': 
u'http://reviewboard.hq.cashview.com/api/repositories/1/info/', u'method': 
u'GET'}, u'self': {u'href': 
u'http://reviewboard.hq.cashview.com/api/repositories/1/', u'method': 
u'GET'}, u'update': {u'href': 
u'http://reviewboard.hq.cashview.com/api/repositories/1/', u'method': 
u'PUT'}, u'delete': {u'href': 
u'http://reviewboard.hq.cashview.com/api/repositories/1/', u'method': 
u'DELETE'}}, u'name': u'app_1010'}]
 Server Aliases: ['build.hq.cashview.com:1666', 
'15.10.1.10.in-addr.arpa:1666', 'perforce.hq.cashview.com:1666']
 Attempting to create review request on perforce.hq.cashview.com:1666 
for 30663
 HTTP POSTing to 

Re: You are not logged in

[Christian Hammond]

Hi Charlie,

Strange. Think you can post the entire debug log? I need to see all the steps 
it's going through.

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com

On Feb 26, 2013, at 12:13 PM, Charlie Davis fishgi...@fishgills.net wrote:

 Hey all...
 
 I've been a RB user for quite some time and recently upgraded my RB to 
 1.7.whatever-the-newest-is.
 
 I haven't been able to post a review though and here's my command line output:
 
 Charlies-MacBook-Pro:~ cdavis$ post-review --debug 30628
  RBTools 0.4.3
  Python 2.7.2 (default, Jun 20 2012, 16:23:33) 
 [GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)]
  Running on Darwin-12.2.0-x86_64-i386-64bit
 
 lots of stuff here...
 
  HTTP POSTing to http://reviewboard.hq.cashview.com/api/review-requests/: 
  {'changenum': '30628', 'repository': u'perforce.hq.cashview.com:1666'}
 == HTTP Authentication Required
 Enter authorization information for Web API at reviewboard.hq.cashview.com
 Username: cdavis
 Password: 
  Got API Error 103 (HTTP code 401): You are not logged in
  Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged in', 
  u'code': 103}}
  Attempting to create review request on perforce.hq.cashview.com:1666 for 
  30628
  HTTP POSTing to http://reviewboard.hq.cashview.com/api/review-requests/: 
  {'changenum': '30628', 'repository': u'perforce.hq.cashview.com:1666'}
  Got API Error 103 (HTTP code 401): You are not logged in
  Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged in', 
  u'code': 103}}
  Attempting to create review request on perforce.hq.cashview.com:1666 for 
  30628
  HTTP POSTing to http://reviewboard.hq.cashview.com/api/review-requests/: 
  {'changenum': '30628', 'repository': u'perforce.hq.cashview.com:1666'}
  Got API Error 103 (HTTP code 401): You are not logged in
  Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged in', 
  u'code': 103}}
  Attempting to create review request on perforce.hq.cashview.com:1666 for 
  30628
  HTTP POSTing to http://reviewboard.hq.cashview.com/api/review-requests/: 
  {'changenum': '30628', 'repository': u'perforce.hq.cashview.com:1666'}
  Got API Error 103 (HTTP code 401): You are not logged in
  Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged in', 
  u'code': 103}}
 Error creating review request: You are not logged in (HTTP 401, API Error 103)
 
 And the contents of .post-review-cookies.txt:
 
 Charlies-MacBook-Pro:~ cdavis$ cat .post-review-cookies.txt 
 # Netscape HTTP Cookie File
 # http://www.netscape.com/newsref/std/cookie_spec.html
 # This is a generated file!  Do not edit.
 
 Charlies-MacBook-Pro:~ cdavis$ 
 
 
 If I delete this file and try again, it still dies.
 
 Any ideas?
 
 
 I'm able to log into the actual RB site just fine and see all my old reviews 
 and what not.
 
 -Charlie
 
 
 -- 
 Want to help the Review Board project? Donate today at 
 http://www.reviewboard.org/donate/
 Happy user? Let us know at http://www.reviewboard.org/users/
 -~--~~~~--~~--~--~---
 To unsubscribe from this group, send email to 
 reviewboard+unsubscr...@googlegroups.com
 For more options, visit this group at 
 http://groups.google.com/group/reviewboard?hl=en
 --- 
 You received this message because you are subscribed to the Google Groups 
 reviewboard group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to reviewboard+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.