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

[Michael Watson]

On 11/02/2012 7:05 AM, Andy Sheen wrote:
>
> Mark Boyum wrote on Thu 09 Feb at 21:45 UK time
>> 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".
>>>>>>
> ...
>
>
>> Those much better at scripting than I am could probably automate
>> checking for disconnected backends and restart them without any user
>> intervention.
>>
>>
> If anyone is interested in how to do this on Ubuntu, it's 3 scripts (two
> upstart scripts and one cron job), the longest of which is 20 or so
> lines including comments. If people want to know how to do this, please
> contact me off line or point me at a wiki page I can update.
>
> Note I'm on 23.1 at the moment that doesn't appear to have the
> mythtv-status command but it works fine with mythtvshutdown -c.
>
Or one simple script;
Set your "Slave Backend Wake Command" to a script, lets call it mywake.sh.
Mywake.sh pings the slave backend, if ping is successful, restart 
mythbackend via ssh, if unsuccessful use WOL to wake the slave backend.
You would need to configure ssh login without password, and sudo 
privileges on slave to restart mythtv-backend process.

Regards,
Michael