Earlier today, we got a report of the production app throwing 503 errors but the errors went away shortly after. At first glance, it appears that the user in question was logged in at the time and at approximately the same time, the following error showed up on blockerbugs02:

Nov 20 15:30:58 blockerbugs02 app 2013-11-20 15:30:58 ERROR Exception on /admin/ [GET]#012Traceback (most recent call last):#012 File "/usr/lib/python2.6/site-packages/flask/app.py", line 1687, in wsgi_app#012 response = self.full_dispatch_request()#012 File "/usr/lib/python2.6/site-packages/flask/app.py", line 1360, in full_dispatch_request#012 rv = self.handle_user_exception(e)#012 File "/usr/lib/python2.6/site-packages/flask/app.py", line 1358, in full_dispatch_request#012 rv = self.dispatch_request()#012 File "/usr/lib/python2.6/site-packages/flask/app.py", line 1344, in dispatch_request#012 return self.view_functionsrule.endpoint#012 File "/usr/lib/python2.6/site-packages/flask_admin/base.py", line 49, in inner#012 abort = self._handle_view(f.name, **kwargs)#012 File "/usr/lib/python2.6/site-packages/blockerbugs/controllers/admin/init.py", line 43, in _handle_view#012 return check_admin_rights()#012 File "/usr/lib/python2.6/site-packages/blockerbugs/controllers/users.py", line 52, in check_admin_rights#012 return fas.login()#012 File "/usr/lib/python2.6/site-packages/flask_fas_openid.py", line 129, in login#012 if 'next' in args.values:#012NameError: global name 'args' is not defined

I suspect that something may be mishandled with login when the load balancer sends traffic to the node on which the user did not login initially, but this is just a suspicion - the issue still needs triage.