[mythtv-users] FE can not retreive files from backend without NFS mount?

Ross Boylan RossBoylan at stanfordalumni.org
Sat Nov 24 19:50:06 UTC 2012


When my FE tries to play a recording from a remote BE (both 0.26.0) it
fails.  However, if I NFS mount the directory with the files from the
BE, it woks.

On failure, visibly, the screen just flashes for a moment.
FE .xsession-errors shows
012-11-24 11:25:23.720969 I  TV: Creating TV object
2012-11-24 11:25:23.761299 N  Suspending idle timer
2012-11-24 11:25:23.764957 I  TV: Created TvPlayWindow.
2012-11-24 11:25:23.851612 I  TV: Attempting to change from None to WatchingPreRecorded
2012-11-24 11:25:23.932581 I  Using protocol version 75
2012-11-24 11:25:23.934215 I  Using protocol version 75
2012-11-24 11:25:23.934805 E  RemoteFile::openSocket(file data socket): Failed to open socket, error was malformed_ann_query
2012-11-24 11:25:23.935503 E  FileRingBuf(myth://192.168.40.2:6543/2091_20120916170000.mpg): RingBuffer::RingBuffer(): Failed to open \
remote file (myth://192.168.40.2:6543/2091_20120916170000.mpg)
2012-11-24 11:25:23.936200 I  TV: Main UI disabled.
2012-11-24 11:25:23.936218 I  TV: Entering main playback loop.
2012-11-24 11:25:23.936529 I  ScreenSaverX11Private: DPMS Deactivated 1
2012-11-24 11:25:23.938423 I  TV: Exiting main playback loop.

This happens every time the FE starts, and repeated attempts in the same session do not fix it.

However, if I execute
mount /usr/local/var/media, given these entries in fstab,
/dev/nfs         /               nfs defaults 0 0
none             /tmp            tmpfs defaults 0 0
none             /var/run        tmpfs defaults 0 0
none             /var/lock       tmpfs defaults 0 0
none             /var/tmp        tmpfs defaults 0 0
none             /media          tmpfs defaults 0 0
192.168.40.2:/usr/local  /mnt/usr/local nfs defaults 0 0
192.168.40.2:/usr/local/var/media        /usr/local/var/media   nfs defaults 0 0

then myth FE can access the same file.  If I do the mount before the
first time I run the FE, the FE can access the file the first time.
I.e., the success if from the NFS mount, not from simply retrying.

The mount is not exactly unrelated to myth; the BE files are
in /usr/local/var/media (actually a subdirectory underneath that).  Note
also the FE is diskless, mounting root from the same machine that the BE
runs on.

It may be relevant that /usr/local and /usr/local/var/media are not
mounted automatically at system startup, though it seems to me they
should be.

Can anyone explain what is going on, or a more elegant solution than a
post-startup script that automatically performs the mount?

My understanding is that the FE should require no direct access to the
BE filesystem, since the BE server sends files or streams as needed
through a myth-specific protocol. Consistent with that understanding,
the log shows the FE attempting to open a socket.  So mounting the
server's directory with the files should be unnecessary.  But it is
necessary.



More information about the mythtv-users mailing list