[mythtv-users] help: i can't record tv after upgrade to ubuntu-13.04/mythtv-0.26

[Michael T. Dean]

On 06/26/2013 07:32 PM, raf wrote:
> hi,
>
> i use the mythtv that comes with ubuntu and just upgraded from
> ubuntu-12.10/mythtv-0.25 to ubuntu-13.04/mythtv-0.26
> (specifically 2:0.26.0+fixes.20121118.340b5d4-0ubuntu1).
>
> anyway, the initial upgrade was a disaster. it looked like the
> mythconverg schema was upgraded by mythtv-setup but nothing worked
> because mythbackend also thought it needed to upgrade the schema
> but thought it wasn't "allowed" to do so it would terminate immediately.
>
> i reloaded the backup and started again and it seems slightly better.
> possibly because i ran mythtv-setup as the mythtv user this time
> rather than just running mythfrontend with my own user account.
> it still forgot everything about my tv tuners and video and music
> directories and all of my recording instructions but that would be
> ok if it weren't for the remaining problems.
>
> i would really appreciate any suggestions to remedy the following
> problems:
>
> 1) mythfrontend can't terminate. when i try, it asks if i really want
> to. i tell it yes and then it just sits there until i kill the
> process some other way. the last thing it writes to its log file
> before hanging is:
>
>    I CoreContext bonjourregister.cpp:26 (~BonjourRegister)
>    Bonjour: De-registering service '_airplay._tcp.' on 'MythTV on HOSTNAME'
>
> is there any way i can tell it not to register/de-register this service?
> or to make it able to de-register the service. i'm not using this
> service.
>
> 2) i am unable to create any recording instructions in mythfrontend
> using the programme guide. when i try, i go through the motions and
> there are no error indications but when complete, there is no visual
> indication that the programme will be recorded and when i go back
> in to check the recording status of the programme in question, it
> says it will not be recorded.
>
> the messages that appear in the logfile when i try to record a programme
> look like:
>
> mythbackend.log:
>   E CoreContext mythsocket.cpp:520 (readStringList)
>     MythSocket(8c08298:60): readStringList: Error, timed out after 30000 ms.
>   E CoreContext mainserver.cpp:6184 (reconnectTimeout)
>     MainServer: Failed to open master server socket, timeout
>   I ProcessRequest mainserver.cpp:1445 (HandleAnnounce)
>     adding: HOSTNAME as a slave backend server
>   W ProcessRequest mainserver.cpp:5841 (connectionClosed)
>     MainServer: Unknown socket closing MythSocket(0x8c08298)
>   E ProcessRequest mythsocket.cpp:344 (writeStringList)
>     MythSocket(8c08298:-1): writeStringList: Error, socket went
>     unconnected.#012#011#011#011We wrote 0 of 10 bytes
>     with 1 errors#012#011#011#011starts with: 2       OK
>   N CoreContext mainserver.cpp:6129 (reconnectTimeout)
>     Connecting to master server: 10.0.0.1:6543
>   N CoreContext mainserver.cpp:6147 (reconnectTimeout)
>     Connected successfully
>
>   this might be a coincidence. these messages repeat evey 31 seconds.
>   either way, it doesn't look good.
>
> mythfrontend.log:
>
>   A ScreenLoad programinfo.cpp:4522 (LoadFromScheduler)
>     LoadFromScheduler(): Error querying master.
>   I Reconnect mythcorecontext.cpp:375 (ConnectCommandSocket)
>     MythCoreContext: Connecting to backend server: 10.0.0.1:6543 (try 1 of 1)
>   E Reconnect mythsocket.cpp:520 (readStringList)
>     MythSocket(ffffffffa07c9df8:74): readStringList: Error, timed out after 7000 ms.
>   C Reconnect mythcorecontext.cpp:1167 (CheckProtoVersion)
>     Protocol version check failure.#012#011#011#011The response to MYTH_PROTO_VERSION
>     was empty.#012#011#011#011This happens when the backend is too busy to
>     respond,#012#011#011#011or has deadlocked due to bugs or hardware failure.
>   I CoreContext mythcorecontext.cpp:375 (ConnectCommandSocket)
>     MythCoreContext: Connecting to backend server: 10.0.0.1:6543 (try 1 of 1)
>   E CoreContext mythsocket.cpp:520 (readStringList)
>     MythSocket(a0b7940:74): readStringList: Error, timed out after 7000 ms.
>   C CoreContext mythcorecontext.cpp:1167 (CheckProtoVersion)
>     Protocol version check failure.#012#011#011#011The response to MYTH_PROTO_VERSION
>     was empty.#012#011#011#011This happens when the backend is too busy to
>     respond,#012#011#011#011or has deadlocked due to bugs or hardware failure.
>   I CoreContext mythcorecontext.cpp:375 (ConnectCommandSocket)
>     MythCoreContext: Connecting to backend server: 10.0.0.1:6543 (try 1 of 1)
>   I CoreContext mythcorecontext.cpp:1191 (CheckProtoVersion) Using protocol version 75
>   I ImageLoad mythcorecontext.cpp:1191 (CheckProtoVersion) Using protocol version 75
>
>   i don't think the backend is too busy. it's not recording anything and it's only
>   using 0.7% of the cpu.
>

You have host name problems.  They may be "real" (if you changed the 
host name of the system) or "configuration" (if you didn't change the 
host name of the system, you have broken config.xml file(s) causing 
problems).

Mike