[mythtv-commits] Ticket #10633: Network Control socket fails to listen on second address

[MythTV]

#10633: Network Control socket fails to listen on second address
-------------------------------------+--------------------------------
 Reporter:  Paul Saunders <darac@…>  |          Owner:  pbennett
     Type:  Bug Report - General     |         Status:  infoneeded_new
 Priority:  minor                    |      Milestone:  0.27.7
Component:  MythTV - General         |        Version:  0.25
 Severity:  medium                   |     Resolution:
 Keywords:                           |  Ticket locked:  0
-------------------------------------+--------------------------------

Comment (by cas@…):

 yep, it was already set to that.

 Here's the log extract from when it died.  I've also included the version
 & build info lines.

 {{{
 2017-08-03 02:27:15.440228 C [27769/27769] thread_unknown
 mythcommandlineparser.cpp:2619 (ConfigureLogging) - mythbackend version:
 fixes/29 [v29.0-b4e4ddcf97] www.mythtv.org
 2017-08-03 02:27:15.440289 C [27769/27769] thread_unknown
 mythcommandlineparser.cpp:2621 (ConfigureLogging) - Qt version: compile:
 5.7.1, runtime: 5.7.1
 2017-08-03 02:27:15.440295 N [27769/27769] thread_unknown
 mythcommandlineparser.cpp:2623 (ConfigureLogging) - Enabled verbose msgs:
 none system general
 ...
 2017-08-03 02:27:15.990051 I [27769/27769] CoreContext
 mythsystemunix.cpp:948 (Fork) - Managed child (PID: 27777) has started! *
 command=ping -t 1 -c 1  proxy.mydomain  >/dev/null 2>&1, timeout=0
 2017-08-03 02:27:15.990200 I [27769/27774] SystemSignalManager
 mythsystemunix.cpp:509 (run) - Starting process signal handler
 2017-08-03 02:27:15.990262 I [27769/27773] SystemManager
 mythsystemunix.cpp:276 (run) - Starting process manager
 2017-08-03 02:27:15.990323 I [27769/27775] SystemIOHandlerR
 mythsystemunix.cpp:92 (run) - Starting IO manager (read)
 2017-08-03 02:27:15.990347 I [27769/27776] SystemIOHandlerW
 mythsystemunix.cpp:92 (run) - Starting IO manager (write)
 2017-08-03 02:27:16.010485 I [27769/27773] SystemManager
 mythsystemunix.cpp:354 (run) - Managed child (PID: 27777) has exited!
 command=ping -t 1 -c 1  proxy.mydomain  >/dev/null 2>&1, status=0,
 result=0
 2017-08-03 02:27:16.047744 I [27769/27769] CoreContext
 schemawizard.cpp:120 (Compare) - Current MythTV Schema Version
 (DBSchemaVer): 1348
 ...

 2017-08-03 02:27:20.857412 I [27769/27769] CoreContext housekeeper.cpp:706
 (Start) - Starting HouseKeeper.
 2017-08-03 02:27:20.873567 I [27769/27769] CoreContext serverpool.cpp:422
 (listen) - Listening on TCP 0.0.0.0:6544
 2017-08-03 02:27:20.874681 I [27769/27769] CoreContext serverpool.cpp:422
 (listen) - Listening on TCP [::]:6544
 2017-08-03 02:27:20.874735 I [27769/27769] CoreContext serverpool.cpp:422
 (listen) - Listening on TCP 0.0.0.0:6554
 2017-08-03 02:27:20.874779 I [27769/27769] CoreContext serverpool.cpp:422
 (listen) - Listening on TCP [::]:6554
 2017-08-03 02:27:20.874858 E [27769/27769] CoreContext serverpool.cpp:437
 (listen) - Failed listening on TCP 0.0.0.0:6549 - Error 10: Operation on
 socket is not supported
 2017-08-03 02:27:20.874878 I [27769/27769] CoreContext serverpool.cpp:454
 (listen) - No IPv4 support on this system. Disabling MythTV IPv4.
 2017-08-03 02:27:20.874915 E [27769/27769] CoreContext serverpool.cpp:437
 (listen) - Failed listening on TCP [::]:6549 - Error 10: Operation on
 socket is not supported
 2017-08-03 02:27:20.874928 I [27769/27769] CoreContext serverpool.cpp:463
 (listen) - No IPv6 support on this system. Disabling MythTV IPv6.
 2017-08-03 02:27:20.874942 E [27769/27769] CoreContext mediaserver.cpp:111
 (Init) - MediaServer: WebSocketServer Create Error
 2017-08-03 02:27:20.889206 I [27769/27769] CoreContext
 main_helpers.cpp:687 (run_backend) - Main::Registering HttpStatus
 Extension
 2017-08-03 02:27:20.890239 C [27769/27769] CoreContext
 main_helpers.cpp:700 (run_backend) - Backend exiting, MainServer
 initialization error.
 2017-08-03 02:27:23.856569 I [27769/27769] CoreContext
 bonjourregister.cpp:28 (~BonjourRegister) - Bonjour: De-registering
 service '' on ''
 }}}

 What's really weird is that it doesn't try to use the proxy to listen on
 6544 or 6554, it only does that for port 6549.


 After I `unset http_proxy`, it works.  Doesn't try to ping my squid proxy
 server, either.

 It makes sense for myth to use a proxy if/when it ever needs to fetch data
 from the net.  or to pass the http_proxy env var to any external
 scripts/programs it might call to do that.  but not when listening on a
 socket.

--
Ticket URL: <https://code.mythtv.org/trac/ticket/10633#comment:27>
MythTV <http://www.mythtv.org>
MythTV Media Center