[mythtv-users] Mythfrontend problem...

Sun Apr 5 05:29:11 UTC 2009

Hi.  I'm having trouble adding a new mythfrontend to an existing 
installation.  Here's my setup.  I have a backend (named mythserver) 
happily recording shows.  I've been using an Xbox running XBMC (with both 
native and the XBMCMythTV python script) as a frontend successfully for a 
while now.  This works fine.  Now I want to add a new frontend.  This 
frontend is a ``normal'' mythfrontend running under gentoo (also on an 
xbox but it's a native installation of Gentoox so it should act just like 
Linux on any other i386 box).  Since I already have a working
frontend + backend setup this should be pretty easy, however, I get the 
following when running mythfronend:

------------------------------------------------------------------------
2009-04-05 00:13:37.550 Using runtime prefix = /usr
2009-04-05 00:13:38.614 DPMS is active.
2009-04-05 00:13:38.687 Empty LocalHostName.
2009-04-05 00:13:38.687 Using localhost value of jen-xbox
2009-04-05 00:13:38.690 Testing network connectivity to mythserver
2009-04-05 00:13:39.179 New DB connection, total: 1
2009-04-05 00:13:39.330 Connected to database 'mythconverg' at host: 
mythserver
2009-04-05 00:13:39.361 Closing DB connection named 'DBManager0'
2009-04-05 00:13:39.377 Primary screen 0.
2009-04-05 00:13:39.380 Connected to database 'mythconverg' at host: 
mythserver
2009-04-05 00:13:39.383 Using screen 0, 640x480 at 0,0
2009-04-05 00:13:39.574 New DB connection, total: 2
2009-04-05 00:13:39.577 Connected to database 'mythconverg' at host: 
mythserver
2009-04-05 00:13:39.586 mythfrontend version: 0.21.20080304-1 
www.mythtv.org
2009-04-05 00:13:39.586 Enabled verbose msgs:  important general
2009-04-05 00:13:42.203 No theme dir: /home/djm/.mythtv/themes/G.A.N.T
2009-04-05 00:13:42.206 Primary screen 0.
2009-04-05 00:13:42.208 Using screen 0, 640x480 at 0,0
2009-04-05 00:13:42.210 No theme dir: /home/djm/.mythtv/themes/G.A.N.T
2009-04-05 00:13:42.212 Switching to square mode (G.A.N.T)
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
2009-04-05 00:13:42.414 Using the Qt painter
2009-04-05 00:13:42.422 JoystickMenuClient Error: Joystick disabled - 
Failed to read /home/djm/.mythtv/joystickmenurc
Xlib:  extension "GLX" missing on display ":0.0".
2009-04-05 00:13:45.153 Loading from: 
/usr/share/mythtv/themes/G.A.N.T/base.xml
2009-04-05 00:13:45.336 Loading from: 
/usr/share/mythtv/themes/default/base.xml
2009-04-05 00:13:45.640 Registering Internal as a media playback plugin.
2009-04-05 00:13:45.752 No theme dir: /home/djm/.mythtv/themes/G.A.N.T
2009-04-05 00:13:51.865 Connecting to backend server: mythserver:6543 (try 
1 of 5)
2009-04-05 00:13:51.866 Connection timed out.
 			You probably should modify the Master Server
 			settings in the setup program and set the
 			proper IP address.
------------------------------------------------------------------------

The usual reason for the above error is because one has specified 
localhost or 127.0.0.1 in mythtv-setup's General Setup page on the 
backend, however, I have set this up correctly.  Also note that this is 
not an error connecting to the database.  The new mythfrontend prints a 
message saying that it connects to the database just fine and I can 
connect to it from the new frontend via ``mysql -umythtv -p -h 
mythserver'' with the same credentials.

Also,
     mysql> SELECT * FROM settings WHERE data='localhost';
     Empty set (0.02 sec)

     mysql> SELECT * FROM settings WHERE data='127.0.0.1';
     Empty set (0.02 sec)

So, this has nothing to do with trying to connect to localhost.

     mysql> SELECT * FROM settings WHERE value='MasterServerIP';

     +----------------+------------+----------+
     | value          | data       | hostname |
     +----------------+------------+----------+
     | MasterServerIP | mythserver | NULL     |
     +----------------+------------+----------+
     1 row in set (0.00 sec)

That's the value in question and it has the correct data.  This is not a 
DNS issue because I can ping mythserver from the new frontend just fine 
(and, as I said, it connects to the mysql server running on mythserver 
just fine).  It's not a firewall issue because I do not have one installed 
on mythserver (and because my current/working frontend uses the exact same 
settings, on the same lan, and works just fine).  It's not a protocol 
version problem because:

mythserver> mythbackend --version
MythTV Version   : export?(C)
MythTV Branch    : branches/release-0-21-fixes
Library API      : 0.21.20080304-1
Network Protocol : 40
Options compiled in:
  linux profile using_oss using_alsa using_arts using_jack using_backend 
using_dbox2 using_dvb using_firewire using_frontend using_hdhomerun 
using_iptv using_ivtv using_joystick_menu using_libfftw3 using_lirc 
using_opengl_vsync using_v4l using_x11 using_xrandr using_xv using_xvmc 
using_xvmcw using_xvmc_vld using_bindings_perl using_bindings_python 
using_opengl using_ffmpeg_threads using_libavc_5_3 using_live

new-frontend> mythfrontend --version
MythTV Version   : 18314
MythTV Branch    : branches/release-0-21-fixes
Library API      : 0.21.20080304-1
Network Protocol : 40
Options compiled in:
  linux profile using_oss using_alsa using_backend using_dbox2 
using_frontend using_hdhomerun using_iptv using_ivtv using_joystick_menu 
using_opengl_vsync using_v4l using_x11 using_xrandr using_xv 
using_glx_proc_addr_arb using_bindings_perl using_bindings_python 
using_opengl using_ffmpeg_threads using_live

I seached the mailing list and the closest hit I found was:
     http://www.gossamer-threads.com/lists/mythtv/users/331580

However, his problem was that his frontend was trying to connect to 
localhost; that isn't my problem.  The log message clearly shows that the 
new frontend is trying to connect to mythserver:6543 and failing.  On 
mythserver, ``netstat -l -p'' tells me that mythbackend is listening for 
tcp connections on 0.0.0.0:6543, 0.0.0.0:6544, and udp connections on 
0.0.0.0:6549.

Running netcat from the new frontend against mythserver:6543 via
``nc -q0 -v mythserver 6543 < /dev/null'' tells me that it can make 
connections just fine from the new frontend to mythserver on the port in 
question.

So, I'm stumped.

Any ideas?