[mythtv-users] 0.22 Backend client protocol

[Dave D]

Just figured it out..   mythlcdserver was still running.  I guess it doesn't
get killed upon mythfrontend exit.

Why is it not killed?  Also, is it possible to have the error message be
more specific about which client is using the bad protocol?

In any case.. hopefully this helps others!

On Thu, Nov 5, 2009 at 7:26 AM, Dave D <dave726 at gmail.com> wrote:

> Hi everyone,
>
> I recently upgraded to 0.22 r22740 (at least 0.22 RC2).  I have a brand new
> database created on the first mythtv-setup run... updated all my capture
> card/schedules direct information there, ran mythfilldatabase... everything
> went smooth.
>
> When I run mythbackend, however, I get the following output about every 10
> seconds:
>
> 2009-11-05 07:10:52.819 MainServer::HandleVersion - Client speaks protocol
> version 40 but we speak 50!
> 2009-11-05 07:10:52.819 MainServer, Warning: Unknown socket closing
> MythSocket(0x826f728)
>
> I don't have any mythfrontends running during this time.. I'm not sure what
> is meant by "client" in this context.
>
>
> any help would be much appreciated.  I had to watch
> <gulp>commercials</gulp> last night!! :-)
>
>
> thanks,
>  - Dave
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20091105/f6a77dec/attachment.htm>