[mythtv] Latest commits have broken UPNP database lookup

[Stuart Auchterlonie]

On 14/11/17 00:17, Peter Bennett wrote:
> 
> 
> On 11/13/2017 04:55 PM, David Hampton wrote:
>> Will it ask before connecting?  How do I keep my test/master frontend
>> from finding my 0.28/production backend and attempting to upgrade its
>> database?  Run both test frontend and backend in a VM so there's no
>> traffic on my home network?  Unplug the ethernet from my workstation
>> while testing?:-)   I want to make sure I don't mess up my production
>> system.
>>
>> David
> Hi David
> 
> If your backend PIN is 0000 and only one backend is running then it will
> connect without even asking.
> 
> Run mythtv-setup on your production backend and set a unique pin that is
> not 0000. That is what I do to prevent inadvertent connection to the
> production system. Note the pin does not have to be 4 digits or numeric.
> It can be a whole sentence, but only if it is 0000 will it connect
> automatically.
> 
> I recommend also using different database names, user ids and passwords
> for production and development. If everything is mythconverg / mythtv /
> mythtv there may be more risk of inadvertently connecting to the wrong
> place.
> 
> A remote frontend or backend will not update the backend database. I
> don't know the details of how it checks, but it does log a message about
> not being authorized to upgrade.
> 
> The times when I have inadvertently connected to my production system
> were when I had a production frontend on my development machine, then
> inadvertently started up a development backend. It goes to
> .mythtv/config.xml and connects - PIN numbers or passwords do not
> protect in this case because everything is in the config.xml. Nowadays I
> have a set of scripts that isolate my various versions so that this type
> of thing cannot happen. I avoid having a .mythtv directory at all on my
> user id on the development system.
> 
> Let me know if you need more information.

I have this set in my wrapper scripts for frontend / backend etc

MYTHCONFDIR=$HOME/.mythtv-prod/

so anything prod is automatically configured to use a non standard
location for it's configuration.

I also have separate database, and use a non standard backend port
(7544 vs 6544) for my development setup. As a consequence I can
run both my prod and dev backend instances on the same physical
hardware.

I also split my dual tuners across both backends. I have a dual
DVB-T and dual DVB-S2, so both dev and prod have 1x DVB-t and 1x
DVB-S2 tuner available.

One crucial detail i've just noticed I missed, is that both the
prod (fixes/29) and dev (master) instances install to different
non standard paths. The wrapper scripts i've mentioned above
also set PATH, LD_LIBRARY_PATH and PYTHONPATH to include the
non standard location

I did do a full write up on this once. If it's of interest to
people I can look into documenting this on the wiki.


Regards
Stuart