Ubuntu
mythtv package

  1. Bug #330272
  2. Comment #22

Comment 22 for bug 330272

Revision history for this message
Roy Thompson (roy-haematic) wrote :

This is a log file with -v important,eit,siparser
snippet just before sql error appears again:

QSqlQuery::exec: empty query
2009-08-31 17:11:02.522 PESPacket: Failed CRC check 0x22161100 != 0xc3bfa4b5 for StreamID = 0x70
QSqlQuery::exec: empty query
QSqlQuery::exec: empty query
QSqlQuery::exec: empty query
QSqlQuery::exec: empty query
QSqlQuery::exec: empty query
2009-08-31 17:11:03.181 EITScanner (1): Added 28 EIT Events
QSqlQuery::exec: empty query
QSqlQuery::exec: empty query
QSqlQuery::exec: empty query
QSqlQuery::exec: empty query
QSqlQuery::exec: empty query
222yyyy-22MM-22dd 22hh:22mm:22ss.22zzz DB Error (Update next_record):
Query was:
UPDATE record SET next_record = '0000-00-00T00:00:00' WHERE recordid = :RECORDID;
Bindings were:
:RECORDID=143
Driver error was [2/1064]:
QMYSQL3: Unable to execute query
Database error was:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ':RECORDID' at line 1

full log file attached.
observations: can't see anything particularly different just before that error happens. There are lots of "PESPacket: Failed CRC check" messages, but those happened from soon after backend is started up not just when it fails.
After it starts to happen, all messages are prefixed with 222yyyy-22MM-22dd 22hh:22mm:22ss.22zzz rather than the correct date+timestamp.