[mythtv-commits] Ticket #13552: Backend now fails to start as master with a new database

[MythTV]

#13552: Backend now fails to start as master with a new database
--------------------------------------+--------------------------
     Reporter:  bib1963               |      Owner:  (none)
         Type:  Bug Report - General  |     Status:  new
     Priority:  minor                 |  Milestone:  needs_triage
    Component:  MythTV - General      |    Version:  Unspecified
     Severity:  medium                |   Keywords:
Ticket locked:  0                     |
--------------------------------------+--------------------------
 Git updated to today, 20200111.

 New database created.

 Set up with a single card, all settings at default.

 Starting the backend brings up a line with:
 2020-01-11 19:52:48.977164 N  MythBackend: Running as a slave backend.

 Backend runs, however the frontend never connects.

 I can see the DB traffic over lo for the FE.

 When the BE starts, and doing a netstat, I see:
 root at eth7 ~# netstat -anp | grep 6543

 tcp        0      0 0.0.0.0:6543            0.0.0.0:*               LISTEN
 17905/mythbackend

 tcp6       1      0 :::6543                 :::*                    LISTEN
 17905/mythbackend

 tcp6       0      0 ::1:45440               ::1:6543
 TIME_WAIT   -

 tcp6       0      0 ::1:45444               ::1:6543
 ESTABLISHED 17905/mythbackend

 tcp6       0      0 ::1:45442               ::1:6543
 TIME_WAIT   -

 tcp6    3738      0 ::1:6543                ::1:45444
 ESTABLISHED -


 Notice the RX queue always has data in it and is never read.

 This connection gets cleared down every 30 seconds with the backend giving
 out:

 2020-01-11 19:58:36.249789 E  MythSocket(17cc960:92): ReadStringList:
 Error, timed out after 30000 ms.

 2020-01-11 19:58:36.249831 W  MainServer: Unknown socket closing
 MythSocket(0x17cc960)

 2020-01-11 19:58:36.249861 E  MythSocket(17cc960:-1): No response.

 2020-01-11 19:58:36.249866 E  MainServer: Failed to open master server
 socket, timeout

 2020-01-11 19:58:36.250149 I  Control sock(180d130) disconnected

 2020-01-11 19:58:37.245682 N  MainServer: Connecting to master server:
 2001:8b0:ca:2::fd:6543

 2020-01-11 19:58:37.245817 N  MainServer: Connected successfully

 It's always the same response.


 The Setup, does show the running system is supposed to be the master.

 If I toggle the master/slave tick box, and going back in nothing changes,
 except that the tickbox is set to show the BE being the master.

 No amount of changes to the General->Host Address Backend Setup makes any
 difference, Including listening on IPv4/IPv6/local/network interfaces, or
 changing it to a host name.

 This was working, before I wiped the database, so I assume something
 changed a while ago and reference a database entry which was still
 existing, but is no longer inserted with a new setup.

-- 
Ticket URL: <https://code.mythtv.org/trac/ticket/13552>
MythTV <http://www.mythtv.org>
MythTV Media Center