[mythtv-users] 29 upgrade issue?

[Stephen Worthington]

On Thu, 17 May 2018 18:09:43 +0200, you wrote:

>On 17-05-18 17:54, Stephen Worthington wrote:
>>> Yes. Who needs IPv6 when stuff works with ipv4?
>> 
>> IPv6 support is there for when IPv4 stops working, which it will
>> eventually.  
>
>Private addressing has no need top stop working.
>Ipv6 has weird design and no need for at home.

I am not sure why you would say "no need for at home" - if I should
want to connect to one of the very few IPv6 only sites out there, I
would need IPv6 on my home network.

>> In the mean time, it just works better than IPv4 is most
>> ways.  
>
>Hahah. You did not experience dual stack internet yet, I assume.
>Did you see the troubles that dhclient in Fedora had to go through in
>how man years to be working OK?
>With how many workarounds?

No, I have not been following any of that.  But dhclient seems to work
fine now.  I have had IPv4/IPv6 dual stack on my network for a long
time now, but I have been using Ubuntu and Debian.  Apart from the MTU
problem going through a PPPoE connection, I have not had any IPv6
related problems.

>> Including in real life connections across the Internet, where
>> speed is usually a bit faster due to the ease with which routers can
>> handle IPv6 packets.
>
>I did experience Vanguard 65xx routers with OSPF enabled so please do
>not mention routing speed. IpV4 speed was OK for me until today.
>I simply see an ISP that gives me a /80 in a world where tools (radvd
>etc) do not except anything else than a /64.
>Who /really/ thought about that?

The designers of IPv6 did think about that and decided that the
minimum size of address block that should ever be delegated is a /64.
If there is any idiot out there delegating smaller address blocks,
then they need to fix what they are doing to conform to normal IPv6
practice.  There is no need for smaller delegations.  The IPv6 address
space is designed to have a /64 on each subnet, and still have enough
addresses for everyone on the planet for the foreseeable future.

>In that same world now fits mythtv that *requires* instead of 'supports'
>IPv6 now, without me knowing beforehand.
>
>> If your network does not have IPv6 connections to the Internet, then
>> there is normally no reason to have IPv6 disabled anyway.  
>
>It does and we run dual stack for quite a while now. Even with a tunnel
>before that.
>But that does not imply I want to run the mythtv box with ipv6 for no
>good reason than application software that *requires* it for no good reason.
>
>
>> And even better to fix the problem and get IPv6
>> working properly.
>
>My ipv6 is working properly already, thank you.
>I do not *need* ipv6 for mythtv and do not see a need either.
>So please enlighten me.

If you have IPv6 working properly on your network, then just enable it
on the MythTV box and this problem will go away.  A simple, easy fix,
and the right thing to do.

>> See this also:
>> 
>> https://lists.gt.net/mythtv/dev/610202
>> 
>> So it looks like you can add a setting into the settings table
>> manually with SQL like this:
>> 
>> insert into settings (value, data, hostname) values('IPv6Support', 0,
>> NULL);
>
>YES! That helps with the IPv6 related things!
>But does *not* help with the 'slave backend' versus 'master' setting:

Yes, that seems to be the remaining problem, and to me it looks like a
bug in mythbackend.  If you really, really want to run with IPv6
disabled, then you probably need to clear all the IPv6 address fields
in mythtv-setup and see if that helps.  My guess would be that
mythbackend is going into slave mode because it sees one mismatched IP
address between its addresses and the master addresses in the
database.  So if you can remove the IPv6 master address from the
database, that mismatch may go away and allow it to work with the two
matching IPv4 addresses and decide it is the master backend.

