[mythtv-users] backend won't record - MYTH_PROTO_VERSION problems
Michael T. Dean
mtdean at thirdcontact.com
Fri Dec 2 03:01:20 EST 2005
Mark Knecht wrote:
>On 12/1/05, Michael T. Dean <mtdean at thirdcontact.com> wrote:
>>Mark Knecht wrote:
>>> I take care of two back end machine. One is here at my place, the
>>>other is remote. At the remote location mythbackend has stopped making
>>>recordings. When I run the frontend in a terminal I see this:
>>>2005-12-01 09:29:28.705 ReadStringList timeout (quick).
>>>2005-12-01 09:29:28.705 Unexpected response to MYTH_PROTO_VERSION:
>>>error querying master in ProgramList::FromScheduler
>>>2005-12-01 09:30:13.320 Connecting to backend server: 192.168.1.2:6543
>>>(try 1 of 5)
>>>2005-12-01 09:30:33.328 ReadStringList timeout (quick).
>>>2005-12-01 09:30:33.329 Unexpected response to MYTH_PROTO_VERSION:
>>>error resceduling id 77 in ScheduledRecording::signalChange
>>>2005-12-01 09:30:33.333 Connecting to backend server: 192.168.1.2:6543
>>> Browsing around I found a common reason is a mixed frontend/backend
>>>setup. Mine are not. Both the fronend and backend are 0.18.1.
>>I highly recommend digging deeper. Are they really 0.18.1 (perhaps one
>>is 0.18-fixes SVN). If a combined frontend/backend, check your paths
>>(perhaps you have one version is /usr/local and another is /usr).
> Thanks for the response. I think you are onto something:
>gandalf ~ # slocate ivtv-detect
>gandalf ~ # ls -al /usr/bin/ivtv-detect
>-rwxr-xr-x 1 root root 7000 Nov 25 10:34 /usr/bin/ivtv-detect
>gandalf ~ # ls -al /usr/local/bin/ivtv-detect
>-rwxr-xr-x 1 root root 11312 Aug 14 14:15 /usr/local/bin/ivtv-detect
>gandalf ~ #
> At some earlier date the machine was running ivtv-0.3.7 from
>source. With the kernel update I started using ivtv-0.4.0 from
>portage. This was installed at Thanksgiving. It looks like the source
>install placed things in /usr/local/bin while portage placed it in
> While I cannot yet be 100% sure this is the problem, it's certainly
>badly configured and needs to be fixed.
True that it needs fixed, but it wouldn't cause a protocol version
mismatch--only differing versions of mythbackend and client (like
mythfrontend or MythWeb) would do that.
More information about the mythtv-users