[mythtv-users] Network Control Socket
R. G. Newbury
newbury at mandamus.org
Mon Mar 19 18:22:41 UTC 2012
On 03/18/2012 04:21 PM, Raymond Wagner wrote:
> 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.
This is the .25 beta from March 5th: 18:10 running on a very recent bare
metal install of Fedora 16 (very bare: brand new SSD for the OS)
mythbackend.service script from rpmfusion, but myth compiled by me
Exact same setup here at work: NO frontend running.
AS ROOT.
[root at tor1 temp]# systemctl status mythbackend.service
mythbackend.service - MythTV backend service from RPMFusion
Loaded: loaded (/lib/systemd/system/mythbackend.service; enabled)
Active: active (running) since Tue, 13 Mar 2012 13:41:19
-0400; 6 days ago
Process: 26209 ExecStart=/usr/local/bin/mythbackend --daemon
--syslog local7 --pidfile /run/mythtv/backend.pid (code=exited,
status=0/SUCCESS)
Main PID: 26210 (mythbackend)
CGroup: name=systemd:/system/mythbackend.service
└ 26210 /usr/local/bin/mythbackend --daemon --syslog
local7 --pidfile /run/mythtv/backend.p...
[root at tor1 temp]# netstat -lnpv | grep 6546
netstat: no support for `AF INET (sctp)' on this system.
netstat: no support for `AF IPX' on this system.
netstat: no support for `AF AX25' on this system.
netstat: no support for `AF X25' on this system.
netstat: no support for `AF NETROM' on this system.
[root at tor1 temp]# nc 192.168.1.99 6546
^C
nc never returns and I have to kill it.
Something wrong in .25?? (I know, highly unlikely as that code has not
been touched recently.)
Now I am really stumped. No wonder I thought I was doing it wrong. *IT*
was not doing....
Geoff
More information about the mythtv-users
mailing list