[mythtv-users] Strange Issue with Myth and HDHomeRun

John Welch jrw3319 at gmail.com
Wed Feb 14 13:41:13 UTC 2007

On 2/13/07, f-myth-users at media.mit.edu <f-myth-users at media.mit.edu> wrote:
> Where exactly is your database?
> As a PVR-x50 user who's been getting screwed for a year by glitches
> caused by MySQL locking winding up locking out other table accesses,
> this is a sore spot.
> I'm assuming that the HDHR isn't trying to write into recordedmarkup
> or its SVN incarnation (unlike the ivtv-based encoders), but I'm
> wondering if perhaps there's something wrong with your database
> (like crashed or extremely un-optimized tables) that's either causing
> outright disk contention, or lots of swapping that is itself screwing
> your ability to write to disk.  So you might try repairing and
> optimizing tables (if you don't already) and see if that helps.
> And of course the FE makes large transient demands on the database,
> hence my suspicion.  Is your DB on the master backend's CPU?  Same
> disk, or a different disk?  (In -my- case, of course, it made no
> difference, since it was the DB locking itself that was a problem and
> not contention for disk bandwidth, but this wasn't obvious for most of
> a year.)  Is your backend swapping a lot?  Can you try moving your
> database to a completely different machine to run a test?
> (You can accomplish this latter, essentially, by shutting down MySQL,
> copying its files to some other machine -with a compatible version-
> installed [don't recklessly switch MySQL versions if you're just
> copying raw database files w/o import/export!], and changing the
> config file on your backend to point to whichever host now has the DB.)
> P.S.  If your test system is using the MySQL server on your production
> backend, of course, you're splitting things off in a way that might
> cause the test system to work fine while the production machine is
> encountering contention issues...

Thanks for the suggestion concerning the database.  Another thing I had not
thought of.  My installation of myth is right from the ATrpms packages, so
wherever the database is installed by default is where mine is located.
It's definitely on the same system (CPU) as the B/E.  On the test system I
did not point it to the database on the B/E; this was a fresh install of
Myth, just taking the defaults.

A couple of questions for clarification purposes:
You say shutdown MySql and copy it's files to another machine.  Are you
referring to just the database files, or do I also need to copy over my
actual recordings?  Also, since the other machine won't have the tuner cards
in it, how will myth react to having these cards, and all associated info,
in the database, but not being able to physically access them?  Will this
cause any issues?

You also say that the FE makes large transient demands on the database.  Are
you referring to a remote FE system, or just the FE functions (LiveTV, Watch
Recordings, Schedule Recordings, etc.) in general?  Because when I do these
functions directly on the BE machine I don't get any corruption; at least
that has been what I have seen so far.  This is one of the things that
really has me confused.  It's only when I connect up to the BE with a FE
running on another machine that I have problems.

Thanks again,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20070214/c3e81d27/attachment-0001.htm 

More information about the mythtv-users mailing list