[mythtv-users] Network Control Socket

Raymond Wagner raymond at wagnerrp.com
Sun Mar 18 20:21:40 UTC 2012


On 3/18/2012 15:54, R. G. Newbury wrote:
> Using fedora ( so it's nc not netcat) I enter:
>
> nc 192.168.1.96 6546  on my laptop, to try to contact the myth box.
>
> Nothing.
> If I ssh into the mythbox and try 'nc -l 6546' on that end, it says 'nc:
> Address already in use'. So myth is doing its bit.

That _should_ work just fine.  You've got a couple different routes you 
can go with it.

raymond at fserve:~
 >nc myth2 6546
MythFrontend Network Control
Type 'help' for usage information
---------------------------------
# query location
playbackbox


raymond at fserve:~
 >echo "query uptime" | nc myth2 6546
MythFrontend Network Control
Type 'help' for usage information
---------------------------------
# 1108520
#


raymond at fserve:~
 >nc myth2 6546 << EOF
? query location
? query uptime
? query memstats
? EOF
MythFrontend Network Control
Type 'help' for usage information
---------------------------------
# playbackbox
# 1108568
# 3012 2074 1032 1032
#


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.


More information about the mythtv-users mailing list