Last modified: 2014-10-12 17:55:55 UTC
On Beta Labs enwiki, attempting to create an account gives (in the red error box): --- Account creation error There was an unexpected error logging in. Please try again. If the problem persists, it may be because you have cookies disabled, and you should check that they are enabled in your browser settings. ---
Matt: Do you have access to the Beta Cluster? If not, you should. Then can you poke around the logs and see if anything pops out?
I think I have the necessary access. I'm not planning to take this (at least not tonight), though.
S Page said he was able to create an account, but it then redirected to the a page that said, "You are already logged in as Spage test account 2".
Mini rant: Those with production deploy privs should have access to the beta cluster (if not, I'll add you right now) and should be able to and should feel explicitly encouraged to debug issues they run into on the beta cluster just as they would on production. The beta cluster can only survive if we all contribute to it (see: the people resource difference between prod and beta cluster and the lack of real complexity difference).
(not complaining about you two specifically, Matthew/S, just something that's been on my mind for a while about making our test infrastructure sustainable/usable and this just was related.)
Can someone test this for me now?
(In reply to Sam Reed (reedy) from comment #6) > Can someone test this for me now? Yeah, still the same symptoms for me. Any information I can provide that would help?
Not sure straight off. Memcached was in somewhat of a mess on beta, which was spamming the hell out of the logs. I sorta presumed that it was related, but that is now fixed up (at least for the mediawiki app servers)
If it helps, when I do the following, I get a different error: 1. Clear all Beta Labs cookies. 2. Go to http://en.wikipedia.beta.wmflabs.org/ 3. Click Log in 4. Click Create account 5. Complete form and submit. In that case, I get: ----- Account creation error There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Go back to the previous page, reload that page and then try again. -----
(In reply to Matthew Flaschen from comment #9) > If it helps, when I do the following, I get a different error: > > 1. Clear all Beta Labs cookies. > 2. Go to http://en.wikipedia.beta.wmflabs.org/ > 3. Click Log in > 4. Click Create account > 5. Complete form and submit. > > In that case, I get: > > ----- > Account creation error > > There seems to be a problem with your login session; this action has been > canceled as a precaution against session hijacking. Go back to the previous > page, reload that page and then try again. > ----- Lego: Any ideas?
(In reply to Matthew Flaschen from comment #0) > There was an unexpected error logging in. This is 'nocookieslogin', with a message override (http://en.wikipedia.beta.wmflabs.org/wiki/MediaWiki:Nocookieslogin). (In reply to Matthew Flaschen from comment #9) > There seems to be a problem with your login session This is 'sessionfailure'. Both of these are core messages, but it's possible CentralAuth is involved in the error somehow.
Seems to be affecting production now...
I can reproduce this on mediawiki.org.
Change 166267 had a related patch set uploaded by Legoktm: Fix sesion failure errors when trying to create an account https://gerrit.wikimedia.org/r/166267
Change 166269 had a related patch set uploaded by Legoktm: Fix session failure errors when trying to create an account https://gerrit.wikimedia.org/r/166269
Should probably be backported ASAP.
Change 166267 merged by jenkins-bot: Fix session failure errors when trying to create an account https://gerrit.wikimedia.org/r/166267
Change 166269 merged by jenkins-bot: Fix session failure errors when trying to create an account https://gerrit.wikimedia.org/r/166269
Should be fixed on beta already automatically, and also fixed on production as I've merged the backports and deployed them
(In reply to Sam Reed (reedy) from comment #19) > as I've merged the backports and deployed them Setting flag accordingly.
