[mythtv-commits] Ticket #10763: Network Control Socket fails to bind to proper interface on remote front end

[MythTV]

#10763: Network Control Socket fails to bind to proper interface on remote front
end
-------------------------------------+-------------------------------------
 Reporter:  Gern Blanston            |           Type:  Bug Report -
  <mythtv@…>                         |  General
   Status:  new                      |       Priority:  minor
Milestone:  unknown                  |      Component:  MythTV - General
  Version:  0.25-fixes               |       Severity:  medium
 Keywords:  frontend, network        |  Ticket locked:  0
  control socket, serverpool         |
-------------------------------------+-------------------------------------
 I hate to re-report an issue with a locked ticket (#10671) but I am
 experiencing the same problem and it feels a lot like a bug.  See that bug
 for the background on the issue.

 This is on a remote frontend.

 I can confirm that I have "LocalHostName" set in mysql.txt and the
 frontend network control port is not binding to that IP address.  It only
 binds to localhost.

 In serverpool.cpp, it appears that the code tries to add "BackendServerIP"
 (which won't work on a remote frontend) and does not reference
 "LocalHostName" from mysql.txt (as far as I can tell).

 The chunk of code in serverpool.cpp which would step through all available
 interfaces is NOT executed because of this test:
 {{{
 config_v4.isNull() && (ip.protocol() == QAbstractSocket::IPv4Protocol))
 }}}
 At this point, config_v4 is not null -- it contains the IP address
 specified by BackendServerIP -- so the following code that would step
 through each interface does not get executed.

 Here's a snip from the frontend log:
 {{{
 2012-05-14 11:34:47.898702 C  ServerPool: Host is configured to listen on
 192.168.10.131, but address is not used on any local network interfaces.
 2012-05-14 11:34:47.911098 I  Listening on TCP 127.0.0.1:6547
 2012-05-14 11:34:47.911472 I  Listening on TCP [::1]:6547
 2012-05-14 11:34:59.132162 I  Listening on TCP 127.0.0.1:6546
 2012-05-14 11:34:59.132380 I  Listening on TCP [::1]:6546
 }}}

 In the past, I -think- that it was important to set "LocalHostName" in
 mysql.txt so that configuration items would be stored correctly for a
 remote frontend.... if that's no longer the case, let us know :)

 My install of mythtv is from the 0.25-286 rpms from atrpms

 Thank you all very much for all the hard work on MythTV!

 mythbackend --version
 {{{
 Please attach all output as a file in bug reports.
 MythTV Version : v0.25
 MythTV Branch :
 Network Protocol : 72
 Library API : 0.25.20120408-1
 QT Version : 4.8.1
 Options compiled in:
  linux release use_hidesyms using_alsa using_jack using_oss using_pulse
 using_pulseoutput using_backend using_bindings_perl using_bindings_python
 using_bindings_php using_crystalhd using_dvb using_firewire using_frontend
 using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv
 using_joystick_menu using_libcrypto using_libdns_sd using_libfftw3
 using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit
 using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv
 using_bindings_perl using_bindings_python using_bindings_php
 using_mythtranscode using_opengl using_vaapi using_vdpau
 using_ffmpeg_threads using_live using_mheg using_libass using_libxml2
 }}}

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