[mythtv-users] Re: There's definitely something wrong.....somewhere....(thousands of mysql errors in backend log)

[Dave Parker]

I think I've answered my own question - I'm providing it here for
completeness:  it appears that my recordedmarkup table had some
corruption issues.  This was causing the considerable logging as well
as some serious problems with playback in that programs were
"skipping" a lot.

mysqlcheck --user=mythtv --password=<pass> mythconverg --analyze

yielded:

mythconverg.recordedmarkup
error    : Key in wrong position at page 8107008
error    : Corrupt

mysqlcheck --user=mythtv --password=<pass> mythconverg --repair

yielded: 

mythconverg.recordedmarkup
warning  : Number of rows changed from 761611 to 761606
status   : OK

Problem appears now to be solved.

I suspect that mysqld died for lack of memory a few days ago when I
had swap turned off and ran something really huge.  So I guess -
lesson to the wise: don't do that.

Rrrrrgh - lots of corrupted STOS episodes :(


On Mon, 16 Aug 2004 22:56:58 -0700, Dave Parker <daveparker01 at gmail.com> wrote:
> I've noticed that in the last few days I've begun to see thousands and
> thousands of messages like this in my mythbackend log:
> 
> DB Error (position map insert):
> Query was:
> INSERT INTO recordedmarkup (chanid, starttime, mark, type, offset)
> values ( '1244', '20040816224200', 238, 6, "78063654");
> Driver error was [2/1062]:
> QMYSQL3: Unable to execute query
> Database error was:
> Duplicate entry '1244-20040816224200-238-6' for key 1