Closed Bug 699865 Opened 13 years ago Closed 13 years ago

[traceback] [prod] Exception: Authentication for new user

Categories

(Participation Infrastructure :: Phonebook, defect)

defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: mbrandt, Assigned: tofumatt)

References

()

Details

(Whiteboard: [1.1.2])

This is not consistently happening but I was able to reproduce the behavior twice. There are also ~ 20 traceback from the last 18 hours with similar stack traces.

Steps to reproduce:
1. got to /register
2. create a new account
3. click submit

Actual:
500 error

root@localhost.seamicro.phx1.mozilla.com
	
10:57 AM (3 minutes ago)
		
to aking, tofumatt, mbrandt, jthomas
Traceback (most recent call last):

 File "/data/www/mozillians.org/mozillians/vendor/src/django/django/core/handlers/base.py", line 111, in get_response
   response = callback(request, *callback_args, **callback_kwargs)

 File "/data/www/mozillians.org/mozillians/vendor/src/django-session-csrf/session_csrf/__init__.py", line 107, in wrapper
   response = f(request, *args, **kw)

 File "/data/www/mozillians.org/mozillians/apps/users/views.py", line 83, in register
   _save_new_user(request, form)

 File "/data/www/mozillians.org/mozillians/apps/users/views.py", line 188, in _save_new_user
   raise Exception(msg)

Exception: Authentication for new user (####@####.com) failed
Flags: in-testsuite?
A bit of additional information. After the account creation process errors out subsequent tries to create the account fail with the message that the email address is already registered.

I used this disposable email address --> a10078141@nepwk.com

 - Additionally the verification email is not being sent, thus locking this email
 - Using the login process to have the verification sent also appears to fail and 
   the email is not being sent.
Severity: major → blocker
I've gotten about 5 reports of this. Matt or Dave, do you know what might be causing this?
I think I created some of these tracebacks, attempting to sign up with the email "duke@leto.net". I think they may be related to esoteric characters in passwords, since I had to crank down the entropy/charsets in my password generator to make the account creation succeed.
Whiteboard: [1.1.1]
Whiteboard: [1.1.1] → [1.1.2]
Assignee: nobody → tofumatt
Target Milestone: --- → 1.1
Summary: [prod] Exception: Authentication for new user → traceback] [prod] Exception: Authentication for new user
Duke: Any insights into what characters you think were causing the issues? I've on my dev server with some pretty weird unicode characters and huge pws and things still work.
Target Milestone: 1.1 → ---
I am curious what is the server/form allowing for as acceptable email addresses?
ie are ., _, -, @ allowed?  Also for the password, what is allowed?  Are !, #, $, % &, etc. allowed?
Summary: traceback] [prod] Exception: Authentication for new user → [traceback] [prod] Exception: Authentication for new user
https://github.com/mozilla/mozillians/commit/944a70ce81e9b251d151f5212923986a2c575cb5

This should solve the issue and log, in our graphite setup, when/where/how often the problems are happening.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.1
> [This will] cut down on 500s and log what/when/where things are happening.
:tofumatt Does this mean graphite will trap the tracebacks or will they still be sent out via traceback emails?
This will prevent those exceptions from happening as much as possible. That means there shouldn't be any tracebacks unless things are royally hosed. If things break we'll still get tracebacks.

Errors that only happen a few times will be caught, the process will be attempted again, and that fact will be logged in graphite. If it NEVER works that will be logged and we'll get a traceback.
(In reply to Matthew Riley MacPherson [:tofumatt] from comment #11)
> Errors that only happen a few times will be caught, the process will be
> attempted again, and that fact will be logged in graphite. If it NEVER works
> that will be logged and we'll get a traceback.
Excellent.

Knocking to QA verified. Account creation and verification work without the original notorious 500's during the registration process. Righteous fix

[13:35:31.899] GET https://mozillians-dev.allizom.org/en-US/login [HTTP/1.1 200 OK 9251ms]
[13:35:41.630] GET https://mozillians-dev.allizom.org/media/css/common-min.css?build=aae9e51 [HTTP/1.1 304 Not Modified 22ms]
[13:35:41.645] GET https://mozillians-dev.allizom.org/en-US/jsi18n/ [HTTP/1.1 200 OK 5662ms]
[13:35:41.657] GET https://mozillians-dev.allizom.org/media/js/common-min.js?build=aae9e51 [HTTP/1.1 304 Not Modified 2882ms]
Status: RESOLVED → VERIFIED
It doesn't work 

- it is not related to the browser or addons : same results with chrome and IE
- and not to the french version : I get the same with the english site
Hey sav123, mind letting us know which version of the site (staging or production) you were testing on and a bit more info (URL, time of request if you recall).

(If you aren't sure which version of the site you were using it's probably production.)

This is a server-side error that browsers wouldn't affect, but it's only fixed on non-production boxes.
Hi Matthew

I use https://mozillians.org/fr/login or https://mozillians.org/login

It works now !
I got a confirmation email and I'm registred

many thanks
I'm having the same error as sav123 but I get Sorry, but we couldn't create your account. Please review the form, correct any errors, and try again. and  Someone has already registered an account with feer56@sumoconnect.com.
Component: mozillians.org → Phonebook
Product: Websites → Community Tools
QA Contact: mozillians-org → phonebook
Target Milestone: 1.1 → ---
Version: unspecified → other
You need to log in before you can comment on or make changes to this bug.