[mythtv-users] Updated to 0.29 now can't connect to backend

[Mark Perkins]

On 20 January 2018 11:36:02 am Damian <myth at surr.co.uk> wrote:

> Hi All,
>
> Ah, the joys of updating!
>
> I had to update one of my frontends, and realised that it had installed
> Mythtv v0.29 (via mythbubtu).
>
> It couldn't connect to the backend, so I assumed it was because the
> backend was v0.28.
>
> So, I've just changed that mythbuntu repositories and updated the
> backend to v0.29.
>
> Now the backend can't even connect to itself! :-)
>
> If I run the frontend (on the backend system), it just keeps searching
> for the backend and saying that it can't find it.
>
> Now I'm stuck in an endless loop of closing the frontend and it auto
> restarting.
>
> If I run  "sudo service mythtv-backend status", I get ...
>
>
> mythtv-backend.service - MythTV Backend
>     Loaded: loaded (/lib/systemd/system/mythtv-backend.service; enabled;
> vendor preset: enabled)
>     Active: active (running) since Sat 2018-01-20 00:25:40 GMT; 27min ago
>       Docs: https://www.mythtv.org/wiki/Mythbackend
>   Main PID: 1387 (mythbackend)
>     CGroup: /system.slice/mythtv-backend.service
>             └─1387 /usr/bin/mythbackend --quiet --syslog local7
>
> Jan 20 00:52:14 xyzserver mythbackend[1387]: mythbackend[1387]: I
> ProcessRequest mainserver.cpp:1743 (HandleAnnounce) MainServer: adding:
> xyzserver(1077ee0) as a client (events: 1)
> Jan 20 00:52:15 xyzserver mythbackend[1387]: mythbackend[1387]: N
> CoreContext mainserver.cpp:7991 (reconnectTimeout) MainServer:
> Connecting to master server: 192.168.0.2:6543
> Jan 20 00:52:15 xyzserver mythbackend[1387]: mythbackend[1387]: N
> CoreContext mainserver.cpp:8002 (reconnectTimeout) MainServer: Connected
> successfully
> Jan 20 00:52:45 xyzserver mythbackend[1387]: mythbackend[1387]: E
> MythSocketThread(-1) mythsocket.cpp:827 (ReadStringListReal)
> MythSocket(107e4f0:88): ReadStringList: Error, timed out a
> Jan 20 00:52:45 xyzserver mythbackend[1387]: mythbackend[1387]: W
> MythSocketThread(-1) mainserver.cpp:7704 (connectionClosed) MainServer:
> Unknown socket closing MythSocket(0x107e4f0)
> Jan 20 00:52:45 xyzserver mythbackend[1387]: mythbackend[1387]: E
> CoreContext mythsocket.cpp:369 (SendReceiveStringList)
> MythSocket(107e4f0:-1): No response.
> Jan 20 00:52:45 xyzserver mythbackend[1387]: mythbackend[1387]: E
> CoreContext mainserver.cpp:8040 (reconnectTimeout) MainServer: Failed to
> open master server socket, timeout
> Jan 20 00:52:45 xyzserver mythbackend[1387]: mythbackend[1387]: I
> MythSocketThread(88) mainserver.cpp:7693 (connectionClosed) Control
> sock(1067cc0) disconnected
> Jan 20 00:52:46 xyzserver mythbackend[1387]: mythbackend[1387]: N
> CoreContext mainserver.cpp:7991 (reconnectTimeout) MainServer:
> Connecting to master server: 192.168.0.2:6543
> Jan 20 00:52:46 xyzserver mythbackend[1387]: mythbackend[1387]: N
> CoreContext mainserver.cpp:8002 (reconnectTimeout) MainServer: Connected
> successfully
>
>
> Any idea what's going on?
>
> Thanks,
> Damian
>
>
>
Has mysql (most likely given mythbuntu otherwise maybe mariadb) started? Is 
it listening?

What does
netstat -peanut | grep 3306
Return?

What does backend log report?