View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 7 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Tue Feb 27, 2007 5:46 pm 
Offline
Joined: Mon Jul 11, 2005 10:56 am
Posts: 3
I've been running KnoppMyth in a client-server setup since R4V5 with a fairly high degree of success. This is the first time I've had issues setting up a remote frontend that a quick browse through the forums couldn't help me fix. I attempted to upgrade my backend server to R5E50 this weekend and managed to completely bork my install -- apparently my /myth directory was on /dev/hda1, and my backup was overwritten in the upgrade process. Undaunted, I figured I'd start with a fresh install and at least spare myself the pain of trying to get all of my old settings restored.

Following various and assorted howtos in the forums and wiki, I set up my server, mounting /myth on a shiny new RAID-5 array for some added disk space, editing my.cnf to comment out the bind-address, granting permission in mysql for all users named mythtv in my subnet to access mythconverg, and changing all references in mythtv-setup and in the frontend settings to my server's IP address. I also mounted videos, music and photos directories via nfs from my file server. I started up the frontend on the server, and sure enough, I could watch live TV, record and edit shows, watch videos, listen to music and view photos.

The problem came when I went to configure the remote frontend. Once again, I did an auto install and restarted. This time I shut down mysql and mythtv-backend and removed them from startup. I started the frontend and told it to connect to the master backend database at my server's IP address. I also mapped the same directories for videos, music and photos as I did on the server. Now, on my remote fronted, I can watch videos, listen to music and view photos just fine. I can even view, change or schedule upcoming recordings. But whenever I go to a page that streams video from MythTV (the program guide, watch recorded programs, or live TV), the system hangs for several seconds before a "Could not connect to the master backend server -- is it running?" error pops up. This crashes the mythtv-backend process on the server. A simple /etc/init.d/mythtv-backend restart on the server will start it back up and allow it to record, play television, etc. on the server, but I cannot access any of this from the remote frontend. The output from mythfrontend when attempting to view television previews from the recorded programs menu looks like this:

Code:
2007-02-27 17:54:36.314 XMLParse::LoadTheme using /usr/share/mythtv/themes/G.A.N.T./ui.xml
2007-02-27 17:54:36.522 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:36.523 Using protocol version 31
2007-02-27 17:54:44.583 MythSocket(8340800:20): readStringList: Error, timeout (quick).
2007-02-27 17:54:44.583 decodeLongLong() called with offset >= list size.
2007-02-27 17:54:44.610 RingBuf(myth://192.168.0.2:6543/1072_20070227165900.mpg) Error: RingBuffer::safe_read(RemoteFile* ...): read failed
2007-02-27 17:54:44.610 NVP::OpenFile(): Error, couldn't read file: myth://192.168.0.2:6543/1072_20070227165900.mpg
2007-02-27 17:54:47.111 Event socket closed. No connection to the backend.
2007-02-27 17:54:47.111 MythSocket(82e24c0:19): readStringList: Connection died (select).
2007-02-27 17:54:47.111 Remote file timeout.
2007-02-27 17:54:47.112 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.112 Connection timed out.         
         You probably should modify the Master Server
         settings in the setup program and set the   
         proper IP address.
2007-02-27 17:54:47.121 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.122 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.127 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.128 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.161 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.162 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.194 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.195 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.227 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.228 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.260 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.261 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.293 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.294 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.326 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.327 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.359 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.360 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.392 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.393 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.425 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.425 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.458 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.458 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.491 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.491 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.524 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.524 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.557 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.558 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.590 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.591 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.623 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.623 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.656 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.656 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.689 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.689 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.722 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.722 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.755 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.755 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.788 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.788 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.821 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.821 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.854 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.854 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.887 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.887 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.920 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.920 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.953 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.953 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:47.986 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:47.986 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:48.019 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:48.019 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:48.052 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:48.052 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:48.085 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:48.085 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:48.118 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:48.118 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:48.151 Connecting to backend server: 192.168.0.2:6543 (try 1 of 5)
2007-02-27 17:54:48.151 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.
2007-02-27 17:54:48.178 Error: File 'myth://192.168.0.2:6543/1054_20070225215900.nuv' missing.


I have to assume that this isn't an issue with the frontend connecting to the database because it has no problem pulling program information, video posters, music playlists, etc. from the database. Could it be a permissions issue? I don't even know how MythTV goes about streaming the video from the backend server to the remote frontend. The fact that I can watch live and recorded TV on the server makes me even more confused. Any help would be very much appreciated. There are some brilliant people in these forums, and I certainly hope you can spot something I've missed.

Thanks.


Top
 Profile  
 
 Post subject:
PostPosted: Tue Feb 27, 2007 8:06 pm 
Offline
Joined: Sat Feb 21, 2004 11:54 am
Posts: 48
Is your swap activated on your mythfrontend? Also, you'll probably want to move this thread to the KnoppMyth General board to get more eyes looking at it.


Top
 Profile  
 
 Post subject:
PostPosted: Tue Feb 27, 2007 8:27 pm 
Offline
Joined: Mon Jul 11, 2005 10:56 am
Posts: 3
Yes. I have a 1G swap partition active on /dev/hda2.

Good point about the topic area. If any moderator would be so kind as to push this over to General, I'd be much appreciative.


Top
 Profile  
 
 Post subject:
PostPosted: Tue Feb 27, 2007 8:42 pm 
Offline
Joined: Sat Feb 21, 2004 11:54 am
Posts: 48
Can you try telnetting into that port from another system on your network? On my end if I do this from a workstation:

Code:
# telnet 192.168.0.10 6543


...it goes to a blank screen so I know the port is open. Also, do you have the output from the backend right before the frontend crashes it? Lastly, does the file frontend is calling for exist on your backend?


Top
 Profile  
 
 Post subject:
PostPosted: Wed Feb 28, 2007 5:42 am 
Offline
Joined: Mon Jul 11, 2005 10:56 am
Posts: 3
This is odd. My frontend works, now. I was going through /var/log/myth/mythbackend.log, trying to find some sort of clue as to what was happening on the backend when it shut down, and I noticed that the unique names I assigned to my server and frontend -- "Master Server" and "Living Room" respectively -- only showed up with the first of the two words of their names in the logs. Mainly because I'm anal retentive and like to have things recorded properly, I went into the settings on both of them and changed their names to "MasterBackend" and "RemoteFrontend". I had to re-enter all of the settings for the frontends on both machines as they are tied to the unique name in the database, but once I did, live and recorded TV "magically" started working on the remote frontend.

My best guess is that mythtv-backend was freaking out over the space in the unique name of the remote fronted? Can anyone confirm this? As much as I'd love certainty, I'm much happier that I can watch TV on the projector in my living room again. Thank you all so much for your help!


Top
 Profile  
 
 Post subject:
PostPosted: Wed Feb 28, 2007 11:45 am 
Offline
Joined: Tue Aug 08, 2006 7:08 pm
Posts: 561
Location: UK
DNS machine names shouldn't have spaces. When trying to set up another Linux box it wouldn't accept underscores either so either no spaces or a dash - .

Bruce S.

_________________
Updated 2019/10/26: AthlonII X2 265 Gigabyte GA-970A-DS3P
16Gb PC 1866 DDR3, 500GB+2TB+4TB SATA HDD,
SATA DVD-RW Asus DRW-24D5MT , NVIDIA GeForce GT1080
Hauppauage Nova-T 500, Nova-T LinHes R8.6.1


Top
 Profile  
 
 Post subject:
PostPosted: Wed Feb 28, 2007 6:49 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
bruce_s01 wrote:
DNS machine names shouldn't have spaces. When trying to set up another Linux box it wouldn't accept underscores either so either no spaces or a dash - .

Bruce S.

This BTW is part of the standard for internet host and domain names. I forget the RFC number, chapter an verse, but it's limited to case insensitive alpha-numeric and dash, with dots between the domain level components and has been basically forever. There used to be some DNS stuff that was sloppy and allowed underscore but even that hasn't worked for at least 5 years now.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 7 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 19 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu