Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Commits

Ticket #10633: Network Control socket fails to listen on second address

  

 
MythTV commits RSS feed   Index | Next | Previous | View Threaded


noreply at mythtv

Apr 20, 2012, 7:05 AM

Post #1 of 16 (597 views)
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


noreply at mythtv

Apr 20, 2012, 7:15 AM

Post #2 of 16 (588 views)
Permalink
Re: Ticket #10633: Network Control socket fails to listen on second address [In reply to]
#10633: Network Control socket fails to listen on second address
-------------------------------------+--------------------------
Reporter: Paul Saunders <darac@…> | Owner: wagnerrp
Type: Bug Report - General | Status: accepted
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------+--------------------------
Changes (by wagnerrp):

* owner: => wagnerrp
* status: new => accepted


--
Ticket URL: <http://code.mythtv.org/trac/ticket/10633#comment:1>
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


noreply at mythtv

Apr 20, 2012, 7:18 AM

Post #3 of 16 (588 views)
Permalink
Re: Ticket #10633: Network Control socket fails to listen on second address [In reply to]
#10633: Network Control socket fails to listen on second address
-------------------------------------+----------------------------
Reporter: Paul Saunders <darac@…> | Owner: wagnerrp
Type: Bug Report - General | Status: infoneeded
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------+----------------------------
Changes (by wagnerrp):

* status: accepted => infoneeded


Comment:

Waiting on logs presumed to be forthcoming. Also, the default port is
6546, not 6456. You were likely checking netstat for the wrong port. Is
there anything already listening on that?

--
Ticket URL: <http://code.mythtv.org/trac/ticket/10633#comment:2>
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


noreply at mythtv

Apr 20, 2012, 7:22 AM

Post #4 of 16 (588 views)
Permalink
Re: Ticket #10633: Network Control socket fails to listen on second address [In reply to]
#10633: Network Control socket fails to listen on second address
-------------------------------------+----------------------------
Reporter: Paul Saunders <darac@…> | Owner: wagnerrp
Type: Bug Report - General | Status: infoneeded
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------+----------------------------

Comment (by Paul Saunders <darac@…>):

Sorry. My laptop crashed between creating the ticket and attaching the
logs.

6456 was a typo here in the ticket. I have actually checked port 6546.

--
Ticket URL: <http://code.mythtv.org/trac/ticket/10633#comment:3>
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


noreply at mythtv

Apr 20, 2012, 8:05 AM

Post #5 of 16 (591 views)
Permalink
Re: Ticket #10633: Network Control socket fails to listen on second address [In reply to]
#10633: Network Control socket fails to listen on second address
-------------------------------------+----------------------------
Reporter: Paul Saunders <darac@…> | Owner: wagnerrp
Type: Bug Report - General | Status: infoneeded
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------+----------------------------

Comment (by wagnerrp):

Just a few side comments first. The logs report version "v0.25pre".
You're running a pre-release and should upgrade, but there haven't been
any changes to the listen servers in several weeks, and that's not likely
to cause your problems. More importantly, that's not a version string
MythTV would generate itself. MythTV would have included a specific
commit hash, as well as a counter of commits since that tag, likely in the
4000+ range. If you are getting MythTV from a third party packager, it
would be beneficial to know who, so we could contact them and get a more
descriptive string put in there.

Line 96 indicates you're running your backend against an internet facing
IP address. Generally this is advised against for security reasons, and
just simple lack of bandwidth needed to make such configuration
worthwhile. Since you don't have an IP forced for that host, MythTV scans
your available addresses, and automatically selects where to listen.
You'll note on line 34 that it refused to listen on the non-RFC1918
address. On the other hand, considering you have multiple internet facing
addresses, as well as multiple internal subnets, you presumably know what
you're doing in that regard.

--
Ticket URL: <http://code.mythtv.org/trac/ticket/10633#comment:4>
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


noreply at mythtv

Apr 20, 2012, 9:12 AM

Post #6 of 16 (581 views)
Permalink
Re: Ticket #10633: Network Control socket fails to listen on second address [In reply to]
#10633: Network Control socket fails to listen on second address
-------------------------------------+----------------------------
Reporter: Paul Saunders <darac@…> | Owner: wagnerrp
Type: Bug Report - General | Status: infoneeded
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------+----------------------------

Comment (by wagnerrp):

Replying to [comment:4 wagnerrp]:
> The logs report version "v0.25pre". That's not a version string MythTV
would generate itself.

Scratch that, it appears that IS the string the build scripts produce
now...

--
Ticket URL: <http://code.mythtv.org/trac/ticket/10633#comment:5>
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


noreply at mythtv

Apr 20, 2012, 9:18 AM

Post #7 of 16 (581 views)
Permalink
Re: Ticket #10633: Network Control socket fails to listen on second address [In reply to]
#10633: Network Control socket fails to listen on second address
-------------------------------------+----------------------------
Reporter: Paul Saunders <darac@…> | Owner: wagnerrp
Type: Bug Report - General | Status: infoneeded
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------+----------------------------

Comment (by wagnerrp):

In [changeset:f4d7bffcc71904d84b06046213ba453fa2aa2865/mythtv]:
{{{
Add logging information as to why MythTV would fail to listen on a port.

Refs #10633
}}}

--
Ticket URL: <http://code.mythtv.org/trac/ticket/10633#comment:6>
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


noreply at mythtv

Apr 20, 2012, 9:18 AM

Post #8 of 16 (580 views)
Permalink
Re: Ticket #10633: Network Control socket fails to listen on second address [In reply to]
#10633: Network Control socket fails to listen on second address
-------------------------------------+----------------------------
Reporter: Paul Saunders <darac@…> | Owner: wagnerrp
Type: Bug Report - General | Status: infoneeded
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------+----------------------------

Comment (by wagnerrp):

In [changeset:1a671d0b252d2b33bd1e96258e65a15d52a5fc7d/mythtv]:
{{{
Add logging information as to why MythTV would fail to listen on a port.

Refs #10633
(cherry picked from commit f4d7bffcc71904d84b06046213ba453fa2aa2865)
}}}

--
Ticket URL: <http://code.mythtv.org/trac/ticket/10633#comment:7>
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


noreply at mythtv

Apr 20, 2012, 9:46 AM

Post #9 of 16 (582 views)
Permalink
Re: Ticket #10633: Network Control socket fails to listen on second address [In reply to]
#10633: Network Control socket fails to listen on second address
-------------------------------------+----------------------------
Reporter: Paul Saunders <darac@…> | Owner: wagnerrp
Type: Bug Report - General | Status: infoneeded
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------+----------------------------

Comment (by beirdo):

Replying to [comment:5 wagnerrp]:
> Replying to [comment:4 wagnerrp]:
> > The logs report version "v0.25pre". That's not a version string
MythTV would generate itself.
>
> Scratch that, it appears that IS the string the build scripts produce
now...

That means that his build was made from the tarball. I have reuploaded
the tarball since with the proper value set in VERSION, and fixed the
release script so it doesn't happen again. If it's a git build, then the
only time you see the tag as the version is when you are right on that
tag, but then the branch would also be filled out.

It might be a good idea to redownload the tarball to remove confusion
later. If this was packaged by someone, please let us know which package
so we can let them know as well.

--
Ticket URL: <http://code.mythtv.org/trac/ticket/10633#comment:8>
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


noreply at mythtv

Apr 20, 2012, 10:14 AM

Post #10 of 16 (579 views)
Permalink
Re: Ticket #10633: Network Control socket fails to listen on second address [In reply to]
#10633: Network Control socket fails to listen on second address
-------------------------------------+----------------------------
Reporter: Paul Saunders <darac@…> | Owner: wagnerrp
Type: Bug Report - General | Status: infoneeded
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------+----------------------------

Comment (by wagnerrp):

Paul Saunders:

Could you test again with the above changes to get an explanation of the
error? My only guess is you've got something else already listening on
those ports.

--
Ticket URL: <http://code.mythtv.org/trac/ticket/10633#comment:9>
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


noreply at mythtv

Apr 20, 2012, 1:31 PM

Post #11 of 16 (571 views)
Permalink
Re: Ticket #10633: Network Control socket fails to listen on second address [In reply to]
#10633: Network Control socket fails to listen on second address
-------------------------------------+----------------------------
Reporter: Paul Saunders <darac@…> | Owner: wagnerrp
Type: Bug Report - General | Status: infoneeded
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------+----------------------------

Comment (by Paul Saunders <darac@…>):

OK. For the record, the build I initially reported the bug against was the
Debian-Multimedia package, version 0.25-0.3.

I've now re-built from git commit 1a671d0 and re-run mythfrontend again.
Perhaps a little surprisingly, the error now is:

{{{
Failed listening on TCP 192.168.123.1:6546 - Error 10: Operation on socket
is not supported
}}}

I can attach the full log if you like, but I suspect that's the bit you're
interested in.

--
Ticket URL: <http://code.mythtv.org/trac/ticket/10633#comment:10>
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


noreply at mythtv

May 6, 2012, 4:54 AM

