Occasionally an OperationalError is raised (usually? always? when trying to log in) claiming "server closed the connection unexpectedly", or something to that effect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Resonate |
Confirmed
|
Low
|
Unassigned |
Bug Description
I think we ought to deal with this by catching OperationalError exceptions at the higher levels of the web stack, and check to see if it mentions something like "server closed the connection unexpectedly"; and, if so, try to process the request once more...
Here's an example stack trace...
File "/home/
ret = view_func(request, *args, **kwargs)
File "/home/
user = authenticate(
File "/home/
user = User.get_
File "/home/
instance = query.filter_
File "/home/
ret = list(self[0:1])
...
File "/home/
cursor.
OperationalError: (OperationalError) FATAL: terminating connection due to administrator command
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
'SELECT users.id AS users_id, users.username AS users_username, users._
Changed in resonate: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in resonate: | |
importance: | High → Medium |
Changed in resonate: | |
importance: | Medium → Low |