Closed
Bug 755232
Opened 12 years ago
Closed 12 years ago
Can not log in due to browser id internal error 500
Categories
(Marketplace Graveyard :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 762326
People
(Reporter: orvils, Unassigned)
References
Details
(Keywords: qawanted, Whiteboard: [qa+])
Attachments
(1 file)
(deleted),
image/png
|
Details |
When loging in I get alert with the followinf content
<div class="">
<section class="primary">
<header>
<h1>Oops! We had an error.</h1>
</header>
<div class="island hero prose">
<p>We'll get to fixing that soon.</p>
<p>
You can try refreshing the page, or try again later.
</p>
</div>
</section>
</div>
Firebug console says that https://marketplace.mozilla.org/en-US/users/browserid-login has Internal server error 500
Reporter | ||
Comment 2•12 years ago
|
||
Yes, I still have this problem.
Comment 4•12 years ago
|
||
(In reply to Wil Clouser [:clouserw] from comment #3)
> Krupa - can you reproduce this?
Log in wfm. I suspect that this is user account specific or related to the duplicate user issue. I checked in Sentry and so did cvan and we found nothing.
Raivis,
Can you help us debug this? We are all available on #amo in IRC or if you tell us the exact time you tried logging in, we can check the logs to see if there's anything fishy.
Reporter | ||
Comment 5•12 years ago
|
||
Glad to help.
I tried to log in from ip 195.244.135.199 just now. That is Friday, May 18, 2012 at 5:34:03 AM GMT
If that doesn't help I'll find you on IRC
Comment 6•12 years ago
|
||
Wil, I never saw anything in Sentry. Anything in the logs?
Comment 7•12 years ago
|
||
Nothing from May 18 at 5:30am. Raivis: we're in #amo on irc.mozilla.org
Updated•12 years ago
|
OS: Windows 7 → All
Hardware: x86_64 → All
Reporter | ||
Comment 8•12 years ago
|
||
Could be something with the browser ID as i think that i can not log in anywhere with my browser id
Comment 9•12 years ago
|
||
I spoke with Raivis on IRC and it appears that registering and logging in with a separate BrowserID account worked okay.
This issue (which looks like a CSRF failure) persisted in Chrome as well. It would appear that this issue is tied to something weird with the email account used. CC'ing James on BrowserID QA to investigate. (Feel free to PM for Ravis' email.)
Comment 10•12 years ago
|
||
So, marketplace points to browserid.org I think (which is Production).
I need full details on how to repro this because I have never seen this before.
Platform, OS, browser and very detailed steps would help.
From there, if it persists with one BID account but no other we can have take a look at what is happening for that specific account/email.
Would help if you could repeat same steps with the following:
1. Same BID account but with same email
2. a new BID account with new email
3. a new BID account with original email (if it will let you)
If you can reproduce 100% with the same account/email combination but no other, then hop onto #identity and let us know - we can watch logs from the BID side of things while you attempt to log in.
Reporter | ||
Comment 11•12 years ago
|
||
Deleted my browser id account and created a new one. The problem is still there.
My email is in the mozilla LDAP or other systems. This might be connected in some way. Will hang around in IRC #identity later today.
Reporter | ||
Comment 12•12 years ago
|
||
Tried the following experiment:
1. Deleted old BID account and created new one
2. Logged into BID on https://browserid.org/
3. Tried to log in to the Marketplace and got an error
Time 2012.5.31 at about 8:33 PDT
Comment 13•12 years ago
|
||
Yep, so we need to look at the logs from the Marketplace side again.
He can successfully log straight into/out of https://browserid.org with his email account and no errors are shown on the client or in the logs.
Can we have marketplace OPs look again in the logs for the following timeframe:
2012.05.31
8:00am - 8:30am PDT
Whiteboard: [qa+]
Comment 14•12 years ago
|
||
I see these in the logs, but they are just incomplete tracebacks (an example of why you don't want to send tracebacks to syslog). The complete tracebacks from sentry should give some great clues.
May 31 08:30:44 web8.addons.phx1.mozilla.com: [][] django.request:ERROR /en-US/users/browserid-login Internal Server Error: /en-US/users/browserid-login :/data/www/addons.mozilla.org/zamboni/vendor/src/django/django/core/handlers/base.py:209#012Traceback (most recent call last):#012 File "/data/www/addons.mozilla.org/zamboni/vendor/src/django/django/core/handlers/base.py", line 111, in get_response#012 response = callback(request, *callback_args, **callback_kwargs)#012 File "/data/www/addons.mozilla.org/zamboni/apps/amo/decorators.py", line 50, in wrapper#012 return f(request, *args, **kw)#012 File "/data/www/addons.mozilla.org/zamboni/vendor/src/django/django/db/transaction.py", line 211, in inner#012 return func(*args, **kwargs)#012 File "/data/www/addons.mozilla.org/zamboni/apps/users/views.py", line 367, in browserid_login#012 assertion=request.POST['assertion'])#012 File "/data/www/addons.mozilla.org/zamboni/apps/users/views.py", line 343, in browserid_authenticate#012 profile.create_django_user()#012 File "/data/www/addons.mozilla.org/zamboni/apps/users/models.py", line 342, in create_django_user#012 self.user.save()#012 File "/data/www/addons.mozilla.org/zamboni/vendor/src/django/django/db/models/base.py", line 463, in save#012 self.save_base(using=using, force_insert=force_insert, force_update=force_update)#012 File "/data/www/addons.mozilla.org/zamboni/vendor/src/django/django/db/models/base.py", line 556, in save_base#012 result = manager._insert(values, return_id=update_pk, using=using)#012 File "/data/www/addons.mozilla.org/zamboni/vendor/src/django/django/db/models/manager.py", line 198, in _insert#012 return insert_query(self.model, values, **kwargs)#012 File "/data/www/addons.mozilla.org/zamboni/vendor/src/django/django/db/models/query.py", line 1448, in insert_query#012 return query.get_compiler(using=using).execute_sql(return_id)#012 File "/data/www/addons.mozilla.org/zamboni/vendor/src/django/django/db/models/sql/compiler.py", line 806, in e
May 31 08:30:44 web8.addons.phx1.mozilla.com: [][] django.request:ERROR Internal Server Error: /en-US/users/browserid-login :/data/www/addons.mozilla.org/zamboni/vendor/src/django/django/core/handlers/base.py:209#012Traceback (most recent call last):#012 File "/data/www/addons.mozilla.org/zamboni/vendor/src/django/django/core/handlers/base.py", line 111, in get_response#012 response = callback(request, *callback_args, **callback_kwargs)#012 File "/data/www/addons.mozilla.org/zamboni/apps/amo/decorators.py", line 50, in wrapper#012 return f(request, *args, **kw)#012 File "/data/www/addons.mozilla.org/zamboni/vendor/src/django/django/db/transaction.py", line 211, in inner#012 return func(*args, **kwargs)#012 File "/data/www/addons.mozilla.org/zamboni/apps/users/views.py", line 367, in browserid_login#012 assertion=request.POST['assertion'])#012 File "/data/www/addons.mozilla.org/zamboni/apps/users/views.py", line 343, in browserid_authenticate#012 profile.create_django_user()#012 File "/data/www/addons.mozilla.org/zamboni/apps/users/models.py", line 342, in create_django_user#012 self.user.save()#012 File "/data/www/addons.mozilla.org/zamboni/vendor/src/django/django/db/models/base.py", line 463, in save#012 self.save_base(using=using, force_insert=force_insert, force_update=force_update)#012 File "/data/www/addons.mozilla.org/zamboni/vendor/src/django/django/db/models/base.py", line 556, in save_base#012 result = manager._insert(values, return_id=update_pk, using=using)#012 File "/data/www/addons.mozilla.org/zamboni/vendor/src/django/django/db/models/manager.py", line 198, in _insert#012 return insert_query(self.model, values, **kwargs)#012 File "/data/www/addons.mozilla.org/zamboni/vendor/src/django/django/db/models/query.py", line 1448, in insert_query#012 return query.get_compiler(using=using).execute_sql(return_id)#012 File "/data/www/addons.mozilla.org/zamboni/vendor/src/django/django/db/models/sql/compiler.py", line 806, in execute_sql#012 cursor = su
Comment 15•12 years ago
|
||
I just reproduced this bug on Marketplace. I can consistently reproduce this with one of my accounts
If you want account info ping me on IRC
Comment 16•12 years ago
|
||
bug 762326 has the details about the traceback.
Updated•12 years ago
|
Priority: -- → P3
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•