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

aaron at boim.com aaron at boim.com
Thu Dec 2 13:41:44 UTC 2010


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.

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

How is it that the first entry seems to be pointing at the
proper backend server, 192.168.1.1:6543,
but when it tries to switch to WatchingPreRecorded, it looks
for a backend at 127.0.0.1:6543?

           aaron



More information about the mythtv-users mailing list