[mythtv-users] Rebooting master results in slave not connected

[Mark Boyum]

On Thu, Feb 9, 2012 at 2:34 PM, Michael T. Dean <mtdean at thirdcontact.com> wrote:
>
> 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
> >>>      connected".
> >>>
> >>>      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.
>
> Mike
>

As Mike said, a reboot is not necessary.  Simply restart the daemon
for the slave backend and it should reconnect without interrupting
other processes on that machine.

Those much better at scripting than I am could probably automate
checking for disconnected backends and restart them without any user
intervention.


Note that this is the normal output for my system as I don't utilize
the slave backend very often.  But If mythtv-status can determine that
the slave is not connected then action should be able to be taken on
that.

mark at mythtv:~$ mythtv-status

MythTV status for localhost
===========================
Status..........: Thu Feb 9 2012, 3:38 PM
Total Disk Space: Total space is 2,794.3 GB, with 1,984.4 GB used (71.0%)

Encoders:
mythtv (1) - 7
mythtv (2) - Idle
mythtv (3) - Idle
mythtv (4) - Idle
mythtv (5) - Idle
mythtv (6) - Idle
Glendive (9) - Error(Disconnected)
Glendive (10) - Error(Disconnected)

Recording Now:
The Electric Company (TPT) Ends: 16:00:00