Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Dev

protocol version 22 / 23

 

 

MythTV dev RSS feed   Index | Next | Previous | View Threaded


jppoet at gmail

Jan 15, 2006, 9:56 AM

Post #1 of 5 (1051 views)
Permalink
protocol version 22 / 23

I updated to the current SVN yesterday, and very quickly had problems
with the backend not responding to the frontend. It would work for a
while, but after an hour or so, there would be problems.

Looking at the log, I see a lot of:

MainServer::HandleVersion - Client speaks protocol version 22 but
we speak 23!

I get that error even when all clients (frontend, mythcommflag,
mythweb) are shut down, and the ONLY thing running is the master
backend.

How do I diagnose this problem? How do I figure out what "client" is
causing the problem?

Thanks,

John
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


mark at dclabs

Jan 15, 2006, 2:29 PM

Post #2 of 5 (1006 views)
Permalink
Re: protocol version 22 / 23 [In reply to]

distclean and rebuild from scratch. you should know better :)
cheers
mark

>I updated to the current SVN yesterday, and very quickly had problems
> with the backend not responding to the frontend. It would work for a
> while, but after an hour or so, there would be problems.
>
> Looking at the log, I see a lot of:
>
> MainServer::HandleVersion - Client speaks protocol version 22 but
> we speak 23!
>
> I get that error even when all clients (frontend, mythcommflag,
> mythweb) are shut down, and the ONLY thing running is the master
> backend.
>
> How do I diagnose this problem? How do I figure out what "client" is
> causing the problem?

_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


jppoet at gmail

Jan 15, 2006, 2:44 PM

Post #3 of 5 (1018 views)
Permalink
Re: protocol version 22 / 23 [In reply to]

On 1/15/06, Mark Spieth <mark [at] dclabs> wrote:
> distclean and rebuild from scratch. you should know better :)
> cheers
> mark

Except, I did not do a "svn update", but a "svn co".

I will try a distclean, but I don't expect it to fix the problem.

Thanks for replying.

John
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


mark at dclabs

Jan 15, 2006, 4:49 PM

Post #4 of 5 (1011 views)
Permalink
Re: protocol version 22 / 23 [In reply to]

>> distclean and rebuild from scratch. you should know better :)
>> cheers
>> mark
>
> Except, I did not do a "svn update", but a "svn co".
>
> I will try a distclean, but I don't expect it to fix the problem.
>
the other problem I usually have is that I forget to update the frontend
after I did the backend so they match.

mark

_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


jppoet at gmail

Jan 15, 2006, 11:19 PM

Post #5 of 5 (1002 views)
Permalink
Re: protocol version 22 / 23 [In reply to]

On 1/15/06, Mark Spieth <mark [at] dclabs> wrote:
> >> distclean and rebuild from scratch. you should know better :)
> >> cheers
> >> mark
> >
> > Except, I did not do a "svn update", but a "svn co".
> >
> > I will try a distclean, but I don't expect it to fix the problem.
> >
> the other problem I usually have is that I forget to update the frontend
> after I did the backend so they match.
>
> mark

You were almost right. I *had* shutdown mythfrontend. What I had not
done, was shutdown mythlcdserver. Not even sure why it was running,
since I don't use it -- yet.

Thanks Mark,

John
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

MythTV dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.