keemllib at gmail
Apr 28, 2012, 8:39 AM
Post #4 of 6
On 04/28/2012 03:13 AM, Wilson Waters wrote:
Re: Frontend control socket 6547 bind issue
[In reply to]
> Hi all,
> I'm having an issue connecting to the Mythtv frontend control socket (default port 6547) after upgrading to 0.25. I have a feeling it may be
> because it is bound to localhost.
> wilson [at] t:~$ netstat -an | grep LISTEN
> tcp 0 0 127.0.0.1:6543 0.0.0.0:* LISTEN
> tcp 0 0 127.0.0.1:6546 0.0.0.0:* LISTEN
> tcp 0 0 127.0.0.1:6547 0.0.0.0:* LISTEN
> tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN
> Is there any way to configure what interface it binds to (preferably all).
In 0.25 the addresses used are what your interface knows about
(look for addresses in ifconfig's output.) The same is true for
both the front and backends.
You can see what either FE/BE is binding to by looking in your
logs. Mine FE looks like:
I [4051/4051] CoreContext serverpool.cpp:306 (listen) - Listening on TCP 127.0.0.1:6547
I [4051/4051] CoreContext serverpool.cpp:306 (listen) - Listening on TCP 192.168.1.123:6547
I [4051/4051] CoreContext serverpool.cpp:306 (listen) - Listening on TCP [::1]:6547
You might want to look at your backend settings too. Are your Local and
Master Backend IP addresses set to 127.0.0.1 rather than what you need?
(Nothing wrong with 127..., you just can't connect to from a remote FE.)
Binding to all doesn't happen anymore for reasons above my pay grade,
however, one of them was the problem with some distributions setting
the bindv6only sysctl to 1, causing those users to loose IPv4 connectivity.
mythtv-users mailing list
mythtv-users [at] mythtv