[mythtv-commits] Ticket #10633: Network Control socket fails to listen on second address

MythTV noreply at mythtv.org
Fri Apr 20 15:05:02 UTC 2012

#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

More information about the mythtv-commits mailing list