[mythtv-users] myth://192.168.205.3:6543/1063_20080919100000.mpg doesn't work
knowledgejunkie at gmail.com
Tue Sep 23 03:24:59 UTC 2008
On 22/09/2008, Marc MERLIN <marc_mtv at merlins.org> wrote:
> On Mon, Sep 22, 2008 at 04:25:05PM +0100, Nick Morrott wrote:
> > On 22/09/2008, Marc MERLIN <marc_mtv at merlins.org> wrote:
> > > I also just got this when restarting mythtv-backend:
> > >
> > > To: root at merlins.org
> > >
> > > mythconverg.recordmatch
> > > warning : Table is marked as crashed and last repair failed
> > >
> > > Any idea if that's related and what I'm supposed to do in a case like this?
> > How did you attempt to repair the database initially? Did you run the
> > optimize_mythdb.pl script? You will need to fix the database as a
> > priority.
> /usr/bin/mysqlcheck --defaults-file=/etc/mysql/debian.cnf -all-databases --fast --silent
> I ran optimize_mythdb.pl as you suggested, it outputted nothing and the
> error looks gone now.
> However I still can't play old recordings on my slave backend:
> 2008-09-22 09:29:07.525 PlaybackBox::showActions(): Error, myth://192.168.205.3:6543/1003_20080920232900.mpg file not found
If you want to check in the database (take a backup first just in case):
mysql> SELECT DISTINCT `hostname` FROM `recorded` ORDER BY `hostname`;
This will list the different hosts that MythTV think recordings are
stored on. If there are any disparities here between 'what was' and
'what is', you will get problems. Does the backend where you believe
the missing file to reside agree have an IP address of '192.168.205.3'
If you reference this message with my reply to another of your
messages, you may begin to see how your machines' identities are
stored in the MythTV database.
MythTV Official wiki:
MythTV users list archive:
"An investment in knowledge always pays the best interest." - Benjamin Franklin
More information about the mythtv-users