[mythtv-users] frontend keeps flipping to local backend 0.23.1

[aaron at boim.com]

Quoting Mike Perkins <mikep at randomtraveller.org.uk>:

> aaron at boim.com wrote:
>> I am trying to set up a frontend for a separate backend.
>> For some reason it works for a while, then it tries
>> to access a non-existent backend at 127.0.0.1.
>> ...
>> Here is some interesting output from the console:
>>
>> 2010-12-02 06:13:05.909 MythContext: Connecting to backend server:  
>> 192.168.1.1:6543 (try 1 of 1)
>> 2010-12-02 06:13:05.910 Using protocol version 23056
>> 2010-12-02 06:13:07.460 Loading menu theme from  
>> /usr/share/mythtv/themes/defaultmenu//library.xml
>> 2010-12-02 06:13:09.604 XMLParseBase: Loading window theme from  
>> /usr/share/mythtv/themes/Arclight/recordings-ui.xml
>> 2010-12-02 06:13:19.995 TV: Attempting to change from None to  
>> WatchingPreRecorded
>> 2010-12-02 06:13:20.003 RemoteFile::openSocket(control socket), Error:
>>            Could not connect to server 127.0.0.1:6543
>> 2010-12-02 06:13:20.003 RemoteFile::openSocket(file data socket), Error:
>>            Could not connect to server 127.0.0.1:6543
>> 2010-12-02 06:13:20.003 RingBuffer::RingBuffer(): Failed to open  
>> remote file (myth://127.0.0.1:6543/1051_20101202050000.mpg)
...
> When you start up a front end for the first time, the first screen  
> you should see should be a language screen, followed by a screen  
> asking you where the *master* back end is (amongst other things). In  
> there you should put the IP address of your backend (I'm assuming  
> that you only want one at this stage).

How can I force it to go through that process again.
Should I delete ~/.mythtv/config.xml, or the whole folder?

> I'm also guessing that you have left the IP addresses of your master  
> backend at their default settings, i.e. 127.0.0.1. This is what may  
> be causing your immediate problem.

Something set it to that.  I'm pretty sure I initialized the
frontend for a backend at 192.168.1.1

> You need to go onto that machine and change them to reflect the  
> correct IP address of that host (while the backend is stopped of  
> course).

Hmm...  so the address for the backend on the backend
should also be 192.168.1.1?  That could make sense.
I have also been playing with a frontend on the backend (for testing),
and perhaps it clobbered the setting with 127.0.0.1.

> You may also need to check that your mysql instance on the master  
> backend is accessable from the network. Your database should only  
> reside in one place.

The database works fine.  It even displays all my recordings,
with their preview images, info, etc.

> If you have installed a database on your frontend host,

No.  mysql is only on backend.

   Thanks,

              aaron