noreply at mythtv
Apr 20, 2012, 7:05 AM
Views: 628
Permalink
|
|
Ticket #10633: Network Control socket fails to listen on second address
|
|
#10633: Network Control socket fails to listen on second address
------------------------------------+--------------------------------------
Reporter: Paul Saunders | Type: Bug Report - General
<darac@…> | Priority: minor
Status: new | Component: MythTV - General
Milestone: unknown | Severity: medium
Version: 0.25 | Ticket locked: 0
Keywords: |
------------------------------------+--------------------------------------
As of 0.25, the Network Control socket (port 6456) doesn't work. At least,
this is the immediately obvious problem. Looking at the logs, I can see
that it successfully listens on 127.0.0.1, but then fails listening to the
next address in the list (for the attached log, that is 192.168.123.1, but
the same occurs on another machine where the second, failing address is
public).
With the frontend still running, I can see that:
a. there is nothing already listening on that port (`sudo netstat -nlp |
grep 6456` returns nothing) and
b. I can listen on that port (`nc -l -p 6456` and even 'nc -l -s
192.168.123.1 -p 6456` start up and print commands from my remote
control).
I'm not quite sure how to proceed, though. I can see there is a problem
here, but without knowing ''why'' MythFrontend is not listening, it's a
bit difficult to find the root cause.
--
Ticket URL: <http://code.mythtv.org/trac/ticket/10633>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center
_______________________________________________
mythtv-commits mailing list
mythtv-commits [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-commits
|
Ticket #10633: Network Control socket fails to listen on second address
