Revision history [back]
I believe this is a caching problem. Note that the issue is intermittent, and is triggered particularly if one signs in, then out, and then back in.
More info: at ask.sagemath.org, this issue appeared after a server move and upgrade to askbot 0.7.51. At the new server, we are forced to use unix sockets instead of tcp ports for communication between the server (nginx) and cache. (Also for communication between the server and uwsgi.) We had trouble getting askbot to acknowledge memcached with a unix socket, and are therefore using a filesystem cache. Could this be causing the problem?
Update
Similar behavior was reported here: http://askbot.org/en/question/10173/google-sign-in-does-not-work/ and was apparently resolved by using memcached.
I believe this is a caching problem. Note that the issue is intermittent, and is triggered particularly if one signs in, then out, and then back in.
More info: at ask.sagemath.org, this issue appeared after a server move and upgrade to askbot 0.7.51. At the new server, we are forced to use unix sockets instead of tcp ports for communication between the server (nginx) and cache. (Also for communication between the server and uwsgi.) We had trouble getting askbot to acknowledge memcached with a unix socket, and are therefore using a filesystem cache. Could this be causing the problem?
Update
Similar behavior was reported here: http://askbot.org/en/question/10173/google-sign-in-does-not-work/ and was apparently resolved by using memcached.