[mythtv-users] arch mythtv

[Hika van den Hoven]

Hoi Kirk,

Wednesday, June 17, 2015, 7:39:51 PM, you wrote:



> On 6/17/2015 10:21 AM, Mike Perkins wrote:
>> On 17/06/15 15:45, Kirk Bocek wrote:
>>>
>>>
>>> On 6/17/2015 7:14 AM, Frank Phillips wrote:
>>>> On Wed, Jun 17, 2015 at 7:39 AM, James Linder <jam at tigger.ws
>>>> <mailto:jam at tigger.ws>> wrote:
>>>>
>>>>      In quest of serious pain and suffering (really all about USB 3 
>>>> and recent
>>>>     kernels fixing the problem, also tried android myth and stumbled 
>>>> over the
>>>>     encoding) I threw away my existing mythtv setup, used the distro 
>>>> (arch
>>>>     linux) compiled mythtv and installed myth keeping my current DB.
>>>>     [a unix guru is someone who has has a bad experience with rm; 
>>>> I’m having a
>>>>     bad experience with uefi]
>>>>
>>>>     None of my front ends connect all claiming no backend even 
>>>> saying “backend
>>>>     is running” “no backend” at the same time.
>>>>
>>>>     Browsing 192.168.5.33:6544 <http://192.168.5.33:6544> shows the 
>>>> schedule
>>>>     etc. Recordings are placed in the store, I can retrieve and 
>>>> watch in vlc.
>>>>     I can access the backend database ie mysql -umythtv -pmythtv 
>>>> -hbackend
>>>>     mythconverg shows the tables.
>>>>
>>>>     But frontend says:
>>>>
>>>>     015-06-17 19:36:09.143575 E  MythSocket(107826ec0:-1): Failed to 
>>>> connect
>>>>     to (192.168.5.33:0 <http://192.168.5.33:0>) Unknown error
>>>>     2015-06-17 19:36:09.143885 E  Connection to master server timed 
>>>> out.
>>>>                             Either the server is down or the master 
>>>> server
>>>>     settings
>>>>                             in mythtv-settings does not contain the 
>>>> proper IP
>>>>     address
>>>>
>>>>     2015-06-17 19:36:09.241548 I  MythCoreContext: Connecting to 
>>>> backend
>>>>     server: 192.168.5.33:0 <http://192.168.5.33:0> (try 1 of 1)
>>>>     2015-06-17 19:36:09.242276 E  MythSocket(113e1fac0:-1): Failed 
>>>> to connect
>>>>     to (192.168.5.33:0 <http://192.168.5.33:0>) Unknown error
>>>>     2015-06-17 19:36:09.242496 E  Connection to master server timed 
>>>> out.
>>>>                             Either the server is down or the master 
>>>> server
>>>>     settings
>>>>                             in mythtv-settings does not contain the 
>>>> proper IP
>>>>     address
>>>>
>>>>     2015-06-17 19:36:14.243239 I  MythCoreContext: Connecting to 
>>>> backend
>>>>     server: 192.168.5.33:0 <http://192.168.5.33:0> (try 1 of 1)
>>>>     2015-06-17 19:36:14.244025 E  MythSocket(107d97760:-1): Failed 
>>>> to connect
>>>>     to (192.168.5.33:0 <http://192.168.5.33:0>) Unknown error
>>>>     2015-06-17 19:36:14.244193 E  Connection to master server timed 
>>>> out.
>>>>                             Either the server is down or the master 
>>>> server
>>>>     settings
>>>>                             in mythtv-settings does not contain the 
>>>> proper IP
>>>>     address
>>>>
>>>>     2015-06-17 19:36:19.244579 I  MythCoreContext: Connecting to 
>>>> backend
>>>>     server: 192.168.5.33:0 <http://192.168.5.33:0> (try 1 of 1)
>>>>
>>>>     What on earth can the problem be? [this frontend has been 
>>>> working for
>>>>     years and worked up to my fiddle]
>>>>     Thanks
>>>>     James
>>>>
>>>>
>>>> Your trying to connect to port 0. It should be 6543.
>>>>
>>>
>>> Checking the settings table on my database:
>>>
>>> value    data    hostname
>>> MasterServerIP    10.0.2.16    NULL
>>> MasterServerPort    6543    NULL
>>>
>> The other obvious thing is: have you checked your mysql settings? 
>> There's an entry on the config file my.cnf which disallows network 
>> access, although I can't remember exactly which it is.
>>
>> What you describe would fit that scenario exactly.
>>

> Looking at my /etc/my.cnf:

> # Don't listen on a TCP/IP port at all. This can be a security enhancement,
> # if all processes that need to connect to mysqld run on the same host.
> # All interaction with mysqld must be made via Unix sockets or named pipes.
> # Note that using this option without enabling named pipes on Windows
> # (via the "enable-named-pipe" option) will render mysqld useless!
> #
> #skip-networking

# bind-address = 127.0.0.1
should be
bind-address = <your ip-address>

Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens