[mythtv-users] Network Control Socket

Raymond Wagner raymond at wagnerrp.com
Mon Mar 19 19:14:30 UTC 2012


On 3/19/2012 14:40, R. G. Newbury wrote:
> On 03/18/2012 04:21 PM, Raymond Wagner wrote:
>
>> The only thing I can think is that either the control socket itself has
>> stalled somehow, or perhaps you have an older zombified instance of the
>> frontend listening on it instead.  Check your frontend logs.  They
>> should register the initialization of that mechanism.  On 0.25, you
>> should see something like...
>>
>> 2012-03-10 01:15:06.794107 I [15388/15388] CoreContext
>> serverpool.cpp:292 (listen) - Listening on TCP 127.0.0.1:6546
>> 2012-03-10 01:15:06.794190 I [15388/15388] CoreContext
>> serverpool.cpp:292 (listen) - Listening on TCP 10.254.2.32:6546
>> 2012-03-10 01:15:06.794293 I [15388/15388] CoreContext
>> serverpool.cpp:292 (listen) - Listening on TCP [0:0:0:0:0:0:0:1]:6546
>>
>> I don't know off hand what you would be looking for in 0.24, but '6546'
>> would be a good thing to grep for.
>
> 2012-03-19 14:26:56.808072 I  Listening on TCP 127.0.0.1:6547
> 2012-03-19 14:26:56.808168 I  Listening on TCP 192.168.1.99:6547
> 2012-03-19 14:26:56.810910 I  Listening on TCP [::1]:6547

This is the frontend web server turning on.  It is enabled by default, 
and uses port 6547 by default.  It can be used to send assorted commands 
and queries through the Services API, and can be used as a 
connectionless HTTP alternative to the control socket.

> 2012-03-19 14:26:58.526496 I  Binding to UDP 127.0.0.1:6948
> 2012-03-19 14:26:58.526553 I  Binding to UDP 192.168.1.99:6948
> 2012-03-19 14:26:58.529235 I  Binding to UDP [::1]:6948
> 2012-03-19 14:26:58.529311 I  Binding to UDP 192.168.1.255:6948

This is MythMessage turning on.  It is enabled by default, and uses port 
6548 by default.  It listens for properly formatted UDP packets sent 
over the network, and displays them as a popup, replacing the old 
MythNotify.  See... http://www.mythtv.org/wiki/MythMessage

> mysql>  select value,data from settings  where data like "%654%";
> +--------------------+------+
> | value              | data |
> +--------------------+------+
> | NetworkControlPort | 6546 |
> +--------------------+------+
> 4 rows in set (0.00 sec)

The network control socket uses port 6546 by default, so having that set 
really doesn't change anything.  However, it is disabled by default, and 
enabled using the 'NetworkControlEnabled' option found in the frontend 
configuration.

> I note that the config.log does NOT report the php bindings status which
> configure reported as 'yes'.

The PHP bindings are always enabled unless you intentionally specify 
otherwise.  While there the PHP bindings do have a few dependencies, 
there are currently none checked for by configure, and the bindings are 
installed to MythTV's share path, usually /usr/local/share/bindings/php/.



More information about the mythtv-users mailing list