Opened 14 years ago

Closed 14 years ago

#1886 closed defect (fixed)

mythbackend gets stuck when the database disappears

Reported by: chrisb@… Owned by: Isaac Richards
Priority: critical Milestone: unknown
Component: mythtv Version: 0.19
Severity: high Keywords:
Cc: Ticket locked: no

Description

Sorry if this bug has already been reported, but I was unable to find it using the search..

Using mythtv version: 0.19.20060121-2

If the MySQL server goes down while mythbackend is running, it appears to get stuck in an infinite loop. It fills the log with the following message repeated every few milliseconds:

2006-05-28 16:41:44.730 DB Error (insert_program -- lock): Query was: LOCK TABLES recorded WRITE No error type from QSqlError? Strange... QSqlQuery::prepare: database not open QSqlQuery::exec: database not open 2006-05-28 16:41:44.741 DB Error (insert_program -- lock): Query was: LOCK TABLES recorded WRITE No error type from QSqlError? Strange... QSqlQuery::prepare: database not open QSqlQuery::exec: database not open 2006-05-28 16:41:44.754 DB Error (insert_program -- lock): Query was: LOCK TABLES recorded WRITE No error type from QSqlError? Strange... QSqlQuery::prepare: database not open QSqlQuery::exec: database not open

Even after the database comes back up, the situation is not resolved. From the looks of it, at no point does it attempt to reconnect to the database, but instead just retries the same query over and over again on the old dead database connection.

Change History (1)

comment:1 Changed 14 years ago by Isaac Richards

Resolution: fixed
Status: newclosed

(In [10532]) Make insert_program reconnect if the db con's died.

Fixes #1886.

Note: See TracTickets for help on using tickets.