Slave Backend recordings unavailable to remote frontends while still recording

[adeffs.mythtv@…]

I'm runing 0.24-fixes from the Mythbuntu Autobuilds.

I have a slave backend with a cable box connected via firewire. It writes the captured file to the storage group drives on the master backend over the network. This slave backend also operates as a frontend in our living room.

The issue I have is that as this slave backend is recording, no other Myth machines on the network are able to play the file, and the master backend is unable to create a screen capture for MythWeb or the Watch Recordings screen. This specific machine though is able to. This also occurs for trying to watch live TV.

So, for instance: This slave backend is recording a show. From the frontend in my bedroom I attempt to watch the show. I get a 1/2 second of audio and what appears to be a single frame of video and then I get kicked back to the Watch Recordings screen with the "backend disconnected"/backend IP lost error. The same occurs if I try and watch Live TV and the tuner that gets selected is the one on this slave backend.

From the frontend running on this slave backend machine though, I *am* able to watch live tv using the "local" tuner, and watch recordings currently being recorded on it.

Now, once the recording is done any of the other frontends is able to watch it with out issue, it is only when the recording is in progress.

I have three logs to attach. One is from a remote frontend attempting to play a recording, the other two are the master and slave backend logs with "-v all" enabled.

[adeffs.mythtv@…]

frontend log

[adeffs.mythtv@…]

Master backend log

[adeffs.mythtv@…]

slave backend log

[Raymond Wagner]

​masterbackend-all.log indicates slave backend is configured to listen on loopback address. As such, only the local frontend can connect to it to access live or in-progress recordings.