Project

General

Profile

Bug #1404

Tissue robot looses connection to MISCOMP

Added by Randy Reitz over 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Start date:
06/27/2011
Due date:
09/15/2011
% Done:

0%

Estimated time:
Duration: 81

Description

The MISCOMP database "disappears" daily at ~4:30AM. The Tissue robots are daemon processes
which keep a connection open to MISCOMP. When MISCOMP is unavailable, the robot daemon
senses the dead MISCOMP connection and tries to get a new connection. Failure to get a new
MISCOMP connection generates an "IMPORTANT ERROR LOG ENTRY FROM TISSUE"
email. As the robot continues to retry, a new email is generated for each connection attempt.
When MISCOMP becomes available, the emails stop. However, by this time several hundred emails have
been generated. The Tissue robot needs to delay before trying a MISCOMP reconnect,
and send a warning email after X connection attempts fail.

History

#1 Updated by Randy Reitz over 8 years ago

When Tissue email robot looses it's MISCOMP connection, it doesn't reacquire the connection. This seems to be the real problem.

#2 Updated by Randy Reitz about 8 years ago

  • Due date set to 09/15/2011
  • Status changed from New to Resolved
  • Assignee set to Lauri Carpenter

Change singleton pattern to not request database connection on instantiation.

Use Django exception handling middleware (contrib) to refresh connection on any database error.

#3 Updated by Randy Reitz about 8 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF