[mythtv-users] Slave backend reboot procedure

[Jan Ceuleers]

Dear list,

A little while ago I moved some of my tuners to another location in the
house so that they are closer to the signal source, thereby improving
recording quality. In doing so I connected them to a machine which
previously was only a frontend, i.e. turning it into a slave backend as
well.

It seems though that whenever I reboot that machine its tuners aren't
regarded as being available (as repported by Mythweb) until I also
restart the slave backend (not necessarily the whole machine, just the
backend service).

Many years ago I also had a slave backend (on a much older MythTV
release), and I remember that restarting the slave backend caused its
tuners to become available automatically, i.e. without the need to
restart the master backend process.

I therefore assume that there is something in my configuration which
currently breaks this. Any ideas?

$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v29.1
MythTV Branch :
Network Protocol : 91
Library API : 29.20180316-1
QT Version : 5.5.1
Options compiled in:
 linux profile use_hidesyms using_alsa using_oss using_pulse
using_pulseoutput using_backend using_bindings_perl
using_bindings_python using_bindings_php using_crystalhd using_dvb
using_firewire using_frontend using_hdhomerun using_vbox using_ceton
using_hdpvr using_ivtv using_joystick_menu using_libcec using_libcrypto
using_libdns_sd using_libfftw3 using_libxml2 using_lirc using_mheg
using_opengl using_opengl_video using_opengl_themepainter using_qtwebkit
using_qtscript using_qtdbus using_taglib using_v4l2 using_x11
using_xrandr using_xv using_profiletype using_systemd_notify
using_systemd_journal using_bindings_perl using_bindings_python
using_bindings_php using_freetype2 using_mythtranscode using_opengl
using_vaapi using_vdpau using_ffmpeg_threads using_mheg using_libass
using_libxml2 using_libmp3lame

Thanks, Jan