Post #12 of 16 (503 views)
Permalink
Re: Ticket #10633: Network Control socket fails to listen on second address [In reply to]
#10633: Network Control socket fails to listen on second address
-------------------------------------+----------------------------
Reporter: Paul Saunders <darac@…> | Owner: wagnerrp
Type: Bug Report - General | Status: infoneeded
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------+----------------------------

Comment (by martin_ginkel@…):

I have exactly the same problem on mythbuntu with official debs,
2:0.25.0+fixes.20120506.1c4066e.
The problem does not exist on opensuse (my other frontend) on a 2.6.39
kernel.
Maybe this is related to newer kernels and different socket handling.
I have not seen anything special in strace.

--
Ticket URL: <http://code.mythtv.org/trac/ticket/10633#comment:11>
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


noreply at mythtv

May 10, 2012, 1:48 PM

Post #13 of 16 (499 views)
Permalink
Re: Ticket #10633: Network Control socket fails to listen on second address [In reply to]
#10633: Network Control socket fails to listen on second address
-------------------------------------+----------------------------
Reporter: Paul Saunders <darac@…> | Owner: wagnerrp
Type: Bug Report - General | Status: infoneeded
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------+----------------------------

Comment (by martin_ginkel@…):

OK after some debugging I found a strange but simple solution:

On my myth box I have the environment variables
http_proxy=http://my.squid.box:3128 enabled.
The Squid is working, but apparently QT uses these always for all tcp
sockets.
After unsetting the variables, mythfrontend listens as expected.

The code for this is somewhere deep in QTcpServer::listen(), I have no
Idea why this
only fails for the network control port. But on my laptop it always
worked, until I set
the same environment variables, then the network control socket failed as
well.

'''Solution:'''

'''export http_proxy='''

--
Ticket URL: <http://code.mythtv.org/trac/ticket/10633#comment:12>
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


noreply at mythtv

May 11, 2012, 4:47 AM

Post #14 of 16 (492 views)
Permalink
Re: Ticket #10633: Network Control socket fails to listen on second address [In reply to]
#10633: Network Control socket fails to listen on second address
-------------------------------------+----------------------------
Reporter: Paul Saunders <darac@…> | Owner: wagnerrp
Type: Bug Report - General | Status: infoneeded
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------+----------------------------

Comment (by martin_ginkel@…):

Did ab bit of research about proxy network operation in QT.
Apparently they introduced the QNetworkProxy in 4.1 and allowed to set
an application-global proxying of all network connections.

http://doc.qt.nokia.com/4.7-snapshot/qnetworkproxy.html#setApplicationProxy

I still don't see, how this is directly related to listening servers but
apparently the QTcpServer works with the DefaultProxy proxy type by
default.
This means it respects the global application setting.

If the application setting is set to global QNetworkProxy::HttpProxy then
all connections (not only HTTP-outgoing) are supposed to tunnel through
a transparent HTTP proxy.

Eventually one could set the Proxy mode of the PrivTcpServer in ServerPool
to
use the NoProxy mode. For the special network non-HTTP ports it does not
make any
sense to use Proxies automatically.

--
Ticket URL: <http://code.mythtv.org/trac/ticket/10633#comment:13>
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


noreply at mythtv

Sep 3, 2012, 3:22 PM

Post #15 of 16 (316 views)
Permalink
Re: Ticket #10633: Network Control socket fails to listen on second address [In reply to]
#10633: Network Control socket fails to listen on second address
-------------------------------------+--------------------------
Reporter: Paul Saunders <darac@…> | Owner: wagnerrp
Type: Bug Report - General | Status: assigned
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------+--------------------------
Changes (by kenni):

* status: infoneeded => assigned


--
Ticket URL: <http://code.mythtv.org/trac/ticket/10633#comment:14>
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


noreply at mythtv

Dec 30, 2012, 3:59 PM

Post #16 of 16 (160 views)
Permalink
Re: Ticket #10633: Network Control socket fails to listen on second address [In reply to]
#10633: Network Control socket fails to listen on second address
-------------------------------------+--------------------------
Reporter: Paul Saunders <darac@…> | Owner: wagnerrp
Type: Bug Report - General | Status: assigned
Priority: minor | Milestone: unknown
Component: MythTV - General | Version: 0.25
Severity: medium | Resolution:
Keywords: | Ticket locked: 0
-------------------------------------+--------------------------

Comment (by bjoernv@…):

I have this bug in Mythfrontend 0.26 too.

--
Ticket URL: <http://code.mythtv.org/trac/ticket/10633#comment:15>
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

MythTV commits RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.