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

Mike Perkins mikep at randomtraveller.org.uk
Thu Dec 2 15:00:01 UTC 2010

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
> What is going on?
> Is there a database entry that is overriding my settings?
> I cannot find a reasonable way to make sure it is pointed
> at the backend.
> I installed the backend, then ran mythtv-setup, and was
> able to get it to re-point at the backend again.
> It seems ridiculous that I need to install a backend to
> get a local mythtv-setup, which seems to be the only way
> to reset the backend IP setting to actually point at
> the real backend.
> Here is some interesting output from the console:
> 2010-12-02 06:13:05.909 MythContext: Connecting to backend server: 
> (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
> 2010-12-02 06:13:20.003 RemoteFile::openSocket(file data socket), Error:
>             Could not connect to server
> 2010-12-02 06:13:20.003 RingBuffer::RingBuffer(): Failed to open remote 
> file (myth://
> How is it that the first entry seems to be pointing at the
> proper backend server,,
> but when it tries to switch to WatchingPreRecorded, it looks
> for a backend at
mythtv-setup *only* sets information for a backend *on that host* to use. You 
should not need to run it on any machine which is front-end only.

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).

I'm also guessing that you have left the IP addresses of your master backend at 
their default settings, i.e. This is what may be causing your 
immediate problem. 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).

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. If 
you have installed a database on your frontend host, you will need to prevent 
mythtv from accessing it by making sure mysql does not start up on that host.


Mike Perkins

More information about the mythtv-users mailing list