[mythtv-users] Switching frontends to different backends failing

[Jim Abernathy]

On 12/19/19 2:45 PM, Greg Oliver wrote:
> On Thu, Dec 19, 2019 at 9:15 AM James Abernathy <jfabernathy at gmail.com 
> <mailto:jfabernathy at gmail.com>> wrote:
>
>
>     > On Dec 19, 2019, at 9:47 AM, Jim Abernathy
>     <jfabernathy at gmail.com <mailto:jfabernathy at gmail.com>> wrote:
>     >
>     > I'm doing some testing since it's too cold to go outside.  I
>     have a production V30 backend that does all my normal recording of
>     OTA Network shows using a PCIe tuner.
>     >
>     > Under test I have a RPI4 V30 backend recording from a HDHR
>     Quatro and I've had some show breakups that I know are not antenna
>     problems. It's either HDHR or network issues.
>     >
>     > So to test this out I have to switch my Shield TV Mythtv
>     Frontend (v31 Pre 539) to the RPI4 from the production backend but
>     it fails.
>     >
>     > On the Shield TV I can switch Mythtv Leanfront v0-86 just by
>     changing the IP address and refreshing.  Same with Kodi 18.5.
>     >
>     > On the Shield TV Mythtv Frontend I change the IP and the
>     password for the mythconverg database but it fails to connect even
>     after a restart. So I'm assuming I'm missing a step.
>     >
>     > The RP4 had it's mythconverg setup with the following commands
>     in a script:
>     >
>     > CREATE DATABASE IF NOT EXISTS mythconverg;
>     > CREATE USER IF NOT EXISTS 'mythtv'@'%' IDENTIFIED BY 'mythtv';
>     > CREATE USER IF NOT EXISTS 'mythtv'@'localhost' IDENTIFIED BY
>     'mythtv';
>     > SET PASSWORD FOR 'mythtv'@'%' = PASSWORD('$mythtv_password');
>     > SET PASSWORD FOR 'mythtv'@'localhost' =
>     PASSWORD('$mythtv_password');
>     > CONNECT mythconverg;
>     > GRANT ALL PRIVILEGES ON *.* TO 'mythtv'@'%' WITH GRANT OPTION;
>     > GRANT ALL PRIVILEGES ON *.* TO 'mythtv'@'localhost' WITH GRANT
>     OPTION;
>     > FLUSH PRIVILEGES;
>     > EXIT
>     >
>     > And the /etc/mysql/mariadb.conf.d/mythtv.cnf has the '#' removed
>     from the bind-address statement.
>     >
>     > Anyone know the missing piece??
>     >
>     > Jim A
>     >
>     >
>
>     Some additional data.  I checked the mythtv-setup on the RPI4
>     backend and noticed the Primary IP Address/DNS name was
>     127.0.0.1.  I hit enter and it listed a bunch of different
>     addressed so I selected it’s real IP address of 192.168.0.44.
>     After saving the change and exiting, I restarting the backend I
>     noticed a change.
>
>     The mythtv frontend didn’t fail to connect to the backend, it just
>     changed the IP and password back to the Production backend and
>     works normally.  No matter how many times I change the IP to
>     192.168.0.44 and the password to ‘mythtv’ and save the results,
>     when I exit and restart the FE it’s back pointing to the
>     production backend and not the RPi4 backend.
>
>     I’ll try clearing all data for the frontend app on the Shield and
>     see what happens. I was hoping not to have to do that.
>
>     Jim A
>
>
> IIRC, the frontends use UPnP if available to find backends.  I have 
> been running the backend with --noupnp for so long that I cannot 
> remember why I turned it off, but I think this exact thing was it.
>
>
I did try clearing out all the data for the app in the Android setting 
and that allowed me to set it up for the test backend. But there are a 
lot of settings that need to be set for mythtv-frontend to work on 
Shield TV.

So I setup mythfrontend only for my production backend on the Shield TV 
and I will use mythtv-leanfront to test the video issues on my test 
backend. I can setup the recordings using mythweb and not use 
mythfrontend on the test system. Leanfront only needs the IP address 
changed and it connects immediately.

Jim A


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20191219/b7ef0e8f/attachment.htm>