[mythtv-users] Unexpected response toMYTH_PROTO_VERSION'MYTH_PROTO_VERSION 13'

[Kane Tse]

> -----Original Message-----
> From: mythtv-users-bounces at mythtv.org 
> [mailto:mythtv-users-bounces at mythtv.org] On Behalf Of David Shay
> Sent: Tuesday, January 04, 2005 12:17 PM
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] Unexpected response 
> toMYTH_PROTO_VERSION'MYTH_PROTO_VERSION 13'
> 
> 
> Does your remote backend share an NFS combined directory or 
> is it separate?

My remote/master backend shares a NFS directory with all other frontends
and one slave backend.

> In my case I have a separate backend and 
> occasionally see this, but it us about 90% tied to accessing 
> the "Recorded Programs" page on MythWeb.  The other 10% of 
> the time it happens without any Mythweb access at all.

I also suspect that my problem is somehow triggered by MythWeb.  Here is
an approximately schedule of events that happened today (but this is not
the first time this has happened)

8:15 AM
Look through the list of recordings to find today's news show, set to
record at 6 AM this morning.  I can see the list of recordings fine, but
I couldn't find my recorded program, so I watch a live TV on the remote
frontend instead.  This particular remote frontend has its own encoder.

8:20 AM 
While still watching the program, access MythWeb from another PC to
check out today's recording schedule.  The first page of MythWeb that
shows the TV listings for the current date/time works fine.

8:21 AM
On MythWeb, click on the to the "Recorded Programs" page to find the
missing recording.  Page takes a long time to load, and eventually dies
with "Unexpected response to MYTH_PROTO_VERSION 'MYTH_PROTO_VERSION
13'".

8:30 AM
Finished watching Live TV on the remote frontend, but the frontend has
lost the connection to the remote backend.  The list of recordings is
now blank.

8:31 AM
I SSH into the remote master backend and restart mythbackend.

The thing is that mythbackend was set to record a news program at 6 AM
this morning, but didn't.  That's why I was going through MythWeb to see
what was going on.  It seems like some unknown error occurs within
Mythbackend at some point, and the programs are no longer recorded...
And eventually this is seen as a "Unexpected response to
MYTH_PROTO_VERSION 'MYTH_PROTO_VERSION 13'" the next time one access the
MythWeb Recorded Programs interface.


>  For 
> the Mythweb piece, have you turned on verbose logging?  See bug 107:
> 
> http://www.mythtv.org/bugs/show_bug.cgi?id=107
> 

I read through the bug report; but I am not sure how to turn on verbose
logging for Mythweb.

I also following a link on that report to bug #89
(http://www.mythtv.org/bugs/show_bug.cgi?id=89) and I had that "Waiting
for thread..." error as well...  I thought that this error was due to
the fact that my slave backend was transcoding an MPEG-2 to MPEG-4 and
then I turned off the slave backend machine; causing the remote master
backend to wait infinitely for the slave backend to finish
transcoding...

Thanks!


> ----- Original Message ----- 
> From: "Kane Tse" <kanetse at hotmail.com>
> To: <mythtv-users at mythtv.org>
> Sent: Tuesday, January 04, 2005 2:15 PM
> Subject: [mythtv-users] Unexpected response to 
> MYTH_PROTO_VERSION'MYTH_PROTO_VERSION 13'
> 
> 
> >
> > I have MythTV-0.16 installed on a dual Athlon MP 1900+ 
> system running 
> > Fedora Core 3 system.  This system is running as a remote backend.
> >
> > When the backend first starts up, everything works fine.  Shows are 
> > recorded, the system status can be viewed through MythWeb, 
> and remote 
> > frontends can watch shows over the network without any problem.
> >
> > After an unknown period of time (which ranges from a few hours to a 
> > few days), the backend becomes unresponsive, and stops recording 
> > shows.  The frontends usually report (in their console output) 
> > "Unexpected response to MYTH_PROTO_VERSION 
> 'MYTH_PROTO_VERSION 13'".  
> > MythWeb also gives this error when trying to access it.  I 
> checked the 
> > mythbackend.log file, but there is nothing to indicate any 
> error has 
> > arisen.
> >
> > I am certain that all the frontends and backends are 
> running matching 
> > versions of MythTV (0.16), since I got them from ATrpms; 
> and this is 
> > confirmed by the console output message when mythfrontend starts up 
> > 0.16.20040906-1.
> >
> > Does anyone know what causes this error?  Or how I can prevent it?
> >
> > Thanks!
> >