[mythtv-users] Rebooting master results in slave not connected
Michael T. Dean
mtdean at thirdcontact.com
Thu Feb 9 20:34:55 UTC 2012
On 02/09/2012 03:27 PM, Andy Sheen wrote:
> Mark Boyum wrote on Thu 09 Feb at 20:20 UK time
>> On Thu, Feb 9, 2012 at 1:57 PM, Andy Sheen wrote:
>>> I've been running MythTV 23.bugfix on Ubuntu 10.04 for a while
>>> now. I'm
>>> extremely happy with it but decided to add a slave backend on one
>>> of my
>>> other computers. It all works very nicely unless I reboot the master
>>> back end when the slave seems to appear with the tuners "currently not
>>> Have I set something up incorrectly - I've done a search but pulled up
>>> nothing seemingly relevant? I've waited 30 minutes to see if it would
>>> reconnect, but nothing doing. It seems a bit silly that if the
>>> master is
>>> rebooted, the slave can't reconnect. Any advice?
>> That has been my experience. If the master is restarted then the
>> slaves will only reconnect if they are restarted as well.
> Thanks Mark. That seems really painful. OK if you have a network of
> dedicated recording devices, but if you've just put a card into the back
> of another machine, which is used for other things, I'd have expected it
> to be tolerant to machines going up and down. Is there a way to
> rebroadcast the announce periodically.?
No idea whether reconnecting works or not (or whether it works in
current 0.24-fixes MythTV and was broken in 0.23), but restart !=
reboot. Worst case, just restart mythbackend on the remote systems.
More information about the mythtv-users