>
>> And I think that those IPv6 messages are just warnings anyway and
>> mythbackend is actually working properly.  The netstat results show
>> that it is listening on the IPv4 ports.
>
>Yet not responding to connection efforts from itself due to the `slave`
>issue?
>
># cat  /var/log/mythtv/mythbackend.20180517160423.19563.log
>2018-05-17 18:04:23.120272 C [19563/19563] thread_unknown
>mythcommandlineparser.cpp:2619 (ConfigureLogging) - mythbackend version:
>master [v29.1-v29.1-19-g0849e99596] www.mythtv.org
>2018-05-17 18:04:23.120325 C [19563/19563] thread_unknown
>mythcommandlineparser.cpp:2621 (ConfigureLogging) - Qt version: compile:
>5.10.1, runtime: 5.10.1
>2018-05-17 18:04:23.120328 N [19563/19563] thread_unknown
>mythcommandlineparser.cpp:2623 (ConfigureLogging) - Enabled verbose
>msgs:  general
>2018-05-17 18:04:23.120494 N [19563/19563] thread_unknown
>logging.cpp:927 (logStart) - Setting Log Level to LOG_INFO
>2018-05-17 18:04:23.131496 I [19563/19566] Logger logging.cpp:313 (run)
>- Added logging to the console
>2018-05-17 18:04:23.134881 I [19563/19563] thread_unknown
>signalhandling.cpp:194 (SetHandlerPrivate) - Setup Interrupt handler
>2018-05-17 18:04:23.134922 I [19563/19563] thread_unknown
>signalhandling.cpp:194 (SetHandlerPrivate) - Setup Terminated handler
>2018-05-17 18:04:23.134937 I [19563/19563] thread_unknown
>signalhandling.cpp:194 (SetHandlerPrivate) - Setup Segmentation fault
>handler
>2018-05-17 18:04:23.134961 I [19563/19563] thread_unknown
>signalhandling.cpp:194 (SetHandlerPrivate) - Setup Aborted handler
>2018-05-17 18:04:23.134973 I [19563/19563] thread_unknown
>signalhandling.cpp:194 (SetHandlerPrivate) - Setup Bus error handler
>2018-05-17 18:04:23.134990 I [19563/19563] thread_unknown
>signalhandling.cpp:194 (SetHandlerPrivate) - Setup Floating point
>exception handler
>2018-05-17 18:04:23.135003 I [19563/19563] thread_unknown
>signalhandling.cpp:194 (SetHandlerPrivate) - Setup Illegal instruction
>handler
>2018-05-17 18:04:23.135042 I [19563/19563] thread_unknown
>signalhandling.cpp:194 (SetHandlerPrivate) - Setup Real-time signal 0
>handler
>2018-05-17 18:04:23.135061 I [19563/19563] thread_unknown
>signalhandling.cpp:194 (SetHandlerPrivate) - Setup Hangup handler
>2018-05-17 18:04:23.135513 N [19563/19563] thread_unknown
>mythdirs.cpp:195 (InitializeMythDirs) - Using runtime prefix = /usr
>2018-05-17 18:04:23.135521 N [19563/19563] thread_unknown
>mythdirs.cpp:197 (InitializeMythDirs) - Using configuration directory =
>/home/mythtv/.mythtv
>2018-05-17 18:04:23.135731 I [19563/19563] CoreContext
>mythcorecontext.cpp:271 (Init) - Assumed character encoding: en_US.UTF-8
>2018-05-17 18:04:23.136801 I [19563/19563] CoreContext
>mythcontext.cpp:607 (LoadDatabaseSettings) - Using localhost value of
>localhost
>2018-05-17 18:04:23.136975 I [19563/19563] CoreContext
>mythcontext.cpp:852 (TestDBconnection) - Start up testing connections.
>DB localhost, BE , attempt 0, status dbAwake
>2018-05-17 18:04:23.232913 I [19563/19565] LogForward
>loggingserver.cpp:146 (FileLogger) - Added logging to
>/var/log/mythtv/mythbackend.20180517160423.19563.log
>2018-05-17 18:04:24.163296 N [19563/19563] CoreContext
>mythcorecontext.cpp:1768 (InitLocale) - Setting QT default locale to EN_US
>2018-05-17 18:04:24.163323 I [19563/19563] CoreContext
>mythcorecontext.cpp:1801 (SaveLocaleDefaults) - Current locale EN_US
>2018-05-17 18:04:24.163405 N [19563/19563] CoreContext
>mythlocale.cpp:123 (LoadDefaultsFromXML) - Reading locale defaults from
>/usr/share/mythtv//locales/en_us.xml
>2018-05-17 18:04:24.175979 I [19563/19563] CoreContext
>mythtranslation.cpp:73 (load) - Loading en_us translation for module
>mythfrontend
>2018-05-17 18:04:24.182041 I [19563/19563] CoreContext
>schemawizard.cpp:120 (Compare) - Current MythTV Schema Version
>(DBSchemaVer): 1348
>2018-05-17 18:04:24.182593 I [19563/19563] CoreContext
>mythtranslation.cpp:73 (load) - Loading en_us translation for module
>mythfrontend
>2018-05-17 18:04:24.185305 E [19563/19568] MythSocketThread(-1)
>mythsocket.cpp:698 (ConnectToHostReal) - MythSocket(2605e00:-1): Failed
>to connect to (127.0.0.1:6543) Connection refused
>2018-05-17 18:04:24.187057 N [19563/19563] CoreContext
>main_helpers.cpp:601 (run_backend) - MythBackend: Running as a slave
>backend.
>2018-05-17 18:04:25.023960 I [19563/19563] CoreContext
>housekeeper.cpp:633 (RegisterTask) - Registering HouseKeeperTask
>'JobQueueRecover'.
>2018-05-17 18:04:25.023998 I [19563/19563] CoreContext
>housekeeper.cpp:633 (RegisterTask) - Registering HouseKeeperTask
>'HardwareProfiler'.
>2018-05-17 18:04:25.026084 I [19563/19563] CoreContext
>housekeeper.cpp:706 (Start) - Starting HouseKeeper.
>2018-05-17 18:04:25.068426 I [19563/19563] CoreContext
>serverpool.cpp:422 (listen) - Listening on TCP 0.0.0.0:6544
>2018-05-17 18:04:25.070369 I [19563/19563] CoreContext
>serverpool.cpp:422 (listen) - Listening on TCP 0.0.0.0:6554
>2018-05-17 18:04:25.070554 I [19563/19563] CoreContext
>serverpool.cpp:422 (listen) - Listening on TCP 0.0.0.0:6549
>2018-05-17 18:04:25.882368 I [19563/19563] CoreContext
>main_helpers.cpp:687 (run_backend) - Main::Registering HttpStatus Extension
>2018-05-17 18:04:25.885397 I [19563/19563] CoreContext
>serverpool.cpp:422 (listen) - Listening on TCP 0.0.0.0:6543
>2018-05-17 18:04:26.836681 N [19563/19563] CoreContext
>mainserver.cpp:7991 (reconnectTimeout) - MainServer: Connecting to
>master server: 127.0.0.1:6543
>2018-05-17 18:04:26.837346 N [19563/19563] CoreContext
>mainserver.cpp:8002 (reconnectTimeout) - MainServer: Connected successfully
>2018-05-17 18:04:56.854285 E [19563/19586] MythSocketThread(-1)
>mythsocket.cpp:827 (ReadStringListReal) - MythSocket(26f97e0:45):
>ReadStringList: Error, timed out after 30000 ms.
>2018-05-17 18:04:56.854548 W [19563/19586] MythSocketThread(-1)
>mainserver.cpp:7704 (connectionClosed) - MainServer: Unknown socket
>closing MythSocket(0x26f97e0)
>2018-05-17 18:04:56.854691 E [19563/19563] CoreContext
>mythsocket.cpp:369 (SendReceiveStringList) - MythSocket(26f97e0:-1): No
>response.
>2018-05-17 18:04:56.854711 E [19563/19563] CoreContext
>mainserver.cpp:8040 (reconnectTimeout) - MainServer: Failed to open
>master server socket, timeout
>2018-05-17 18:04:56.860376 I [19563/19563] CoreContext
>bonjourregister.cpp:118 (BonjourCallback) - Bonjour: Service
>registration complete: name 'Mythbackend on localhost' type
>'_mythbackend._tcp.' domain: 'local.'
>2018-05-17 18:04:56.862109 I [19563/19600] MythSocketThread(8)
>mainserver.cpp:7693 (connectionClosed) - Control sock(25dd3c0) disconnected
>2018-05-17 18:04:57.806921 N [19563/19563] CoreContext
>mainserver.cpp:7991 (reconnectTimeout) - MainServer: Connecting to
>master server: 127.0.0.1:6543
>2018-05-17 18:04:57.807533 N [19563/19563] CoreContext
>mainserver.cpp:8002 (reconnectTimeout) - MainServer: Connected successfully
>2018-05-17 18:05:27.824487 E [19563/19602] MythSocketThread(-1)
>mythsocket.cpp:827 (ReadStringListReal) - MythSocket(2702060:47):
>ReadStringList: Error, timed out after 30000 ms.
>2018-05-17 18:05:27.824625 W [19563/19602] MythSocketThread(-1)
>mainserver.cpp:7704 (connectionClosed) - MainServer: Unknown socket
>closing MythSocket(0x2702060)
>2018-05-17 18:05:27.824764 E [19563/19563] CoreContext
>mythsocket.cpp:369 (SendReceiveStringList) - MythSocket(2702060:-1): No
>response.
>2018-05-17 18:05:27.824785 E [19563/19563] CoreContext
>mainserver.cpp:8040 (reconnectTimeout) - MainServer: Failed to open
>master server socket, timeout
>2018-05-17 18:05:27.825813 I [19563/19603] MythSocketThread(47)
>mainserver.cpp:7693 (connectionClosed) - Control sock(26fdc50) disconnected
>2018-05-17 18:05:28.776647 N [19563/19563] CoreContext
>mainserver.cpp:7991 (reconnectTimeout) - MainServer: Connecting to
>master server: 127.0.0.1:6543
>2018-05-17 18:05:28.777251 N [19563/19563] CoreContext
>mainserver.cpp:8002 (reconnectTimeout) - MainServer: Connected successfully
>2018-05-17 18:05:58.796278 E [19563/19604] MythSocketThread(-1)
>mythsocket.cpp:827 (ReadStringListReal) - MythSocket(26fb6a0:49):
>ReadStringList: Error, timed out after 30000 ms.
>2018-05-17 18:05:58.796419 W [19563/19604] MythSocketThread(-1)
>mainserver.cpp:7704 (connectionClosed) - MainServer: Unknown socket
>closing MythSocket(0x26fb6a0)
>2018-05-17 18:05:58.796561 E [19563/19563] CoreContext
>mythsocket.cpp:369 (SendReceiveStringList) - MythSocket(26fb6a0:-1): No
>response.
>2018-05-17 18:05:58.796581 E [19563/19563] CoreContext
>mainserver.cpp:8040 (reconnectTimeout) - MainServer: Failed to open
>master server socket, timeout
>2018-05-17 18:05:58.796748 C [19563/19563] CoreContext
>signalhandling.cpp:305 (handleSignal) - Received Terminated: Code 0, PID
>1, UID 0, Value 0x00000000
>2018-05-17 18:05:58.797136 N [19563/19563] CoreContext
>main_helpers.cpp:730 (run_backend) - MythBackend exiting
>2018-05-17 18:05:58.800300 I [19563/19563] CoreContext
>bonjourregister.cpp:28 (~BonjourRegister) - Bonjour: De-registering
>service '_mythbackend._tcp.' on 'Mythbackend on localhost'